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-google-maps-web-services.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,7 +298,7 @@ Add markers to a static map image by specifying the `pins` parameter in the URL.
298
298
299
299
To use additional styles, add additional `pins` parameters to the URL with a different style and set of locations.
300
300
301
-
For the pin location, 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.
301
+
In Azure Maps, the pin location needs to be in the "longitude latitude" format. Google Maps uses "latitude,longitude" format. A space, not a comma, separates longitude and latitude in the Azure Maps format.
302
302
303
303
The `iconType` specifies the type of pin to create. It can have the following values:
304
304
@@ -308,20 +308,20 @@ The `iconType` specifies the type of pin to create. It can have the following va
308
308
-`{udid}` – A Unique Data ID (UDID) for an icon stored in the Azure
309
309
Maps Data Storage platform.
310
310
311
-
Add pin styles in Azure Maps 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 in Azure Maps:
311
+
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:
312
312
313
313
-`al` – Specifies the opacity (alpha) of the marker. Choose a number between 0 and 1.
314
-
-`an` – Specifies the pin anchor. X and y pixel values specified in the format "x y".
315
-
-`co` – The color of the pin. Must be a 24-bit hex color: `000000` to `FFFFFF`.
316
-
-`la` – Specifies the label anchor. X and y pixel values specified in the format "x y".
317
-
-`lc` – The color of the label. Must be a 24-bit hex color: `000000` to `FFFFFF`.
314
+
-`an` – Specifies the pin anchor. Specify X and y pixel values in the "x y" format.
315
+
-`co` – The color of the pin. Specify a 24-bit hex color: `000000` to `FFFFFF`.
316
+
-`la` – Specifies the label anchor. Specify X and y pixel values in the "x y" format.
317
+
-`lc` – The color of the label. Specify a 24-bit hex color: `000000` to `FFFFFF`.
318
318
-`ls` – The size of the label in pixels. Choose a number greater than 0.
319
319
-`ro` – A value in degrees to rotate the icon. Choose a number between -360 and 360.
320
320
-`sc` – A scale value for the pin icon. Choose a number greater than 0.
321
321
322
-
Label values are specified for each pin location. This approach is more efficient than applying a single label value to all markers in the list of locations. The label value can be a string of multiple characters. Wrap the string with single quotes to ensure that it isn’t mistaken as a style or location value.
322
+
Specify label values for each pin location. This approach is more efficient than applying a single label value to all markers in the list of locations. The label value can be a string of multiple characters. Wrap the string with single quotes to ensure that it isn’t mistaken as a style or location value.
323
323
324
-
For example, in Azure Maps, adding a red (`FF0000`) default icon, with the label "Space Needle", positioned below (15 50), with icon at coordinates (longitude: -122.349300, latitude: 47.620180) is done with the following URL parameter:
324
+
Let's add a red (`FF0000`) default icon, with the label "Space Needle", positioned below (15 50). The icon is at longitude: -122.349300, latitude: 47.620180:
@@ -345,24 +345,24 @@ The following example adds three pins with the label values '1', '2', and '3':
345
345
346
346
**Before: Google Maps**
347
347
348
-
In Google Maps, lines and polygons can be added to a static map image using the `path` parameter in the URL. The `path` parameter takes in a style and a list of locations to be rendered on the map, as shown below:
348
+
Add lines and polygon to a static map image using the `path` parameter in the URL. The `path` parameter takes in a style and a list of locations to be rendered on the map, as shown below:
349
349
350
350
```
351
351
&path=pathStyles|pathLocation1|pathLocation2|...
352
352
```
353
353
354
-
Additional styles can be used by adding additional `path` parameters to the URL with a different style and set of locations.
354
+
Use additional styles by adding additional `path` parameters to the URL with a different style and set of locations.
355
355
356
-
Path locations in Google Maps are specified with the format `latitude1,longitude1|latitude2,longitude2|…`. Paths can be encoded or contain addresses for points.
356
+
Path locations are specified with the `latitude1,longitude1|latitude2,longitude2|…` format. Paths can be encoded or contain addresses for points.
357
357
358
-
Path styles in Google Maps are added with the format `optionName:value`, with multiple styles separated by pipe (\|) characters. Like this: `optionName1:value1|optionName2:value2`. Note the option names and values are separated with a colon (:). The following style option names can be used to style paths in Google Maps:
358
+
Add path styles with the `optionName:value` format, separate multiple styles by the pipe (\|) characters. And, separate option names and values with a colon (:). Like this: `optionName1:value1|optionName2:value2`. The following style option names can be used to style paths in Google Maps:
359
359
360
360
-`color` – The color of the path or polygon outline. Can be a 24-bit hex color (`0xrrggbb`), a 32-bit hex color (`0xrrggbbbaa`) or one of the following values: black, brown, green, purple, yellow, blue, gray, orange, red, white.
361
361
-`fillColor` – The color to fill the path area with (polygon). Can be a 24-bit hex color (`0xrrggbb`), a 32-bit hex color (`0xrrggbbbaa`) or one of the following values: black, brown, green, purple, yellow, blue, gray, orange, red, white.
362
362
-`geodesic` – Indicates if the path should be a line that follows the curvature of the earth.
363
363
-`weight` – The thickness of the path line in pixels.
364
364
365
-
In Google Maps, a red line opacity and pixel thickness can be added to the map between the coordinates, in the URL parameter. For the example below, the line has a 50% opacity and a thickness of four pixels. The coordinates are longitude: -110, latitude: 45 and longitude: -100, latitude: 50.
365
+
Add a red line opacity and pixel thickness to the map between the coordinates, in the URL parameter. For the example below, the line has a 50% opacity and a thickness of four pixels. The coordinates are longitude: -110, latitude: 45 and longitude: -100, latitude: 50.
366
366
367
367
```
368
368
&path=color:0xFF000088|weight:4|45,-110|50,-100
@@ -374,15 +374,15 @@ In Google Maps, a red line opacity and pixel thickness can be added to the map b
374
374
375
375
**After: Azure Maps**
376
376
377
-
In Azure Maps, add lines and polygons to a static map image by specifying the `path` parameter in the URL. Like Google Maps, specify a style and a list of locations in this parameter. Specify the `path` parameter multiple times to render multiple circles, lines, and polygons with different styles.
377
+
Add lines and polygons to a static map image by specifying the `path` parameter in the URL. Like Google Maps, specify a style and a list of locations in this parameter. Specify the `path` parameter multiple times to render multiple circles, lines, and polygons with different styles.
378
378
379
379
```
380
380
&path=pathStyles||pathLocation1|pathLocation2|...
381
381
```
382
382
383
-
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. Upload larger data sets as a GeoJSON fills into the Azure Maps Data Storage API as documented [here](how-to-render-custom-data.md#get-data-from-azure-maps-data-storage).
383
+
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. Upload larger data sets as a GeoJSON file into the Azure Maps Data Storage API as documented [here](how-to-render-custom-data.md#get-data-from-azure-maps-data-storage).
384
384
385
-
In Azure Maps, 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:
385
+
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:
386
386
387
387
-`fa` - The fill color opacity (alpha) used when rendering polygons. Choose a number between 0 and 1.
388
388
-`fc` - The fill color used to render the area of a polygon.
@@ -391,7 +391,7 @@ In Azure Maps, add path styles with the `optionNameValue` format. Separate multi
391
391
-`lw` – The width of the line in pixels.
392
392
-`ra` – Specifies a circles radius in meters.
393
393
394
-
In Azure Maps, add a red line opacity and pixel thickness between the coordinates, in the URL parameter. For the example below, the line has 50% opacity and a thickness of four pixels. The coordinates have the following values: longitude: -110, latitude: 45 and longitude: -100, latitude: 50.
394
+
Add a red line opacity and pixel thickness between the coordinates, in the URL parameter. For the example below, the line has 50% opacity and a thickness of four pixels. The coordinates have the following values: longitude: -110, latitude: 45 and longitude: -100, latitude: 50.
395
395
396
396
```
397
397
&path=lcFF0000|la.5|lw4||-110 45|-100 50
@@ -405,12 +405,12 @@ In Azure Maps, add a red line opacity and pixel thickness between the coordinate
405
405
406
406
Azure Maps provides the distance matrix API. Use this API to calculate the travel times and the distances between a set of locations, with a distance matrix. It's comparable to the distance matrix API in Google Maps.
407
407
408
-
-[**Route matrix**](https://docs.microsoft.com/rest/api/maps/route/postroutematrixpreview): Asynchronously calculates travel times and distances for a set of origins and destinations. Supports up to 700 cells per request (the number of origins multiplied by the number of destinations. With that constraint in mind, examples of possible matrix dimensions are: 700x1, 50x10, 10x10, 28x25, 10x70.
408
+
-[**Route matrix**](https://docs.microsoft.com/rest/api/maps/route/postroutematrixpreview): Asynchronously calculates travel times and distances for a set of origins and destinations. Supports up to 700 cells per request. That's the number of origins multiplied by the number of destinations. With that constraint in mind, examples of possible matrix dimensions are: 700x1, 50x10, 10x10, 28x25, 10x70.
409
409
410
410
> [!NOTE]
411
411
> A request to the distance matrix API can only be made using a POST request with the origin and destination information in the body of the request. Additionally, Azure Maps requires all origins and destinations to be coordinates. Addresses will need to be geocoded first.
412
412
413
-
The following table cross-references the Google Maps API parameters with the comparable Azure Maps API parameters.
413
+
This table cross-references the Google Maps API parameters with the comparable Azure Maps API parameters.
414
414
415
415
| Google Maps API parameter | Comparable Azure Maps API parameter |
@@ -429,15 +429,15 @@ The following table cross-references the Google Maps API parameters with the com
429
429
|`units`|*N/A* – Azure Maps only uses the metric system. |
430
430
431
431
> [!TIP]
432
-
> All the advanced routing options available in the Azure Maps routing API are supported in the Azure Maps distance matrix API. Advanced routing options include: ruck routing, engine specifications, and so on.
432
+
> All the advanced routing options available in the Azure Maps routing API are supported in the Azure Maps distance matrix API. Advanced routing options include: truck routing, engine specifications, and so on.
433
433
434
434
## Get a time zone
435
435
436
436
Azure Maps provides an API for retrieving the time zone of a coordinate. The Azure Maps time zone API is comparable to the time zone API in Google Maps:
437
437
438
438
-[**Time zone by coordinate**](https://docs.microsoft.com/rest/api/maps/timezone/gettimezonebycoordinates): Specify a coordinate and receive the time zone details of the coordinate.
439
439
440
-
The following table cross-references the Google Maps API parameters with the comparable API parameters in Azure Maps.
440
+
This table cross-references the Google Maps API parameters with the comparable API parameters in Azure Maps.
441
441
442
442
| Google Maps API parameter | Comparable Azure Maps API parameter |
@@ -446,7 +446,7 @@ The following table cross-references the Google Maps API parameters with the com
446
446
|`location`|`query`|
447
447
|`timestamp`|`timeStamp`|
448
448
449
-
In addition to this API, the Azure Maps platform provides a number of time zone APIs. These APIs convert the time based on the names or the IDs of the time zone:
449
+
In addition to this Time zone by coordinate API, Azure Maps provides a number of time zone APIs. These APIs convert the time based on the names or the IDs of the time zone:
450
450
451
451
-[**Time zone by ID**](https://docs.microsoft.com/rest/api/maps/timezone/gettimezonebyid): Returns current, historical, and future time zone information for the specified IANA time zone ID.
452
452
-[**Time zone Enum IANA**](https://docs.microsoft.com/rest/api/maps/timezone/gettimezoneenumiana): Returns a full list of IANA time zone IDs. Updates to the IANA service are reflected in the system within one day.
@@ -460,13 +460,13 @@ Azure Maps provides client libraries for the following programming languages:
0 commit comments