diff --git a/specification/maps/data-plane/Common/preview/1.0/common.json b/specification/maps/data-plane/Common/preview/1.0/common.json
index f91f88f9b5b6..8f05314cd2c9 100644
--- a/specification/maps/data-plane/Common/preview/1.0/common.json
+++ b/specification/maps/data-plane/Common/preview/1.0/common.json
@@ -120,7 +120,7 @@
}
}
},
- "CoordinatesPair": {
+ "LatLongPair": {
"description": "A location represented as a latitude and longitude.",
"type": "object",
"properties": {
@@ -136,7 +136,7 @@
}
}
},
- "CoordinatesPairAbbreviated": {
+ "LatLongPairAbbreviated": {
"description": "A location represented as a latitude and longitude using short names 'lat' & 'lon'.",
"type": "object",
"properties": {
@@ -532,7 +532,7 @@
"Language": {
"name": "language",
"in": "query",
- "description": "Language in which search results should be returned. Should be one of supported IETF language tags, case insensitive. When data in specified language is not available for a specific field, default language is used.\n\nPlease refer to [Supported Languages](https://docs.microsoft.com/en-us/azure/azure-maps/supported-languages) for details.",
+ "description": "Language in which search results should be returned. Should be one of supported IETF language tags, case insensitive. When data in specified language is not available for a specific field, default language is used.\n\nPlease refer to [Supported Languages](https://docs.microsoft.com/azure/azure-maps/supported-languages) for details.",
"type": "string",
"x-ms-parameter-location": "method"
},
@@ -614,16 +614,115 @@
},
"View": {
"name": "view",
+ "x-ms-client-name": "localizedMapView",
"in": "query",
- "description": "The View parameter specifies which set of geopolitically disputed content is returned via Azure Maps services, including borders and labels displayed on the map. The View parameter (also referred to as “user region parameter”) will show the correct maps for that country/region. By default, the View parameter is set to “Unified” even if you haven’t defined it in the request. It is your responsibility to determine the location of your users, and then set the View parameter correctly for that location. Alternatively, you have the option to set ‘View=Auto’, which will return the map data based on the IP address of the request. The View parameter in Azure Maps must be used in compliance with applicable laws, including those regarding mapping, of the country where maps, images and other data and third party content that you are authorized to access via Azure Maps is made available. Example: view=IN.\n\nPlease refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.",
+ "description": "The View parameter (also called the \"user region\" parameter) allows you to show the correct maps for a certain country/region for geopolitically disputed regions. Different countries have different views of such regions, and the View parameter allows your application to comply with the view required by the country your application will be serving. By default, the View parameter is set to “Unified” even if you haven’t defined it in the request. It is your responsibility to determine the location of your users, and then set the View parameter correctly for that location. Alternatively, you have the option to set ‘View=Auto’, which will return the map data based on the IP address of the request. The View parameter in Azure Maps must be used in compliance with applicable laws, including those regarding mapping, of the country where maps, images and other data and third party content that you are authorized to access via Azure Maps is made available. Example: view=IN.\n\nPlease refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.",
+ "x-ms-parameter-location": "method",
"type": "string",
- "x-ms-parameter-location": "method"
+ "enum": [
+ "AE",
+ "AR",
+ "BH",
+ "IN",
+ "IQ",
+ "JO",
+ "KW",
+ "LB",
+ "MA",
+ "OM",
+ "PK",
+ "PS",
+ "QA",
+ "SA",
+ "SY",
+ "YE",
+ "Auto",
+ "Unified"
+ ],
+ "x-ms-enum": {
+ "name": "LocalizedMapView",
+ "modelAsString": true,
+ "values": [
+ {
+ "value": "AE",
+ "description": "United Arab Emirates (Arabic View)"
+ },
+ {
+ "value": "AR",
+ "description": "Argentina (Argentinian View)"
+ },
+ {
+ "value": "BH",
+ "description": "Bahrain (Arabic View)"
+ },
+ {
+ "value": "IN",
+ "description": "India (Indian View)"
+ },
+ {
+ "value": "IQ",
+ "description": "Iraq (Arabic View)"
+ },
+ {
+ "value": "JO",
+ "description": "Jordan (Arabic View)"
+ },
+ {
+ "value": "KW",
+ "description": "Kuwait (Arabic View)"
+ },
+ {
+ "value": "LB",
+ "description": "Lebanon (Arabic View)"
+ },
+ {
+ "value": "MA",
+ "description": "Morocco (Moroccan View)"
+ },
+ {
+ "value": "OM",
+ "description": "Oman (Arabic View)"
+ },
+ {
+ "value": "PK",
+ "description": "Pakistan (Pakistani View)"
+ },
+ {
+ "value": "PS",
+ "description": "Palestinian Authority (Arabic View)"
+ },
+ {
+ "value": "QA",
+ "description": "Qatar (Arabic View)"
+ },
+ {
+ "value": "SA",
+ "description": "Saudi Arabia (Arabic View)"
+ },
+ {
+ "value": "SY",
+ "description": "Syria (Arabic View)"
+ },
+ {
+ "value": "YE",
+ "description": "Yemen (Arabic View)"
+ },
+ {
+ "value": "Auto",
+ "description": "Return the map data based on the IP address of the request."
+ },
+ {
+ "value": "Unified",
+ "description": "Unified View (Others)"
+ }
+ ]
+ }
},
"xTileIndex": {
"name": "x",
"x-ms-client-name": "xTileIndex",
"in": "query",
- "description": "X coordinate of the tile on zoom grid. Value must be in the range [0, 2`zoom` -1].\n\nPlease see [Zoom Levels and Tile Grid](https://docs.microsoft.com/en-us/azure/location-based-services/zoom-levels-and-tile-grid) for details.",
+ "description": "X coordinate of the tile on zoom grid. Value must be in the range [0, 2`zoom` -1].\n\nPlease see [Zoom Levels and Tile Grid](https://docs.microsoft.com/azure/location-based-services/zoom-levels-and-tile-grid) for details.",
"required": true,
"type": "integer",
"format": "int32",
@@ -633,7 +732,7 @@
"name": "y",
"x-ms-client-name": "yTileIndex",
"in": "query",
- "description": "Y coordinate of the tile on zoom grid. Value must be in the range [0, 2`zoom` -1].\n\nPlease see [Zoom Levels and Tile Grid](https://docs.microsoft.com/en-us/azure/location-based-services/zoom-levels-and-tile-grid) for details.",
+ "description": "Y coordinate of the tile on zoom grid. Value must be in the range [0, 2`zoom` -1].\n\nPlease see [Zoom Levels and Tile Grid](https://docs.microsoft.com/azure/location-based-services/zoom-levels-and-tile-grid) for details.",
"required": true,
"type": "integer",
"format": "int32",
@@ -686,7 +785,7 @@
"x-ms-error-response": true
},
"409StorageLimit": {
- "description": "The [data storage limit](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-maps-limits) is reached on the Azure Maps account. You can always use the [Data Delete API](https://docs.microsoft.com/en-us/rest/api/maps/data/deletepreview) to delete old/unused content and create space for new uploads.",
+ "description": "The [data storage limit](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-maps-limits) is reached on the Azure Maps account. You can always use the [Data Delete API](https://docs.microsoft.com/rest/api/maps/data/deletepreview) to delete old/unused content and create space for new uploads.",
"schema": {
"$ref": "../../../../../common-types/data-plane/v1/types.json#/definitions/ErrorResponse"
},
diff --git a/specification/maps/data-plane/DEM/preview/1.0/elevation.json b/specification/maps/data-plane/DEM/preview/1.0/elevation.json
index 34562e06e61c..31ec76728752 100644
--- a/specification/maps/data-plane/DEM/preview/1.0/elevation.json
+++ b/specification/maps/data-plane/DEM/preview/1.0/elevation.json
@@ -18,7 +18,7 @@
"type": "oauth2",
"authorizationUrl": "https://login.microsoftonline.com/common/oauth2/authorize",
"flow": "implicit",
- "description": "These are the [Azure Active Directory OAuth2](https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-overview) Flows. When paired with [Azure role-based access](https://docs.microsoft.com/en-us/azure/role-based-access-control/overview) control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.\n\nTo implement scenarios, we recommend viewing [authentication concepts](https://aka.ms/amauth). In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.\n\n#### Notes\n* This security definition **requires** the use of the `x-ms-client-id` header to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the [Maps management API](https://aka.ms/amauthdetails).\n* \nThe `Authorization URL` is specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Azure Active directory configurations. \n* \nThe Azure role-based access control is configured from the [Azure management plane](https://aka.ms/amrbac) via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.\n* \nUsage of the [Azure Maps Web SDK](https://aka.ms/amaadmc) allows for configuration based setup of an application for multiple use cases.\n* Currently, Azure Active Directory [v1.0](https://docs.microsoft.com/en-us/azure/active-directory/develop/azure-ad-endpoint-comparison) tokens are supported.",
+ "description": "These are the [Azure Active Directory OAuth2](https://docs.microsoft.com/azure/active-directory/develop/v1-overview) Flows. When paired with [Azure role-based access](https://docs.microsoft.com/azure/role-based-access-control/overview) control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.\n\nTo implement scenarios, we recommend viewing [authentication concepts](https://aka.ms/amauth). In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.\n\n#### Notes\n* This security definition **requires** the use of the `x-ms-client-id` header to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the [Maps management API](https://aka.ms/amauthdetails).\n* \nThe `Authorization URL` is specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Azure Active directory configurations. \n* \nThe Azure role-based access control is configured from the [Azure management plane](https://aka.ms/amrbac) via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.\n* \nUsage of the [Azure Maps Web SDK](https://aka.ms/amaadmc) allows for configuration based setup of an application for multiple use cases.\n* Currently, Azure Active Directory [v1.0](https://docs.microsoft.com/azure/active-directory/develop/azure-ad-endpoint-comparison) tokens are supported.",
"scopes": {
"https://atlas.microsoft.com/.default": "https://atlas.microsoft.com/.default"
}
@@ -56,10 +56,10 @@
"/elevation/point/{format}": {
"get": {
"summary": "Get Elevation Data on One or More Points",
- "description": "**Applies to**: S1 pricing tier.\n\nThe Get Data for Points API provides elevation data for one or more points. A point is defined in lat,long coordinate format.\n\n Due to the URL character length limit of 2048, it's not possible to pass more than 100 coordinates as a pipeline delimited string in a URL GET request. If you intend to pass more than 100 coordinates as a pipeline delimited string, use the [POST Data\n For Points](https://docs.microsoft.com/en-us/rest/api/maps/elevation/postdataforpoints).",
+ "description": "**Applies to**: S1 pricing tier.\n\n The Get Data for Points API provides elevation data for one or more points. A point is defined in lat,long coordinate format.\n\n Due to the URL character length limit of 2048, it's not possible to pass more than 100 coordinates as a pipeline delimited string in a URL GET request. If you intend to pass more than 100 coordinates as a pipeline delimited string, use the [POST Data\n For Points](https://docs.microsoft.com/rest/api/maps/elevation/postdataforpoints).\n\n The result will be in the same sequence of points listed in the request.",
"operationId": "GetDataForPoints",
"x-ms-examples": {
- "GetDataForPoints": {
+ "Successfully retrieve elevation data for one or more points using get": {
"$ref": "./examples/GetDataForPoints.json"
}
},
@@ -91,7 +91,7 @@
"200": {
"description": "OK",
"schema": {
- "$ref": "#/definitions/PointsResult"
+ "$ref": "#/definitions/ElevationResult"
}
},
"default": {
@@ -101,10 +101,10 @@
},
"post": {
"summary": "Query Elevation Data for Multiple Points",
- "description": "**Applies to**: S1 pricing tier.\n\nThe Post Data for Points API provides elevation data for multiple points. A point is defined lon/lat coordinate format. Use the POST endpoint only if you intend to pass multiple points in the request. If you intend to pass a single coordinate into the API, use the [GET Data For Points API](https://docs.microsoft.com/en-us/rest/api/maps/elevation/getdataforpoints).",
+ "description": "**Applies to**: S1 pricing tier.\n\n The Post Data for Points API provides elevation data for multiple points. A point is defined lon/lat coordinate format.\n\n Use the POST endpoint only if you intend to pass multiple points in the request. If you intend to pass a single coordinate into the API, use the [GET Data For Points API](https://docs.microsoft.com/rest/api/maps/elevation/getdataforpoints).\n\n The result will be in the same sequence of points listed in the request.",
"operationId": "PostDataForPoints",
"x-ms-examples": {
- "PostDataForPoints": {
+ "Successfully retrieve elevation data for multiple points using post": {
"$ref": "./examples/PostDataForPoints.json"
}
},
@@ -119,7 +119,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
},
{
- "name": "pointsRequestBody",
+ "name": "points",
"in": "body",
"description": "The string representation of a list of points. A point is defined in lon/lat WGS84 coordinate reference system format. Each points in a list should be separated by the pipe ('|') character. The number of points that can be requested in a POST request ranges from 2 to 2,000. The resolution of the elevation data will be the highest for a single point and will decrease if multiple points are spread further apart. ",
"required": true,
@@ -132,7 +132,7 @@
"200": {
"description": "OK",
"schema": {
- "$ref": "#/definitions/PointsResult"
+ "$ref": "#/definitions/ElevationResult"
}
},
"default": {
@@ -144,10 +144,10 @@
"/elevation/line/{format}": {
"get": {
"summary": "Get Elevation Data Along a Polyline",
- "description": "**Applies to**: S1 pricing tier.\n\nThe Get Data for Polyline API provides elevation data along a polyline.\n\n A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments. Elevation data at both start and endpoints and equally spaced points along the polyline will be returned.\n\n A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.",
+ "description": "**Applies to**: S1 pricing tier.\n\n The Get Data for Polyline API provides elevation data along a polyline.\n\n A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments.\n\n Elevation data at both start and endpoints, as well as equally spaced points along the polyline will be returned. The results will be listed in the direction from the first endpoint towards the last endpoint. A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.",
"operationId": "GetDataForPolyline",
"x-ms-examples": {
- "GetDataForPolyLine": {
+ "Successfully retrieve elevation data along a polyline using get": {
"$ref": "./examples/GetDataForPolyline.json"
}
},
@@ -187,7 +187,7 @@
"200": {
"description": "OK",
"schema": {
- "$ref": "#/definitions/LinesResult"
+ "$ref": "#/definitions/ElevationResult"
}
},
"default": {
@@ -197,10 +197,10 @@
},
"post": {
"summary": "Query Elevation Data Along a Polyline",
- "description": "**Applies to**: S1 pricing tier.\n\n The Post Data for Polyline API provides elevation data along a polyline. A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments.\n\n Elevation data at both start and end points and equally spaced points along the polyline will be returned. A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.",
+ "description": "**Applies to**: S1 pricing tier.\n\n The Post Data for Polyline API provides elevation data along a polyline.\n\n A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments.\n\n Elevation data at both start and end points, as well as equally spaced points along the polyline will be returned. The results will be listed in the direction from the first endpoint towards the last endpoint. A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.",
"operationId": "PostDataForPolyline",
"x-ms-examples": {
- "PostDataForPolyLine": {
+ "Successfully retrieve elevation data along a polyline using post": {
"$ref": "./examples/PostDataForPolyline.json"
}
},
@@ -215,7 +215,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
},
{
- "name": "linesRequestBody",
+ "name": "polyline",
"in": "body",
"description": "The string representation of a polyline path. A polyline is defined by endpoint coordinates, with each endpoint separated by a pipe ('|') character. The polyline should be defined in the following format: `[longitude_point1, latitude_point1 | longitude_point2, latitude_point2, ..., longitude_pointN, latitude_pointN]`. The longitude and latitude values refer to the World Geodetic System (WGS84) coordinate reference system. The resolution of the data used to compute the elevation will depend on the distance between the endpoints.",
"required": true,
@@ -236,7 +236,7 @@
"200": {
"description": "OK",
"schema": {
- "$ref": "#/definitions/LinesResult"
+ "$ref": "#/definitions/ElevationResult"
}
},
"default": {
@@ -251,7 +251,7 @@
"description": "**Applies to**: S1 pricing tier.\n\nThe Get Data for Bounding Box API provides elevation data at equally spaced locations within a bounding box. A bounding box is defined by the coordinates for two corners (southwest, northeast) and then subsequently divided into rows and columns.\n\n Elevations are returned for the vertices of the grid created by the rows and columns. Up to 2,000 elevations can be returned in a single request. The returned elevation values are ordered, starting at the southwest corner, and then proceeding west to east along the row. At the end of the row, it moves north to the next row, and repeats the process until it reaches the far northeast corner.",
"operationId": "GetDataForBoundingBox",
"x-ms-examples": {
- "GetDataForBoundingBox": {
+ "Successfully retrieve elevation data within a bounding box": {
"$ref": "./examples/GetDataForBoundingBox.json"
}
},
@@ -271,14 +271,18 @@
"description": "The string that represents the rectangular area of a bounding box. The bounds parameter is defined by the 4 bounding box coordinates, with WGS84 longitude and latitude of the southwest corner followed by WGS84 longitude and latitude of the northeast corner. The string is presented in the following format: `[SouthwestCorner_Longitude, SouthwestCorner_Latitude, NortheastCorner_Longitude, NortheastCorner_Latitude]`.",
"required": true,
"type": "array",
+ "collectionFormat": "csv",
+ "minItems": 4,
+ "maxItems": 4,
"items": {
- "type": "string"
+ "type": "number",
+ "format": "float"
}
},
{
"name": "rows",
"in": "query",
- "description": "Specifies the number of rows to use to divide the bounding box area into a grid. The number of vertices in the grid should be less than 2,000. ",
+ "description": "Specifies the number of rows to use to divide the bounding box area into a grid. The number of vertices (rows x columns) in the grid should be less than 2,000. ",
"type": "integer",
"minimum": 2,
"maximum": 1000,
@@ -287,7 +291,7 @@
{
"name": "columns",
"in": "query",
- "description": "Specifies the number of columns to use to divide the bounding box area into a grid. The number of vertices in the grid should be less than 2,000. ",
+ "description": "Specifies the number of columns to use to divide the bounding box area into a grid. The number of vertices (rows x columns) in the grid should be less than 2,000. ",
"type": "integer",
"minimum": 2,
"maximum": 1000,
@@ -298,7 +302,7 @@
"200": {
"description": "OK",
"schema": {
- "$ref": "#/definitions/BoundingBoxResult"
+ "$ref": "#/definitions/ElevationResult"
}
},
"default": {
@@ -309,20 +313,20 @@
}
},
"definitions": {
- "ElevationPointResponse": {
+ "ElevationArray": {
"description": "The response for point/points elevation API. The result will be in same sequence of points listed in request.",
"type": "array",
"readOnly": true,
"items": {
- "$ref": "#/definitions/PointElevationResult"
+ "$ref": "#/definitions/Elevation"
}
},
- "PointElevationResult": {
+ "Elevation": {
"type": "object",
"description": "The elevation data.",
"properties": {
"coordinate": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
},
"elevationInMeter": {
"description": "The elevation value in meters.",
@@ -331,46 +335,13 @@
}
}
},
- "ElevationLineResponse": {
- "description": "The response from the Get Data for Polyline API. The results will be listed in the direction from the first endpoint towards the last endpoint.",
- "type": "array",
- "readOnly": true,
- "items": {
- "$ref": "#/definitions/PointElevationResult"
- }
- },
- "ElevationLatticeResponse": {
- "description": "The response from the Get Data for Bounding Box API. The results are ordered starting with the southwest corner, and then proceed west to east and south to north.",
- "type": "array",
- "readOnly": true,
- "items": {
- "$ref": "#/definitions/PointElevationResult"
- }
- },
- "PointsResult": {
- "type": "object",
- "description": "The response from a successful Elevation Points request.",
- "properties": {
- "data": {
- "$ref": "#/definitions/ElevationPointResponse"
- }
- }
- },
- "LinesResult": {
- "type": "object",
- "description": "The response from a successful Elevation Polyline request.",
- "properties": {
- "data": {
- "$ref": "#/definitions/ElevationLineResponse"
- }
- }
- },
- "BoundingBoxResult": {
+ "ElevationResult": {
"type": "object",
"description": "The response from a successful Get Data for Bounding Box API.",
"properties": {
"data": {
- "$ref": "#/definitions/ElevationLatticeResponse"
+ "x-ms-client-name": "elevations",
+ "$ref": "#/definitions/ElevationArray"
}
}
},
@@ -378,14 +349,14 @@
"type": "array",
"description": "The post elevation points array request body. The length of the array ranges from 2 to 2000.",
"items": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
},
"LinesInRequestBody": {
"type": "array",
"description": "The post elevation lines request body.",
"items": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
}
}
diff --git a/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPoints.json b/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPoints.json
index 61ab92e429b1..f5cca15a81ae 100644
--- a/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPoints.json
+++ b/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPoints.json
@@ -2,7 +2,7 @@
"parameters": {
"format": "json",
"api-version": "1.0",
- "pointsRequestBody": [
+ "points": [
{
"lon": -121.66853362143818,
"lat": 46.84646479863713
diff --git a/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPolyline.json b/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPolyline.json
index e1de6f13cbc5..b1be86350322 100644
--- a/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPolyline.json
+++ b/specification/maps/data-plane/DEM/preview/1.0/examples/PostDataForPolyline.json
@@ -2,7 +2,7 @@
"parameters": {
"format": "json",
"api-version": "1.0",
- "linesRequestBody": [
+ "polyline": [
{
"lon": -121.66853362143818,
"lat": 46.84646479863713
diff --git a/specification/maps/data-plane/Geolocation/preview/1.0/geolocation.json b/specification/maps/data-plane/Geolocation/preview/1.0/geolocation.json
index aa90387d93e7..602c6c8bf4a2 100644
--- a/specification/maps/data-plane/Geolocation/preview/1.0/geolocation.json
+++ b/specification/maps/data-plane/Geolocation/preview/1.0/geolocation.json
@@ -18,7 +18,7 @@
"type": "oauth2",
"authorizationUrl": "https://login.microsoftonline.com/common/oauth2/authorize",
"flow": "implicit",
- "description": "These are the [Azure Active Directory OAuth2](https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-overview) Flows. When paired with [Azure role-based access](https://docs.microsoft.com/en-us/azure/role-based-access-control/overview) control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.\n\nTo implement scenarios, we recommend viewing [authentication concepts](https://aka.ms/amauth). In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.\n\n#### Notes\n* This security definition **requires** the use of the `x-ms-client-id` header to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the [Maps management API](https://aka.ms/amauthdetails).\n* \nThe `Authorization URL` is specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Azure Active directory configurations. \n* \nThe Azure role-based access control is configured from the [Azure management plane](https://aka.ms/amrbac) via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.\n* \nUsage of the [Azure Maps Web SDK](https://aka.ms/amaadmc) allows for configuration based setup of an application for multiple use cases.\n* Currently, Azure Active Directory [v1.0](https://docs.microsoft.com/en-us/azure/active-directory/develop/azure-ad-endpoint-comparison) tokens are supported.",
+ "description": "These are the [Azure Active Directory OAuth2](https://docs.microsoft.com/azure/active-directory/develop/v1-overview) Flows. When paired with [Azure role-based access](https://docs.microsoft.com/azure/role-based-access-control/overview) control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.\n\nTo implement scenarios, we recommend viewing [authentication concepts](https://aka.ms/amauth). In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.\n\n#### Notes\n* This security definition **requires** the use of the `x-ms-client-id` header to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the [Maps management API](https://aka.ms/amauthdetails).\n* \nThe `Authorization URL` is specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Azure Active directory configurations. \n* \nThe Azure role-based access control is configured from the [Azure management plane](https://aka.ms/amrbac) via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.\n* \nUsage of the [Azure Maps Web SDK](https://aka.ms/amaadmc) allows for configuration based setup of an application for multiple use cases.\n* Currently, Azure Active Directory [v1.0](https://docs.microsoft.com/azure/active-directory/develop/azure-ad-endpoint-comparison) tokens are supported.",
"scopes": {
"https://atlas.microsoft.com/.default": "https://atlas.microsoft.com/.default"
}
diff --git a/specification/maps/data-plane/Route/preview/1.0/route.json b/specification/maps/data-plane/Route/preview/1.0/route.json
index a5771c613d6b..87a29b0487fd 100644
--- a/specification/maps/data-plane/Route/preview/1.0/route.json
+++ b/specification/maps/data-plane/Route/preview/1.0/route.json
@@ -1782,7 +1782,7 @@
"type": "array",
"readOnly": true,
"items": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
}
}
}
@@ -1976,7 +1976,7 @@
"readOnly": true
},
"point": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
},
"pointIndex": {
"description": "The index of the point in the list of polyline \"points\" corresponding to the point of the instruction.",
@@ -2387,14 +2387,14 @@
"properties": {
"center": {
"description": "Center point of the reachable range",
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
},
"boundary": {
"description": "Polygon boundary of the reachable range represented as a list of points.",
"type": "array",
"readOnly": true,
"items": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
}
}
}
diff --git a/specification/maps/data-plane/Search/preview/1.0/search.json b/specification/maps/data-plane/Search/preview/1.0/search.json
index 39fe49675dfd..6401c05e681b 100644
--- a/specification/maps/data-plane/Search/preview/1.0/search.json
+++ b/specification/maps/data-plane/Search/preview/1.0/search.json
@@ -123,13 +123,6 @@
"type": "number",
"x-ms-parameter-location": "method"
},
- "Language": {
- "name": "language",
- "in": "query",
- "description": "Language in which search results should be returned. Should be one of supported IETF language tags, case insensitive. When data in specified language is not available for a specific field, default language is used.\n\nPlease refer to [Supported Languages](https://docs.microsoft.com/en-us/azure/azure-maps/supported-languages) for details.",
- "type": "string",
- "x-ms-parameter-location": "method"
- },
"Query": {
"name": "query",
"in": "query",
@@ -146,13 +139,6 @@
"type": "string",
"x-ms-parameter-location": "method"
},
- "View": {
- "name": "view",
- "in": "query",
- "description": "The View parameter specifies which set of geopolitically disputed content is returned via Azure Maps services, including borders and labels displayed on the map. The View parameter (also referred to as “user region parameter”) will show the correct maps for that country/region. By default, the View parameter is set to “Unified” even if you haven’t defined it in the request. It is your responsibility to determine the location of your users, and then set the View parameter correctly for that location. Alternatively, you have the option to set ‘View=Auto’, which will return the map data based on the IP address of the request. The View parameter in Azure Maps must be used in compliance with applicable laws, including those regarding mapping, of the country where maps, images and other data and third party content that you are authorized to access via Azure Maps is made available. Example: view=IN.\n\nPlease refer to [Supported Views](https://aka.ms/AzureMapsLocalizationViews) for details and to see the available Views.",
- "type": "string",
- "x-ms-parameter-location": "method"
- },
"SearchIndexSet": {
"name": "idxSet",
"in": "query",
@@ -522,7 +508,7 @@
"$ref": "#/parameters/BoundingBoxBottomRight"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/ExtendedPostalCodesFor"
@@ -556,7 +542,7 @@
"$ref": "#/parameters/EntityType"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
},
{
"$ref": "#/parameters/OpeningHours"
@@ -632,7 +618,7 @@
"$ref": "#/parameters/BoundingBoxBottomRight"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/ExtendedPostalCodesForPoi"
@@ -644,7 +630,7 @@
"$ref": "#/parameters/ConnectorSet"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
},
{
"$ref": "#/parameters/OpeningHours"
@@ -707,7 +693,7 @@
"type": "number"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/ExtendedPostalCodesFor"
@@ -719,7 +705,7 @@
"$ref": "#/parameters/ConnectorSet"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
}
],
"responses": {
@@ -792,7 +778,7 @@
"$ref": "#/parameters/BoundingBoxBottomRight"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/ExtendedPostalCodesFor"
@@ -804,7 +790,7 @@
"$ref": "#/parameters/ConnectorSet"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
},
{
"$ref": "#/parameters/OpeningHours"
@@ -916,7 +902,7 @@
"$ref": "#/parameters/BoundingBoxBottomRight"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/ExtendedPostalCodesFor"
@@ -925,7 +911,7 @@
"$ref": "#/parameters/EntityType"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
}
],
"responses": {
@@ -964,7 +950,7 @@
"$ref": "#/parameters/Position"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"name": "returnSpeedLimit",
@@ -1017,7 +1003,7 @@
"$ref": "#/parameters/EntityType"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
}
],
"responses": {
@@ -1070,10 +1056,10 @@
"$ref": "#/parameters/Radius"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
}
],
"responses": {
@@ -1109,7 +1095,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ResponseFormat"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"name": "countryCode",
@@ -1185,7 +1171,7 @@
"$ref": "#/parameters/EntityType"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
}
],
"responses": {
@@ -1233,7 +1219,7 @@
"$ref": "#/parameters/LimitSearch"
},
{
- "$ref": "#/parameters/Language"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"$ref": "#/parameters/CategorySet"
@@ -1254,7 +1240,7 @@
}
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
},
{
"$ref": "#/parameters/OpeningHours"
@@ -1320,7 +1306,7 @@
"$ref": "#/parameters/ConnectorSet"
},
{
- "$ref": "#/parameters/View"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/View"
},
{
"$ref": "#/parameters/OpeningHours"
@@ -1851,7 +1837,7 @@
"readOnly": true,
"allOf": [
{
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
]
}
@@ -1893,7 +1879,7 @@
"$ref": "#/definitions/SearchResultAddress"
},
"position": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
},
"viewport": {
"$ref": "#/definitions/SearchResultViewport"
@@ -2352,10 +2338,10 @@
"readOnly": true,
"properties": {
"topLeftPoint": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
},
"btmRightPoint": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
}
},
@@ -2378,7 +2364,7 @@
}
},
"position": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
}
},
@@ -2396,10 +2382,10 @@
"type": "string"
},
"from": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
},
"to": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPairAbbreviated"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPairAbbreviated"
}
}
},
diff --git a/specification/maps/data-plane/Traffic/preview/1.0/traffic.json b/specification/maps/data-plane/Traffic/preview/1.0/traffic.json
index d87505a6d072..5eb6edc06de4 100644
--- a/specification/maps/data-plane/Traffic/preview/1.0/traffic.json
+++ b/specification/maps/data-plane/Traffic/preview/1.0/traffic.json
@@ -681,7 +681,7 @@
"type": "array",
"readOnly": true,
"items": {
- "$ref": "../../../Common/preview/1.0/common.json#/definitions/CoordinatesPair"
+ "$ref": "../../../Common/preview/1.0/common.json#/definitions/LatLongPair"
}
}
}
diff --git a/specification/maps/data-plane/Weather/preview/1.0/weather.json b/specification/maps/data-plane/Weather/preview/1.0/weather.json
index dab27658e75e..74831c73cc91 100644
--- a/specification/maps/data-plane/Weather/preview/1.0/weather.json
+++ b/specification/maps/data-plane/Weather/preview/1.0/weather.json
@@ -41,7 +41,7 @@
],
"responses": {},
"parameters": {
- "WeatherApiVersion": {
+ "ApiVersion": {
"name": "api-version",
"description": "Version number of Azure Maps API.",
"type": "string",
@@ -50,13 +50,6 @@
"default": "1.0",
"x-ms-parameter-location": "client"
},
- "WeatherLanguage": {
- "name": "language",
- "description": "Language in which search results should be returned. Should be one of supported IETF language tags, case insensitive. When data in specified language is not available for a specific field, default language is used. Default value is en-us. \n\nPlease refer to [Supported languages](https://docs.microsoft.com/azure/azure-maps/supported-languages) for details.",
- "type": "string",
- "in": "query",
- "x-ms-parameter-location": "method"
- },
"WeatherDataUnit": {
"name": "unit",
"description": "Specifies to return the data in either metric units or imperial units. Default value is metric.",
@@ -98,7 +91,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -120,7 +113,7 @@
"type": "integer"
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -150,7 +143,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -169,7 +162,7 @@
"type": "integer"
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -199,7 +192,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -221,7 +214,7 @@
"type": "integer"
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -251,7 +244,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -279,7 +272,7 @@
"type": "integer"
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -309,7 +302,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -331,7 +324,7 @@
"type": "integer"
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -361,7 +354,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -374,7 +367,7 @@
"required": true
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
}
],
"responses": {
@@ -404,7 +397,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -417,7 +410,7 @@
"required": true
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"name": "details",
@@ -453,7 +446,7 @@
"$ref": "../../../Common/preview/1.0/common.json#/parameters/ClientId"
},
{
- "$ref": "#/parameters/WeatherApiVersion"
+ "$ref": "#/parameters/ApiVersion"
},
{
"$ref": "../../../Common/preview/1.0/common.json#/parameters/JsonFormat"
@@ -466,7 +459,7 @@
"required": true
},
{
- "$ref": "#/parameters/WeatherLanguage"
+ "$ref": "../../../Common/preview/1.0/common.json#/parameters/Language"
},
{
"name": "duration",