Skip to content

Commit da129f8

Browse files
authored
Fix typos in Azure Maps migration guide
Updated services to service where applicable.
1 parent bcb1a8d commit da129f8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-maps/migrate-traffic-v1-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,19 +14,19 @@ ms.subservice: rest-api
1414

1515
This article provides guidance on migrating the Azure Maps [Traffic v1 service] to other Azure Maps services.
1616

17-
The following table outlines all Traffic services along with their respective migration options.
17+
The following table outlines all Traffic service along with their respective migration options.
1818

1919
| Azure Maps Traffic v1.0 | Azure Maps migration option  |
2020
|-------------------------|------------------------------|
2121
| [Get Traffic Flow Segment] | No direct replacement.<br/>Map tiles can be used to visualize traffic flow, but speed and travel time isn't available. |
2222
| [Get Traffic Flow Tile]<br/>- Absolute <br/>- Reduced sensitivity <br/>- Relative <br/>- Relative delay  | [Get Map Tile]<br/>[TilesetID] <br/>- microsoft.traffic.absolute (vector) <br/>- microsoft.traffic.absolute.main (raster) <br/>- microsoft.traffic.relative (vector) <br/>- microsoft.traffic.relative.dark (raster) <br/>- microsoft.traffic.relative.main (raster) <br/>- microsoft.traffic.delay (vector) <br/>- microsoft.traffic.delay.main (raster) <br/>- microsoft.traffic.reduced.main (raster)  |
2323
| [Get Traffic Incident Detail] | [Get Traffic Incident]  |
2424
| [Get Traffic Incident Tile]| [Get Map Tile] <br/>[TilesetID] <br/>- microsoft.traffic.incident (vector)  |
25-
| [Get Traffic Incident Viewport] | No replacement.<br/>Returns the traffic model ID used by Traffic v1 services, but isn't required for unified traffic incident or render services. |
25+
| [Get Traffic Incident Viewport] | No replacement.<br/>Returns the traffic model ID used by Traffic v1 service, but isn't required for the latest traffic or render services. |
2626

2727
## Notable differences
2828

29-
- Unlike the Traffic v1.0 services, the latest Azure Maps [Get Traffic Incident] API and the Render services' [Get Map Tile] API don't require a traffic model ID.
29+
- Unlike the Traffic v1.0 service, the latest Azure Maps [Get Traffic Incident] API and the Render service [Get Map Tile] API don't require a traffic model ID.
3030

3131
- The [Get Traffic Incident] v2025-01-01 input bounding box and response are in the GeoJSON format.
3232

@@ -38,7 +38,7 @@ The following table outlines all Traffic services along with their respective mi
3838

3939
## Transactions usage
4040

41-
For information on how transactions are calculated for the Traffic Incident and Render services, see [Understanding Azure Maps Transactions].
41+
For information on how transactions are calculated for the Traffic and Render services, see [Understanding Azure Maps Transactions].
4242

4343
## Traffic service examples
4444

0 commit comments

Comments
 (0)