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
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-from-bing-maps-web-services.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,7 +393,6 @@ The `iconType` value specifies the type of pin to create and can have the follow
393
393
*`default` – The default pin icon.
394
394
*`none` – No icon is displayed, only labels are rendered.
395
395
*`custom` – Specifies a custom icon is to be used. A URL pointing to the icon image can be added to the end of the `pins` parameter after the pin location information.
396
-
*`{udid}` – A Unique Data ID (UDID) for an icon stored in the Azure Maps Data Storage platform.
397
396
398
397
Pin styles in Azure Maps are added with the format `optionNameValue`, with multiple styles separated by pipe (`|`) characters like this `iconType|optionName1Value1|optionName2Value2`. Note the option names and values aren't separated. The following style option names can be used to style pushpins in Azure Maps:
399
398
@@ -446,7 +445,7 @@ In Azure Maps, lines and polygons can also be added to a static map image by spe
When it comes to path locations, Azure Maps requires the coordinates to be in `longitude latitude` format whereas Bing Maps uses `latitude,longitude` format. Also note that **there is a space, not a comma separating** longitude and latitude in Azure Maps. Azure Maps doesn't support encoded paths currently. Larger data sets can be uploaded as a GeoJSON fills into the Azure Maps Data Storage API. For more information, see [Upload pins and path data](./how-to-render-custom-data.md#upload-pins-and-path-data).
448
+
When it comes to path locations, Azure Maps requires the coordinates to be in `longitude latitude` format whereas Bing Maps uses `latitude,longitude` format. Also note that **there is a space, not a comma separating** longitude and latitude in Azure Maps. Azure Maps doesn't support encoded paths currently.
450
449
451
450
Path styles in Azure Maps are added with the format `optionNameValue`, with multiple styles separated by pipe (`|`) characters like this `optionName1Value1|optionName2Value2`. Note the option names and values aren't separated. The following style option names can be used to style paths in Azure Maps:
Copy file name to clipboardExpand all lines: articles/azure-maps/migrate-from-google-maps-web-services.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -329,8 +329,6 @@ The `iconType` specifies the type of pin to create. It can have the following va
329
329
*`default` – The default pin icon.
330
330
*`none` – No icon is displayed, only labels are rendered.
331
331
*`custom` – Specifies a custom icon is to be used. A URL pointing to the icon image can be added to the end of the `pins` parameter after the pin location information.
332
-
*`{udid}` – A Unique Data ID (UDID) for an icon stored in the Azure
333
-
Maps Data Storage platform.
334
332
335
333
Add pin styles with the `optionNameValue` format. Separate multiple styles with the pipe (\|) characters. For example: `iconType|optionName1Value1|optionName2Value2`. The option names and values aren't separated. Use the following style option names to style markers:
336
334
@@ -398,7 +396,7 @@ Add lines and polygons to a static map image by specifying the `path` parameter
398
396
&path=pathStyles||pathLocation1|pathLocation2|...
399
397
```
400
398
401
-
When it comes to path locations, Azure Maps requires the coordinates to be in "longitude latitude" format. Google Maps uses "latitude,longitude" format. A space, not a comma, separates longitude and latitude in the Azure Maps format. Azure Maps doesn't support encoded paths or addresses for points. For more information on how to Upload larger data sets as a GeoJSON file into the Azure Maps Data Storage API, see [Upload pins and path data].
399
+
When it comes to path locations, Azure Maps requires the coordinates to be in "longitude latitude" format. Google Maps uses "latitude,longitude" format. A space, not a comma, separates longitude and latitude in the Azure Maps format. Azure Maps doesn't support encoded paths or addresses for points.
402
400
403
401
Add path styles with the `optionNameValue` format. Separate multiple styles by pipe (\|) characters, like this `optionName1Value1|optionName2Value2`. The option names and values aren't separated. Use the following style option names to style paths in Azure Maps:
404
402
@@ -543,4 +541,3 @@ Learn more about Azure Maps REST services:
543
541
[Time zone Windows to IANA]: /rest/api/maps/timezone/gettimezonewindowstoiana
544
542
[Time Zone]: /rest/api/maps/timezone
545
543
[Traffic]: /rest/api/maps/traffic
546
-
[Upload pins and path data]: how-to-render-custom-data.md#upload-pins-and-path-data
0 commit comments