You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| avoid || avoid | False | string | Here are the Bing Maps Calculate a Route API to Azure Maps Route Directions API avoid equivalents, where supported: <br><br>tolls: tollRoads<br>ferry: ferries<br>borderCrossings: borderCrossings<br>minimizeDrivingSideTurn: Not supported<br><br>minimizeAgainstDrivingSideTurn: Not supported<br>minimizeUTurn: Not supported<br>minimizeTolls: Not supported<br>highways: limitedAccessHighways<br>minimizeHighways: Not supported<br> |
43
43
| dateTime | dt | departAt | False | string | Azure Maps Route Directions API also supports arriveAt parameter that is used to specify the desired date and time of arrival. It can't be used with departAt.|
| avoid || avoid | False | string | Here are the Bing Maps to Azure Maps Route Directions API _avoid_ equivalents, where supported:<br><br>- tolls: tollRoads<br>- ferry: ferries<br>- borderCrossings: borderCrossings<br>- highways: limitedAccessHighways<br>- minimizeDrivingSideTurn: Not supported<br>- minimizeAgainstDrivingSideTurn: Not supported<br>- minimizeUTurn: Not supported <br>- minimizeTolls: Not supported<br>- minimizeHighways: Not supported |
42
42
| borderRestriction || Not supported | Not supported | Not supported | In Azure Maps Route Directions API, _avoid=borderCrossings_ can be used to restrict routes from crossing country borders however specifying a region list for border restriction isn't supported. |
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-address.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,22 +31,21 @@ This article explains how to migrate the Bing Maps [Find a Location by Address]
31
31
32
32
## Security and authentication
33
33
34
-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
34
+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Microsoft Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
35
35
36
36
## Request parameters
37
37
38
38
The following table lists the Bing Maps _Find a Location by Address_ request parameters and the Azure Maps equivalent:
| addressLine || addressLine | False | string | In Azure Maps Get Geocoding API, a street address, or street address with locality and `adminDistrict`, is supported input for `addressLine`. |
| culture | c | Request Header: Accept-Language | False | string | As specified in the Azure Maps [request header], `culture` defines the language used in search results when using the Azure Maps Get Geocoding API. For more information, see [Supported Languages]. |
49
-
|||||||
50
49
| include | incl | Not needed | Not needed | Not needed | In Bing Maps Find a Location by Address API, the ‘include’ input parameter is required in order to get a two-letter ISO country code for the location result in the response (_include=ciso2_). In Azure Maps Get Geocoding API, the two-letter ISO country code is returned by default. |
51
50
| includeNeighborhood | inclnb | Not needed | Not needed | Not needed | In Azure Maps Get Geocoding API, neighborhood info is returned in the response by default, when available. |
52
51
| maxResults | maxRes | top | False | Integer (int32) | In Azure Maps Get Geocoding API, the default number of responses returned is 5. The minimum is 1 and the maximum is 20. |
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-by-point.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,23 +30,20 @@ This article explains how to migrate the Bing Maps [Find a Location by Point] AP
30
30
31
31
## Security and authentication
32
32
33
-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
33
+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Microsoft Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
34
34
35
35
## Request parameters
36
36
37
37
The following table lists the Bing Maps _Find a Location by Point_ request parameters and the Azure Maps equivalent:
| culture | c | Request Header: Accept-Language | False | string | In Azure Maps Get Reverse Geocoding API, this is the language in which search results should be returned. This is specified in the Azure Maps [request header]. Please refer to [Supported Languages] for details. |
42
-
|||||||
43
42
| include | incl | Not needed | Not needed | Not needed | In Bing Maps Find a Location by Point, the ‘include’ input parameter is required to get a two-letter ISO country code for the location result in the response. In Azure Maps Get Reverse Geocoding API, the two-letter ISO country code is returned by default. |
| includeNeighborhood | inclnb | Not needed | Not needed | Not needed | In Azure Maps Get Reverse Geocoding API, neighborhood info is returned in the response by default, when available. |
47
45
| point || coordinates | True | number[]| In Bing Maps Find a Location by Point API, the coordinates in the request and the response are in latitude/longitude format, whereas Azure Maps Get Reverse Geocoding API requires the coordinates in the request and the coordinates in the response use longitude/latitude format, as defined by [GeoJSON]. |
48
-
| userRegion | ur | view | False | string | A string that represents an [ISO 3166-1 Alpha-2 region/country code]. This will alter geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request. |
49
-
|||||| Please refer to [Supported Views] for details and to see the available Views. |
46
+
| userRegion | ur | view | False | string | A string that represents an [ISO 3166-1 Alpha-2 region/country code]. This will alter geopolitical disputed borders and labels to align with the specified user region. By default, the View parameter is set to “Auto” even if you haven’t defined it in the request.<br><br> Please refer to [Supported Views] for details and to see the available Views. |
50
47
| verboseplacenames | vbpn | Not supported | Not supported | Not supported | Azure Maps Get Reverse Geocoding API only supports returning [adminDistricts] short name (FL instead of Florida). |
51
48
52
49
For more information about the Azure Maps Get Reverse Geocoding API request parameters, see [URI Parameters].
The following table lists the fields that can appear in the HTTP response when running the Bing Maps _Find a Location by Point_ request and the Azure Maps equivalent:
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-find-location-query.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,17 +31,16 @@ This article explains how to migrate the Bing Maps [Find a Location by Query] AP
31
31
32
32
## Security and authentication
33
33
34
-
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Azure Maps].
34
+
Bing Maps for Enterprise only supports API key authentication. Azure Maps supports multiple ways to authenticate your API calls, such as a [subscription key](azure-maps-authentication.md#shared-key-authentication), [Microsoft Entra ID], and [Shared Access Signature (SAS) Token]. For more information on security and authentication in Azure Maps, See [Authentication with Microsoft Azure Maps] and the [Security section] in the Azure Maps Get Geocoding documentation.
35
35
36
36
## Request parameters
37
37
38
38
The following table lists the Bing Maps _Find a Location by Query_ request parameters and the Azure Maps equivalent:
| culture | c | Request Header: Accept-Language | False | string | As specified in the Azure Maps [request header], `culture` defines the language used in search results when using the Azure Maps Get Geocoding API. For more information, see [Supported Languages].|
43
43
| include | incl | Not needed | Not needed | Not needed | In Bing Maps Find a Location by Query API, the `include` input parameter is required to get a two-letter ISO country code for the location result in the response (_include=ciso2_) and to specify that the response shows how the query string was parsed into address values (_include=queryParse_). In Azure Maps Get Geocoding API, the two-letter ISO country code is returned by default and doesn’t support a queryParse equivalent. |
44
-
||| Not supported | Not supported | Not supported ||
45
44
| includeNeighborhood | inclnb | Not needed | Not needed | Not needed | In Azure Maps Get Geocoding API, neighborhood info is returned in the response by default, when available. |
46
45
| maxResults | maxRes | top | False | Integer (int32) | In Azure Maps Get Geocoding API, the default number of responses returned is 5. The minimum is 1 and the maximum is 20. |
| dateTime | dt | timeStamp | False | string date-time | Alternatively, use alias "stamp", or "s". Reference time, if omitted, the API uses the machine time serving the request. |
42
42
| IncludeDstRules | None | transitionsFrom | False | string date-time | The start date from which daylight savings time (DST) transitions are requested, only applies when "options" = all or "options" = transitions. See options (Timezone Options) parameter for more info. |
0 commit comments