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
The following service APIs aren't currently available in Azure Maps:
43
43
@@ -264,7 +264,7 @@ There are several ways to snap coordinates to roads in Azure Maps.
264
264
265
265
**Using the route direction API to snap coordinates**
266
266
267
-
Azure Maps can snap coordinates to roads by using the [route directions] API. This service can be used to reconstruct a logical route between a set of coordinates and is comparable to the Bing Maps Snap to Road API.
267
+
Azure Maps can snap coordinates to roads by using the [Get Route Directions] API. This service can be used to reconstruct a logical route between a set of coordinates and is comparable to the Bing Maps Snap to Road API.
268
268
269
269
There are two different ways to use the route directions API to snap coordinates to roads.
270
270
@@ -359,7 +359,7 @@ For more information, see [Render custom data on a raster map].
359
359
360
360
In addition to being able to generate a static map image, the Azure Maps render service also enables direct access to map tiles in raster (PNG) and vector format:
361
361
362
-
*[Map tiles] – Retrieve raster (PNG) and vector tiles for the base maps (roads, boundaries, background).
362
+
*[Get Map Static Image] – Retrieve raster (PNG) and vector tiles for the base maps (roads, boundaries, background).
363
363
*[Get Map Tile] – Retrieve aerial and satellite imagery tiles.
364
364
365
365
### Pushpin URL parameter format comparison
@@ -467,7 +467,7 @@ For example, in Azure Maps, a blue line with 50% opacity and a thickness of four
467
467
468
468
Azure Maps provides an API for calculating the travel times and distances between a set of locations as a distance matrix. The Azure Maps distance matrix API is comparable to the distance matrix API in Bing Maps:
469
469
470
-
*[Route matrix]: Asynchronously calculates travel times and distances for a set of origins and destinations. Up to 700 cells per request is supported (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`.
470
+
*[Post Route Matrix]: Asynchronously calculates travel times and distances for a set of origins and destinations. Up to 700 cells per request is supported (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`.
471
471
472
472
> [!NOTE]
473
473
> 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.
@@ -678,7 +678,6 @@ Learn more about the Azure Maps REST services.
0 commit comments