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/tutorial-creator-indoor-maps.md
+16-15Lines changed: 16 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,10 @@
1
1
---
2
2
title: 'Tutorial: Use Microsoft Azure Maps Creator to create indoor maps'
3
+
titleSuffix: Microsoft Azure Maps
3
4
description: Tutorial on how to use Microsoft Azure Maps Creator to create indoor maps
4
5
author: stevemunk
5
6
ms.author: v-munksteve
6
-
ms.date: 10/28/2021
7
+
ms.date: 01/24/2022
7
8
ms.topic: tutorial
8
9
ms.service: azure-maps
9
10
services: azure-maps
@@ -20,8 +21,8 @@ This tutorial describes how to create indoor maps. In this tutorial, you'll lear
20
21
> * Create a dataset from your map data.
21
22
> * Create a tileset from the data in your dataset.
22
23
> * Query the Azure Maps Web Feature Service (WFS) API to learn about your map features.
23
-
> * Create a feature stateset by using your map features and the data in your dataset.
24
-
> * Update your feature stateset.
24
+
> * Create a feature stateset that can be used to set the states of features in your dataset.
25
+
> * Update the state of a given map feature.
25
26
26
27
## Prerequisites
27
28
@@ -33,7 +34,7 @@ This tutorial describes how to create indoor maps. In this tutorial, you'll lear
33
34
This tutorial uses the [Postman](https://www.postman.com/) application, but you can use a different API development environment.
34
35
35
36
>[!IMPORTANT]
36
-
> This tutorial uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator Services](how-to-manage-creator.md#access-to-creator-services). To view mappings of region to geographical location, [see Creator service geographic scope](creator-geographic-scope.md).
37
+
> This tutorial uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator Services](how-to-manage-creator.md#access-to-creator-services).
37
38
38
39
## Upload a Drawing package
39
40
@@ -71,15 +72,15 @@ To upload the Drawing package:
71
72
72
73
11. Select **Select File**, and then select a Drawing package.
73
74
74
-
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-body.png" alt-text="Select a Drawing package.":::
75
+
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-body.png" alt-text="A screenshot of Postman showing the body tab in the POST window, with Select File highlighted, this is used to select the Drawing package to import into Creator.":::
75
76
76
77
12. Select **Send**.
77
78
78
79
13. In the response window, select the **Headers** tab.
79
80
80
-
14. Copy the value of the **Operation-Location** key, which is the `status URL`. We'll use the `status URL` to check the status of the Drawing package upload.
81
+
14. Copy the value of the **Operation-Location** key. The Operation-Location key is also known as the `status URL` and is required to check the status of the Drawing package upload, which is explained in the next section.
81
82
82
-
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-response-header.png" alt-text="Copy the status URL in the Location key.":::
83
+
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-upload-response-header.png" alt-text="A screenshot of Postman showing the header tab in the response window, with the Operation Location key highlighted.":::
83
84
84
85
### Check the Drawing package upload status
85
86
@@ -93,7 +94,7 @@ To check the status of the drawing package and retrieve its unique ID (`udid`):
93
94
94
95
4. Select the **GET** HTTP method.
95
96
96
-
5. Enter the `status URL` you copied in [Upload a Drawing package](#upload-a-drawing-package). The request should look like the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
97
+
5. Enter the `status URL` you copied as the last step in the previous section of this article. You will need to append your subscription key to the end of the URL `&subscription-key={Your-Azure-Maps-Primary-Subscription-key}` (replace `{Azure-Maps-Primary-Subscription-key}` with your Azure Maps primary subscription key). The request should look like the following URL:
5. Enter the `resource Location URL` you copied in [Check Drawing package upload status](#check-the-drawing-package-upload-status). The request should look like the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key):
125
+
5. Enter the `resource Location URL` you copied as the last step in the previous section of this article. You will need to append your subscription key to the end of the URL `&subscription-key={Your-Azure-Maps-Primary-Subscription-key}` (replace `{Azure-Maps-Primary-Subscription-key}` with your Azure Maps primary subscription key). The request should look like the following URL:
Now that the Drawing package is uploaded, we'll use the `udid` for the uploaded package to convert the package into map data. The Conversion API uses a long-running transaction that implements the pattern defined [here](creator-long-running-operation-v2.md).
148
+
Now that the Drawing package is uploaded, we'll use the `udid` for the uploaded package to convert the package into map data. The Conversion API uses a long-running transaction that implements the pattern defined in the [Creator Long-Running Operation](creator-long-running-operation-v2.md) article.
148
149
149
150
To convert a Drawing package:
150
151
@@ -311,7 +312,7 @@ To create a tileset:
311
312
312
313
### Check the tileset creation status
313
314
314
-
To check the status of the dataset creation process and retrieve the `tilesetId`:
315
+
To check the status of the tileset creation process and retrieve the `tilesetId`:
315
316
316
317
1. In the Postman app, select **New**.
317
318
@@ -407,7 +408,7 @@ To query the unit collection in your dataset:
407
408
408
409
6. Select **Send**.
409
410
410
-
7. After the response returns, copy the feature `id` for one of the `unit` features. In the following example, the feature `id` is "UNIT26". In this tutorial, we'll use "UNIT26" as our feature `id` in the next section.
411
+
7. After the response returns, copy the feature `id` for one of the `unit` features. In the following example, the feature `id` is "UNIT26". In this tutorial, you'll use "UNIT26" as your feature `id` when you [Update a feature state](#update-a-feature-state).
411
412
412
413
```json
413
414
{
@@ -453,19 +454,19 @@ To create a stateset:
453
454
454
455
4. Select the **POST** HTTP method.
455
456
456
-
5. Enter the following URL to the [Stateset API](/rest/api/maps/v2/feature-state/create-stateset). The request should look like the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key, and `{datasetId`} with the `datasetId` obtained in [Check dataset creation status](#check-the-dataset-creation-status)):
457
+
5. Enter the following URL to the [Stateset API](/rest/api/maps/v2/feature-state/create-stateset). The request should look like the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key, and `{datasetId`} with the `datasetId` obtained in [Check the dataset creation status](#check-the-dataset-creation-status)):
8. In the **VALUE** field, select `application/json`.
467
468
468
-
:::image type="content" source="./media/tutorial-creator-indoor-maps/stateset-header.png"alt-text="Header tab information for stateset creation.":::
469
+
:::image type="content" source="./media/tutorial-creator-indoor-maps/stateset-header.png"alt-text="A screenshot of Postman showing the Header tab of the POST request that shows the Content Type Key with a value of application forward slash json.":::
0 commit comments