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
+39-19Lines changed: 39 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,27 +23,27 @@ This tutorial describes how to create indoor maps for use in Microsoft Azure Map
23
23
> * Get the default map configuration ID from your tileset.
24
24
25
25
> [!TIP]
26
-
> You can also create a dataset from a GeoJSON package. For more information, see [Create a dataset using a GeoJson package (Preview)](how-to-dataset-geojson.md).
26
+
> You can also create a dataset from a GeoJSON package. For more information, see [Create a dataset using a GeoJson package (Preview)].
27
27
28
28
## Prerequisites
29
29
30
-
1.[Make an Azure Maps account](quick-demo-map-app.md#create-an-azure-maps-account).
31
-
2.[Obtain a primary subscription key](quick-demo-map-app.md#get-the-primary-key-for-your-account), also known as the primary key or the subscription key.
32
-
3.[Create a Creator resource](how-to-manage-creator.md).
33
-
4. Download the [Sample drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples/blob/master/Sample%20-%20Contoso%20Drawing%20Package.zip).
30
+
1.An [Azure Maps account]
31
+
2.A [subscription key]
32
+
3.A [Creator resource]
33
+
4. Download the [Sample drawing package]
34
34
35
-
This tutorial uses the [Postman](https://www.postman.com/) application, but you can use a different API development environment.
35
+
This tutorial uses the [Postman] application, but you can use a different API development environment.
36
36
37
37
>[!IMPORTANT]
38
38
>
39
-
> * This article 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).
39
+
> * This article 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].
40
40
> * In the URL examples in this article you will need to replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
41
41
42
42
## Upload a drawing package
43
43
44
-
Use the [Data Upload API](/rest/api/maps/data-v2/upload) to upload the drawing package to Azure Maps resources.
44
+
Use the [Data Upload API] to upload the drawing package to Azure Maps resources.
45
45
46
-
The Data Upload API is a long running transaction that implements the pattern defined in [Creator Long-Running Operation API V2](creator-long-running-operation-v2.md).
46
+
The Data Upload API is a long running transaction that implements the pattern defined in [Creator Long-Running Operation API V2].
47
47
48
48
To upload the drawing package:
49
49
@@ -55,7 +55,7 @@ To upload the drawing package:
55
55
56
56
4. Select the **POST** HTTP method.
57
57
58
-
5. Enter the following URL to the [Data Upload API](/rest/api/maps/data-v2/upload) The request should look like the following URL:
58
+
5. Enter the following URL to the [Data Upload API] The request should look like the following URL:
Now that the drawing package is uploaded, you'll use the `udid` for the uploaded package to convert the package into map data. The [Conversion API](/rest/api/maps/v2/conversion) uses a long-running transaction that implements the pattern defined in the [Creator Long-Running Operation](creator-long-running-operation-v2.md) article.
151
+
Now that the drawing package is uploaded, you'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] article.
152
152
153
153
To convert a drawing package:
154
154
@@ -160,7 +160,7 @@ To convert a drawing package:
160
160
161
161
4. Select the **POST** HTTP method.
162
162
163
-
5. Enter the following URL to the [Conversion service](/rest/api/maps/v2/conversion/convert) (replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key and `udid` with the `udid` of the uploaded package):
163
+
5. Enter the following URL to the [Conversion service] (replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key and `udid` with the `udid` of the uploaded package):
@@ -202,7 +202,7 @@ To check the status of the conversion process and retrieve the `conversionId`:
202
202
203
203
:::image type="content" source="./media/tutorial-creator-indoor-maps/data-conversion-id.png" alt-text="A screenshot of Postman highlighting the conversion ID value that appears in the resource location key in the responses header.":::
204
204
205
-
The sample drawing package should be converted without errors or warnings. However, if you receive errors or warnings from your own drawing package, the JSON response includes a link to the [Drawing error visualizer](drawing-error-visualizer.md). You can use the Drawing Error visualizer to inspect the details of errors and warnings. To receive recommendations to resolve conversion errors and warnings, see [Drawing conversion errors and warnings](drawing-conversion-error-codes.md).
205
+
The sample drawing package should be converted without errors or warnings. However, if you receive errors or warnings from your own drawing package, the JSON response includes a link to the [Drawing error visualizer]. You can use the Drawing Error visualizer to inspect the details of errors and warnings. To receive recommendations to resolve conversion errors and warnings, see [Drawing conversion errors and warnings].
206
206
207
207
The following JSON fragment displays a sample conversion warning:
208
208
@@ -233,7 +233,7 @@ The following JSON fragment displays a sample conversion warning:
233
233
234
234
## Create a dataset
235
235
236
-
A dataset is a collection of map features, such as buildings, levels, and rooms. To create a dataset, use the [Dataset Create API](/rest/api/maps/v2/dataset/create). The Dataset Create API takes the `conversionId` for the converted drawing package and returns a `datasetId` of the created dataset.
236
+
A dataset is a collection of map features, such as buildings, levels, and rooms. To create a dataset, use the [Dataset Create API]. The Dataset Create API takes the `conversionId` for the converted drawing package and returns a `datasetId` of the created dataset.
237
237
238
238
To create a dataset:
239
239
@@ -245,7 +245,7 @@ To create a dataset:
245
245
246
246
4. Select the **POST** HTTP method.
247
247
248
-
5. Enter the following URL to the [Dataset API](/rest/api/maps/v2/dataset). The request should look like the following URL (replace `{conversionId`} with the `conversionId` obtained in [Check drawing package conversion status](#check-the-drawing-package-conversion-status)):
248
+
5. Enter the following URL to the [Dataset service]. The request should look like the following URL (replace `{conversionId`} with the `conversionId` obtained in [Check drawing package conversion status](#check-the-drawing-package-conversion-status)):
5. Enter the following URL to the [Tileset API](/rest/api/maps/v2/tileset). The request should look like the following URL (replace `{datasetId`} with the `datasetId` obtained in the [Check the dataset creation status](#check-the-dataset-creation-status) section above:
302
+
5. Enter the following URL to the [Tileset service]. The request should look like the following URL (replace `{datasetId`} with the `datasetId` obtained in the [Check the dataset creation status](#check-the-dataset-creation-status) section above:
@@ -339,7 +339,7 @@ To check the status of the tileset creation process and retrieve the `tilesetId`
339
339
340
340
## The map configuration (preview)
341
341
342
-
Once your tileset creation completes, you can get the `mapConfigurationId` using the [tileset get](/rest/api/maps/v20220901preview/tileset/get) HTTP request:
342
+
Once your tileset creation completes, you can get the `mapConfigurationId` using the [tileset get] HTTP request:
343
343
344
344
1. In the Postman app, select **New**.
345
345
@@ -349,7 +349,7 @@ Once your tileset creation completes, you can get the `mapConfigurationId` using
349
349
350
350
4. Select the **GET** HTTP method.
351
351
352
-
5. Enter the following URL to the [Tileset API](/rest/api/maps/v20220901preview/tileset), passing in the tileset ID you obtained in the previous step.
352
+
5. Enter the following URL to the [Tileset service], passing in the tileset ID you obtained in the previous step.
0 commit comments