Skip to content

Commit bcb1a8d

Browse files
authored
Update Traffic API references and links
Updated Traffic Incident v2025-01-01 and Get Map Tile link.
1 parent 5490d7f commit bcb1a8d

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,13 +26,13 @@ The following table outlines all Traffic services along with their respective mi
2626

2727
## Notable differences
2828

29-
- Unlike the Traffic v1.0 services, the latest Azure Maps [Traffic Incident] API and the Render services' [Get Map Tile] API don't require a traffic model ID.
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.
3030

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

3333
- [Traffic Flow Segment][Get Traffic Flow Segment] v1.0 provides information about vehicle speeds and travel times of the road segment. This information isn't available in the latest version, but the traffic data can be visualized using the Render [Get Map Tile] API.
3434

35-
- To assign an icon category to the points returned by [Traffic Incident] v2025-01-01, use the `incidentType` enum provided in the response.
35+
- To assign an icon category to the points returned by [Get Traffic Incident] v2025-01-01, use the `incidentType` enum provided in the response.
3636

3737
- Traffic map tiles are available in vector and raster format in the Render service using the [Get Map Tile] API.
3838

@@ -166,14 +166,13 @@ Content-Type: application/vnd.mapbox-vector-tile
166166

167167
"binary image string"
168168

169-
[Get Map Tile]: /rest/api/maps/render/get-map-tile?view=rest-maps-1.0
169+
[Get Map Tile]: /rest/api/maps/render/get-map-tile?view=rest-maps-2025-01-01
170170
[Get Traffic Flow Segment]: /rest/api/maps/traffic/get-traffic-flow-segment?view=rest-maps-1.0
171171
[Get Traffic Flow Tile]: /rest/api/maps/traffic/get-traffic-flow-tile#trafficflowtilestyle?view=rest-maps-1.0
172172
[Get Traffic Incident Detail]: /rest/api/maps/traffic/get-traffic-incident-detail?view=rest-maps-1.0
173173
[Get Traffic Incident]: /rest/api/maps/traffic/get-traffic-incident?view=rest-maps-2025-01-01
174174
[Get Traffic Incident Tile]: /rest/api/maps/traffic/get-traffic-incident-tile?view=rest-maps-1.0
175175
[Get Traffic Incident Viewport]: /rest/api/maps/traffic/get-traffic-incident-viewport?view=rest-maps-1.0
176176
[TilesetID]: /rest/api/maps/render/get-map-tile#tilesetid
177-
[Traffic Incident]: /rest/api/maps/traffic/incident
178177
[Traffic v1 service]: /rest/api/maps/traffic?view=rest-maps-1.0
179178
[Understanding Azure Maps Transactions]: /azure/azure-maps/understanding-azure-maps-transactions

0 commit comments

Comments
 (0)