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
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ The following table cross-references the Google Maps API parameters with the com
70
70
An example of how to use the search service is documented [here](how-to-search-for-address.md). Be sure to review [best practices for search](how-to-use-best-practices-for-search.md).
71
71
72
72
> [!TIP]
73
-
> The free-form address geocoding and fuzzy search APIs can be used in autocomplete mode by adding `&typeahead=true` to the request URL. This will tell the server that the input text is likely partial, and the search will go into predictive mode.
73
+
> The free-form address geocoding and fuzzy search APIs can be used in autocomplete mode by adding `&typeahead=true` to the request URL. This will tell the server that the input text is likely partial, and the search will go into predictive mode.
74
74
75
75
## Reverse geocode a coordinate
76
76
@@ -121,7 +121,7 @@ Azure Maps provides several search APIs for points of interest:
121
121
Currently Azure Maps doesn't have a comparable API to the Text Search API in Google Maps.
122
122
123
123
> [!TIP]
124
-
> The POI search, POI category search, and fuzzy search APIs can be used in autocomplete mode by adding `&typeahead=true` to the request URL. This will tell the server that the input text is likely partial.The API will conduct the search in predictive mode.
124
+
> The POI search, POI category search, and fuzzy search APIs can be used in autocomplete mode by adding `&typeahead=true` to the request URL. This will tell the server that the input text is likely partial.The API will conduct the search in predictive mode.
125
125
126
126
Review the [best practices for search](how-to-use-best-practices-for-search.md) documentation.
127
127
@@ -217,6 +217,8 @@ Azure Maps routing API has additional features, that aren't available in Google
217
217
218
218
In addition to this, the route service in Azure Maps supports [calculating routable ranges](https://docs.microsoft.com/rest/api/maps/route/getrouterange). Calculating routable ranges is also known as isochrones. It entails generating a polygon covering an area that can be traveled to in any direction from an origin point. All under a specified amount of time or amount of fuel or charge.
219
219
220
+
Review the [best practices for routing](how-to-use-best-practices-for-routing.md) documentation.
221
+
220
222
## Retrieve a map image
221
223
222
224
Azure Maps provides an API for rendering the static map images with data overlaid. The [Map image render](https://docs.microsoft.com/rest/api/maps/render/getmapimagerytile) API in Azure Maps is comparable to the static map API in Google Maps.
@@ -434,6 +436,8 @@ This table cross-references the Google Maps API parameters with the comparable A
434
436
> [!TIP]
435
437
> 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.
436
438
439
+
Review the [best practices for routing](how-to-use-best-practices-for-routing.md) documentation.
440
+
437
441
## Get a time zone
438
442
439
443
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:
@@ -473,6 +477,7 @@ The following are additional documentation and resources for the Azure Maps REST
473
477
474
478
-[Best practices for search](how-to-use-best-practices-for-search.md)
475
479
-[Search for an address](how-to-search-for-address.md)
480
+
-[Best practices for routing](how-to-use-best-practices-for-routing.md)
476
481
-[Azure Maps REST Service API reference documentation](https://docs.microsoft.com/rest/api/maps/)
477
482
478
483
## Next steps
@@ -483,7 +488,10 @@ Learn more about the Azure Maps REST services.
483
488
> [Best practices for using the search service](how-to-use-best-practices-for-search.md)
484
489
485
490
> [!div class="nextstepaction"]
486
-
> [How to use the services module (Web SDK)](how-to-use-services-module.md)
491
+
> [Best practices for using the routing service](how-to-use-best-practices-for-search.md)
492
+
493
+
> [!div class="nextstepaction"]
494
+
> [How to use the services module (Web SDK)](how-to-use-best-practices-for-routing.md)
0 commit comments