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
1. Execute the following **HTTP GET request** (replace {routesetId} with the routesetId obtained in the [Check the routeset creation status](#check-the-routeset-creation-status-and-retrieve-the-routesetid) section and the {facilityId} with the facilityId obtained in the [Get the facility ID](#get-the-facility-id) section):
1. Set `Content-Type` in the **Header** to `application/zip`.
@@ -60,7 +60,7 @@ To check the status of the GeoJSON package and retrieve its unique identifier (`
60
60
1. Execute the following HTTP GET request that uses the status URL you copied as the last step in the previous section of this article. The request should look like the following URL:
1. Copy the value of the `Resource-Location` key in the response header, which is the `resource location URL`. The `resource location URL` contains the unique identifier (`udid`) of the GeoJSON package resource.
@@ -79,7 +79,7 @@ To create a dataset:
79
79
<!--1. Enter the following URL to the [Dataset service][Dataset Create 2022-09-01-preview]. The request should look like the following URL (replace {udid} with the `udid` obtained in [Check the GeoJSON package upload status](#check-the-geojson-package-upload-status) section):-->
1. Copy the value of the `Operation-Location` key in the response header. The `Operation-Location` key is also known as the `status URL` and is required to check the status of the dataset creation process and to get the `datasetId`, which is required to create a tileset.
@@ -91,7 +91,7 @@ To check the status of the dataset creation process and retrieve the `datasetId`
91
91
1. Enter the status URL you copied in [Create a dataset](#create-a-dataset). The request should look like the following URL:
@@ -181,7 +181,7 @@ To check the status of the data upload and retrieve its unique ID (`udid`):
181
181
5. Enter the `status URL` you copied in [Upload pins and path data](#upload-pins-and-path-data). The request should look like the following URL (replace {`Your-Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
@@ -207,7 +207,7 @@ To render the uploaded pins and path data on the map:
207
207
5. Enter the following URL to the [Render Service](/rest/api/maps/render/get-map-image) (replace {`Your-Azure-Maps-Primary-Subscription-key}` with your primary subscription key and `udid` with the `udid` of the uploaded data):
@@ -262,7 +262,7 @@ To render a circle and pushpins with custom labels:
262
262
5. Enter the following URL to the [Render Service](/rest/api/maps/render/get-map-image) (replace {`Your-Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
@@ -274,7 +274,7 @@ To render a circle and pushpins with custom labels:
274
274
8. Now we'll change the color of the pushpins by modifying the `co` style modifier. If you look at the value of the `pins` parameter (`pins=default|la15+50|al0.66|lc003C62|co002D62|`), you'll see that the current color is `#002D62`. To change the color to `#41d42a`, we'll replace `#002D62` with `#41d42a`. Now the `pins` parameter is `pins=default|la15+50|al0.66|lc003C62|co41D42A|`. The request looks like the following URL:
4. On the **Builder** tab, select the **GET** HTTP method, and then enter the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
5. Select the **Send** button. You'll receive the following JSON response:
@@ -110,7 +110,7 @@ To create the request:
110
110
6. Now, we'll call the [Post Data for Points API](/rest/api/maps/elevation/postdataforpoints) to get elevation data for the same two points. On the **Builder** tab, select the **POST** HTTP method and then enter the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
7. In the **Headers** field of the **POST** request, set `Content-Type` to `application/json`.
@@ -156,7 +156,7 @@ To create the request:
156
156
4. On the **Builder** tab, select the **GET** HTTP method, and then enter the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
5. Select the **Send** button. You'll receive the following JSON response:
@@ -246,7 +246,7 @@ To create the request:
246
246
9. Now, we'll call the [Post Data For Polyline API](/rest/api/maps/elevation/postdataforpolyline) to get elevation data for the same three points. On the **Builder** tab, select the **POST** HTTP method, and then enter the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
10. In the **Headers** field of the **POST** request, set `Content-Type` to `application/json`.
@@ -291,7 +291,7 @@ To create the request:
291
291
4. On the **Builder** tab, select the **GET** HTTP method, and then enter the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
0 commit comments