Skip to content

Commit 68a4c56

Browse files
authored
Merge pull request #186002 from stevemunk/SM-Updates-to-tutorial-creator-indoor-maps
Update tutorial-creator-indoor-maps.md
2 parents bd3b7c0 + feaedcd commit 68a4c56

File tree

1 file changed

+16
-15
lines changed

1 file changed

+16
-15
lines changed

articles/azure-maps/tutorial-creator-indoor-maps.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
22
title: 'Tutorial: Use Microsoft Azure Maps Creator to create indoor maps'
3+
titleSuffix: Microsoft Azure Maps
34
description: Tutorial on how to use Microsoft Azure Maps Creator to create indoor maps
45
author: stevemunk
56
ms.author: v-munksteve
6-
ms.date: 10/28/2021
7+
ms.date: 01/24/2022
78
ms.topic: tutorial
89
ms.service: azure-maps
910
services: azure-maps
@@ -20,8 +21,8 @@ This tutorial describes how to create indoor maps. In this tutorial, you'll lear
2021
> * Create a dataset from your map data.
2122
> * Create a tileset from the data in your dataset.
2223
> * 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.
2526
2627
## Prerequisites
2728

@@ -33,7 +34,7 @@ This tutorial describes how to create indoor maps. In this tutorial, you'll lear
3334
This tutorial uses the [Postman](https://www.postman.com/) application, but you can use a different API development environment.
3435

3536
>[!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).
3738
3839
## Upload a Drawing package
3940

@@ -71,15 +72,15 @@ To upload the Drawing package:
7172
7273
11. Select **Select File**, and then select a Drawing package.
7374
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.":::
7576
7677
12. Select **Send**.
7778
7879
13. In the response window, select the **Headers** tab.
7980
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.
8182
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.":::
8384
8485
### Check the Drawing package upload status
8586
@@ -93,7 +94,7 @@ To check the status of the drawing package and retrieve its unique ID (`udid`):
9394
9495
4. Select the **GET** HTTP method.
9596
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:
9798
9899
```http
99100
https://us.atlas.microsoft.com/mapData/operations/{operationId}?api-version=2.0&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
@@ -121,7 +122,7 @@ To retrieve content metadata:
121122
122123
4. . Select the **GET** HTTP method.
123124
124-
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:
125126
126127
```http
127128
https://us.atlas.microsoft.com/mapData/metadata/{udid}?api-version=2.0&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
@@ -144,7 +145,7 @@ To retrieve content metadata:
144145
145146
## Convert a Drawing package
146147
147-
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.
148149
149150
To convert a Drawing package:
150151
@@ -311,7 +312,7 @@ To create a tileset:
311312
312313
### Check the tileset creation status
313314
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`:
315316
316317
1. In the Postman app, select **New**.
317318
@@ -407,7 +408,7 @@ To query the unit collection in your dataset:
407408
408409
6. Select **Send**.
409410
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).
411412
412413
```json
413414
{
@@ -453,19 +454,19 @@ To create a stateset:
453454
454455
4. Select the **POST** HTTP method.
455456
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)):
457458
458459
```http
459460
https://us.atlas.microsoft.com/featurestatesets?api-version=2.0&datasetId={datasetId}&subscription-key={Your-Azure-Maps-Primary-Subscription-key}
460461
```
461462
462463
6. Select the **Headers** tab.
463464
464-
7. In the **KEY** field, select `Content-Type`.
465+
7. In the **KEY** field, select `Content-Type`.
465466
466467
8. In the **VALUE** field, select `application/json`.
467468
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.":::
469470
470471
9. Select the **Body** tab.
471472

0 commit comments

Comments
 (0)