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
|[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. |
26
26
27
27
## Notable differences
28
28
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.
30
30
31
31
- The [Get Traffic Incident] v2025-01-01 input bounding box and response are in the GeoJSON format.
32
32
@@ -38,7 +38,7 @@ The following table outlines all Traffic services along with their respective mi
38
38
39
39
## Transactions usage
40
40
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].
0 commit comments