Updated examples and added new billing information to the docs. (Azur…

…e#18093) Co-authored-by: Daniel Rocha <[email protected]>
AzureSDKAutomation · Mar 5, 2022 · ccbab5a · ccbab5a
1 parent d1df5ef
commit ccbab5a
Show file tree

Hide file tree

Showing 4 changed files with 27 additions and 9 deletions.
diff --git a/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficFlowSegment.json b/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficFlowSegment.json
@@ -4,7 +4,10 @@
     "format": "json",
     "style": "absolute",
     "zoom": 10,
-    "query": "52.41072,4.84239"
+    "query": [
+      52.41072,
+      4.84239
+    ]
   },
   "responses": {
     "200": {

diff --git a/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficIncidentDetail.json b/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficIncidentDetail.json
@@ -3,7 +3,12 @@
     "api-version": "1.0",
     "format": "json",
     "style": "s3",
-    "boundingbox": "6841263.950712,511972.674418,6886056.049288,582676.925582",
+    "boundingbox": [
+      6841263.950712,
+      511972.674418,
+      6886056.049288,
+      582676.925582
+    ],
     "boundingZoom": 11,
     "trafficmodelid": "1335294634919"
   },

diff --git a/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficIncidentViewport.json b/specification/maps/data-plane/Traffic/preview/1.0/examples/GetTrafficIncidentViewport.json
@@ -2,9 +2,19 @@
   "parameters": {
     "api-version": "1.0",
     "format": "json",
-    "boundingbox": "-939584.4813015489,-23954526.723651607,14675583.153020501,25043442.895825107",
+    "boundingbox": [
+      -939584.4813015489,
+      -23954526.723651607,
+      14675583.153020501,
+      25043442.895825107
+    ],
     "boundingzoom": 2,
-    "overviewbox": "-939584.4813018347,-23954526.723651607,14675583.153020501,25043442.8958229083",
+    "overviewbox": [
+      -939584.4813018347,
+      -23954526.723651607,
+      14675583.153020501,
+      25043442.8958229083
+    ],
     "overviewzoom": 2,
     "copyright": true
   },

diff --git a/specification/maps/data-plane/Traffic/preview/1.0/traffic.json b/specification/maps/data-plane/Traffic/preview/1.0/traffic.json
@@ -108,7 +108,7 @@
   "paths": {
     "/traffic/flow/tile/{format}": {
       "get": {
-        "description": "__Traffic Flow Tile__\n\n\n**Applies to**: S0 and S1 pricing tiers.\n\nThe Azure Flow Tile API serves 256 x 256 pixel tiles showing traffic flow. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound  display. The Flow tiles use colors to indicate either the speed of traffic on different road segments, or the difference between that speed and the free-flow speed on the road segment in question.",
+        "description": "__Traffic Flow Tile__\n\n\n**Applies to**: see pricing [tiers](https://aka.ms/AzureMapsPricingTier).\n\nThe Azure Flow Tile API serves 256 x 256 pixel tiles showing traffic flow. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound  display. The Flow tiles use colors to indicate either the speed of traffic on different road segments, or the difference between that speed and the free-flow speed on the road segment in question.",
         "operationId": "Traffic_GetTrafficFlowTile",
         "x-ms-examples": {
           "Request tile depicting the traffic flow": {
@@ -209,7 +209,7 @@
     },
     "/traffic/flow/segment/{format}": {
       "get": {
-        "description": "__Traffic Flow Segment__\n\n\n**Applies to**: S0 and S1 pricing tiers.\n\nThis service provides information about the speeds and travel times of the road fragment closest to the given coordinates. It is designed to work alongside the Flow layer of the Render Service to support clickable  flow data visualizations. With this API, the client side can connect any place in the map with flow data on the  closest road and present it to the user.",
+        "description": "__Traffic Flow Segment__\n\n\n**Applies to**: see pricing [tiers](https://aka.ms/AzureMapsPricingTier).\n\nThis service provides information about the speeds and travel times of the road fragment closest to the given coordinates. It is designed to work alongside the Flow layer of the Render Service to support clickable  flow data visualizations. With this API, the client side can connect any place in the map with flow data on the  closest road and present it to the user.",
         "operationId": "Traffic_GetTrafficFlowSegment",
         "x-ms-examples": {
           "Request traffic flow segment information": {
@@ -315,7 +315,7 @@
     },
     "/traffic/incident/tile/{format}": {
       "get": {
-        "description": "__Traffic Incident Tile__\n\n\n**Applies to**: S0 and S1 pricing tiers.\n\nThis service serves 256 x 256 pixel tiles showing traffic incidents. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. Traffic tiles render graphics to indicate traffic on the roads in the specified area.",
+        "description": "__Traffic Incident Tile__\n\n\n**Applies to**: see pricing [tiers](https://aka.ms/AzureMapsPricingTier).\n\nThis service serves 256 x 256 pixel tiles showing traffic incidents. All tiles use the same grid system. Because the traffic tiles use transparent images, they can be layered on top of map tiles to create a compound display. Traffic tiles render graphics to indicate traffic on the roads in the specified area.",
         "operationId": "Traffic_GetTrafficIncidentTile",
         "x-ms-examples": {
           "Request a tile depicting a traffic incident": {
@@ -414,7 +414,7 @@
     },
     "/traffic/incident/detail/{format}": {
       "get": {
-        "description": "__Traffic Incident Detail__ \n\n\n\n**Applies to**: S0 and S1 pricing tiers.\n\nThis API provides information on traffic incidents inside a given bounding box, based on the current Traffic  Model ID. The Traffic Model ID is available to grant synchronization of data between calls and API's. The  Traffic Model ID is a key value for determining the currency of traffic incidents. It is updated every minute,  and is valid for two minutes before it times out. It is used in rendering  [incident tiles](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidenttile). It can be  obtained from the [Viewport API](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidentviewport).",
+        "description": "__Traffic Incident Detail__ \n\n\n\n**Applies to**: see pricing [tiers](https://aka.ms/AzureMapsPricingTier).\n\nThis API provides information on traffic incidents inside a given bounding box, based on the current Traffic  Model ID. The Traffic Model ID is available to grant synchronization of data between calls and API's. The  Traffic Model ID is a key value for determining the currency of traffic incidents. It is updated every minute,  and is valid for two minutes before it times out. It is used in rendering  [incident tiles](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidenttile). It can be  obtained from the [Viewport API](https://docs.microsoft.com/en-us/rest/api/maps/traffic/gettrafficincidentviewport).",
         "operationId": "Traffic_GetTrafficIncidentDetail",
         "x-ms-examples": {
           "Request information about a traffic incident": {
@@ -579,7 +579,7 @@
     },
     "/traffic/incident/viewport/{format}": {
       "get": {
-        "description": "__Traffic Incident Viewport__\n\n\n**Applies to**: S0 and S1 pricing tiers.\n\nThis API returns legal and technical information for the viewport described in the request. It should be called  by client applications whenever the viewport changes (for instance, through zooming, panning, going to a  location, or displaying a route). The request should contain the bounding box and zoom level of the viewport  whose information is needed. The return will contain map version information, as well as the current Traffic  Model ID and copyright IDs. The Traffic Model ID returned by the Viewport Description is used by other APIs to  retrieve last traffic information for further processing.",
+        "description": "__Traffic Incident Viewport__\n\n\n**Applies to**: see pricing [tiers](https://aka.ms/AzureMapsPricingTier).\n\nThis API returns legal and technical information for the viewport described in the request. It should be called  by client applications whenever the viewport changes (for instance, through zooming, panning, going to a  location, or displaying a route). The request should contain the bounding box and zoom level of the viewport  whose information is needed. The return will contain map version information, as well as the current Traffic  Model ID and copyright IDs. The Traffic Model ID returned by the Viewport Description is used by other APIs to  retrieve last traffic information for further processing.",
         "operationId": "Traffic_GetTrafficIncidentViewport",
         "x-ms-examples": {
           "Request traffic incident information for the selected viewport": {