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-traffic-v1-api.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,13 +26,13 @@ The following table outlines all Traffic services along with their respective mi
26
26
27
27
## Notable differences
28
28
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.
30
30
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.
32
32
33
33
-[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.
34
34
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.
36
36
37
37
- Traffic map tiles are available in vector and raster format in the Render service using the [Get Map Tile] API.
0 commit comments