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/creator-indoor-maps.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Creator for indoor maps| Microsoft Azure Maps
2
+
title: Work with indoor maps in Azure Maps Creator
3
3
description: This article introduces concepts that apply to Azure Maps Creator services.
4
4
author: anastasia-ms
5
5
ms.author: v-stharr
6
-
ms.date: 05/07/2020
6
+
ms.date: 05/18/2020
7
7
ms.topic: conceptual
8
8
ms.service: azure-maps
9
9
services: azure-maps
@@ -17,7 +17,7 @@ This article introduces concepts and tools that apply to Azure Maps Creator. We
17
17
18
18
You can use Creator to develop applications with map features based on indoor map data. This article describes the process of uploading, converting, creating, and using your map data. The entire workflow is illustrated in the diagram below.
19
19
20
-
20
+
21
21
22
22
## Create Azure Maps Creator
23
23
@@ -27,17 +27,17 @@ To use Creator services, Azure Maps Creator must be created in an Azure Maps acc
27
27
28
28
Creator collects indoor map data by converting an uploaded Drawing package. The Drawing package represents a constructed or remodeled facility. For information on Drawing package requirements, see [Drawing package requirements](drawing-requirements.md).
29
29
30
-
Use the [Azure Maps Data Upload API](https://docs.microsoft.com/rest/api/maps/data/uploadpreview) to upload a Drawing package. Upon a successful upload, the Data Upload API will return a *user data identifier (`udid`). The `udid` will be used in the next step to convert the uploaded package into indoor map data.
30
+
Use the [Azure Maps Data Upload API](https://docs.microsoft.com/rest/api/maps/data/uploadpreview) to upload a Drawing package. Upon a successful upload, the Data Upload API will return a user data identifier (`udid`). The `udid` will be used in the next step to convert the uploaded package into indoor map data.
31
31
32
32
## Convert a Drawing package
33
33
34
34
The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) converts an uploaded Drawing package into indoor map data. The Conversion service also validates the package. Validation issues are classified into two types: errors and warnings. If any errors are detected, the conversion process fails. Should warnings be detected, the conversion will succeed. However, it’s recommended that you review and resolve all warnings. A warning means that part of the conversion was ignored or automatically fixed. Failing to resolve the warnings could result in errors in latter processes. For more information, see [Drawing package warnings and errors](drawing-conversion-error-codes.md).
35
35
36
-
When an error occurs, the Conversion service provides a link to the [Azure Maps Drawing Error Visualizer](azure-maps-drawing-errors-visualizer.md) stand-alone web application. You can use the Drawing Error Visualizer to inspect [Drawing package warnings and errors](drawing-conversion-error-codes.md) that occurred during the conversion process. Once you have fixed the errors, you can then attempt to upload and convert the package.
36
+
When an error occurs, the Conversion service provides a link to the [Azure Maps Drawing Error Visualizer](drawing-error-visualizer.md) stand-alone web application. You can use the Drawing Error Visualizer to inspect [Drawing package warnings and errors](drawing-conversion-error-codes.md) that occurred during the conversion process. Once you have fixed the errors, you can then attempt to upload and convert the package.
Copy file name to clipboardExpand all lines: articles/azure-maps/drawing-conversion-error-codes.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Drawing Conversion Error and Warning in Azure Maps | Microsoft Docs
2
+
title: Azure Maps Drawing Conversion errors and warnings
3
3
description: Learn about the Conversion errors and warnings you may meet while you're using the Azure Maps Conversion service. Read the recommendations on how to resolve the errors and the warnings, with some examples.
4
4
author: anastasia-ms
5
5
ms.author: v-stharr
6
-
ms.date: 05/04/2020
6
+
ms.date: 05/18/2020
7
7
ms.topic: conceptual
8
8
ms.service: azure-maps
9
9
services: azure-maps
@@ -30,13 +30,13 @@ The Conversion service is unable to create a map feature from an invalid entity
30
30
31
31
* The two images below show examples of self-intersecting polygons.
32
32
33
-
33
+
34
34
35
-
35
+
36
36
37
37
* Below is an image that shows a non-closed PolyLine. Assume that the layer only supports closed geometry.
38
38
39
-
39
+
40
40
41
41
#### *How to fix geometryWarning*
42
42
@@ -52,7 +52,7 @@ An **unexpectedGeometryInLayer** warning occurs when the drawing contains geomet
52
52
53
53
The image below shows a non-closed PolyLine. Assume that the layer only supports closed geometry.
54
54
55
-
55
+
56
56
57
57
#### *How to fix unexpectedGeometryInLayer*
58
58
@@ -68,7 +68,7 @@ The **unsupportedFeatureRepresentation** warning occurs when the drawing contain
68
68
69
69
The image below shows an unsupported entity type as a multi-line text object on a label layer.
70
70
71
-
71
+
72
72
73
73
#### *How to fix unsupportedFeatureRepresentation*
74
74
@@ -84,15 +84,15 @@ The **automaticRepairPerformed** warning occurs when the Conversion service auto
84
84
85
85
* The following image shows how the Conversion service repaired a self-intersecting polygon into valid geometry.
86
86
87
-
87
+
88
88
89
89
* The image below shows how the Conversion service snapped the first and last vertex of a non-closed PolyLine to create a closed PolyLine, where the first and last vertex were less than 1 mm apart.
90
90
91
-
91
+
92
92
93
93
* The image below shows how, in a layer that supports only closed PolyLines, the Conversion service repaired multiple non-closed PolyLines. In order to avoid discarding the non-closed PolyLines, the service combined them into a single closed PolyLine.
94
94
95
-
95
+
96
96
97
97
#### *How to fix automaticRepairPerformed*
98
98
@@ -184,11 +184,11 @@ The **wallOutsideLevel** warning occurs when the drawing contains a Wall geometr
184
184
185
185
* The image below shows an interior wall, in red, outside the yellow level boundary.
186
186
187
-
187
+
188
188
189
189
* The following image shows an exterior wall, in red, outside the yellow level boundary.
190
190
191
-
191
+
192
192
193
193
#### *How to fix wallOutsideLevel*
194
194
@@ -206,7 +206,7 @@ A **unitOutsideLevel** warning occurs when the drawing contains unit geometry ou
206
206
207
207
In the following image, unit geometry, in red, exceeds the bounds of the yellow level boundary.
208
208
209
-
209
+
210
210
211
211
#### *How to fix unitOutsideLevel*
212
212
@@ -222,7 +222,7 @@ A **partiallyOverlappingUnit** warning occurs when the drawing contains a unit g
222
222
223
223
In the following image, the overlapping unit is highlighted in red. `UNIT110` and `HALLWAY` are discarded.
224
224
225
-
225
+
226
226
227
227
#### *How to fix partiallyOverlappingUnit*
228
228
@@ -240,7 +240,7 @@ A **doorOutsideLevel** warning occurs when the drawing contains a door geometry
240
240
241
241
In the following image, the door geometry, highlighted in red, overlaps the yellow level boundary.
242
242
243
-
243
+
244
244
245
245
#### *How to fix doorOutsideLevel*
246
246
@@ -258,7 +258,7 @@ The **zoneWarning** occurs when a zone doesn't contain a label. The Conversion s
258
258
259
259
The following image shows a zone that doesn't contain a label.
260
260
261
-
261
+
262
262
263
263
#### *How to fix zoneWarning*
264
264
@@ -282,7 +282,7 @@ A **labelWarning** occurs because of one or more of the following reasons:
282
282
283
283
The following image shows a label that inside two zones.
284
284
285
-
285
+
286
286
287
287
#### *How to fix labelWarning*
288
288
@@ -462,7 +462,7 @@ The **wallError** occurs when the drawing contains an error while attempting to
462
462
463
463
The following image displays a wall feature that doesn't overlap any units.
464
464
465
-
465
+
466
466
467
467
#### *How to fix wallError*
468
468
@@ -485,11 +485,11 @@ The **verticalPenetrationError** occurs because of one or more of the following
485
485
486
486
The image below shows a vertical penetration area with no overlapping vertical penetration areas on levels above or below it.
487
487
488
-
488
+
489
489
490
490
The following image shows a vertical penetration area that overlaps more than one vertical penetration area on an adjacent level.
491
491
492
-
492
+
493
493
494
494
#### How to fix verticalPenetrationError
495
495
@@ -498,7 +498,7 @@ To fix a **verticalPenetrationError** error, read about how to use a vertical pe
498
498
## Next steps
499
499
500
500
> [!div class="nextstepaction"]
501
-
> [How to use Azure Maps Drawing error visualizer](azure-maps-drawing-errors-visualizer.md)
501
+
> [How to use Azure Maps Drawing error visualizer](drawing-error-visualizer.md)
502
502
503
503
> [!div class="nextstepaction"]
504
-
> [Creator for indoor mapping](creator-for-indoor-maps.md)
504
+
> [Creator for indoor mapping](creator-indoor-maps.md)
Copy file name to clipboardExpand all lines: articles/azure-maps/drawing-error-visualizer.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Use Azure Maps Drawing Error Visualizer | Microsoft Azure Maps
2
+
title: Use Azure Maps Drawing Error Visualizer
3
3
description: In this article, you'll learn about how to visualize warnings and errors returned by the Creator Conversion API.
4
4
author: anastasia-ms
5
5
ms.author: v-stharr
6
-
ms.date: 04/27/2020
6
+
ms.date: 05/18/2020
7
7
ms.topic: conceptual
8
8
ms.service: azure-maps
9
9
services: azure-maps
@@ -73,15 +73,15 @@ Open the _index.html_ file using any of the browsers below, with the respective
73
73
74
74
After launching the Drawing Error Visualizer tool, you'll be presented with the upload page. The upload page contains a drag and drop box. The drag & drop box also functions as button that launches a File Explorer dialog.
The _ConversionWarningsAndErrors.json_ file has been placed at the root of the downloaded directory. To load the _ConversionWarningsAndErrors.json_ you can either drag & drop the file onto the box or click on the box, find the file in the File Explorer dialogue, and then upload the file.
79
79
80
-
80
+
81
81
82
82
Once the _ConversionWarningsAndErrors.json_ file loads, you'll see a list of your Drawing package errors and warnings. Each error or warning is specified by the layer, level, and a detailed message. You may now navigate to each error to learn more details on how to resolve the error.
83
83
84
-
84
+
85
85
86
86
## Next steps
87
87
@@ -91,7 +91,7 @@ Once your [Drawing package meets the requirements](drawing-requirements.md), you
Copy file name to clipboardExpand all lines: articles/azure-maps/drawing-requirements.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
-
title: Drawing package requirements in Creator | Microsoft Docs
2
+
title: Drawing package requirements in Azure Maps Creator
3
3
description: Learn about the Drawing package requirements to convert your facility design files to map data using the Azure Maps Conversion service
4
4
author: anastasia-ms
5
5
ms.author: v-stharr
6
-
ms.date: 5/01/2020
6
+
ms.date: 5/18/2020
7
7
ms.topic: conceptual
8
8
ms.service: azure-maps
9
9
services: azure-maps
@@ -12,7 +12,7 @@ manager: philMea
12
12
13
13
# Drawing package requirements
14
14
15
-
The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) lets you convert uploaded Drawing packages into map data. This article describes the Drawing package requirements for the Conversion API. To view a sample package, you can download the sample [Conversion Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
15
+
The [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) lets you convert uploaded Drawing packages into map data. This article describes the Drawing package requirements for the Conversion API. To view a sample package, you can download the sample [Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
16
16
17
17
## Prerequisites
18
18
@@ -262,9 +262,11 @@ The `zoneProperties` object contains a JSON array of zone properties.
262
262
|zoneNameSubtitle| string/int | false |Subtitle of the zone. |
263
263
264
264
### Sample Drawing package manifest
265
-
Below is a sample manifest file for the sample Drawing package. To download the entire package, click [sample Drawing package](https://github.com/Azure-Samples/Azure-Maps-DWG-Package-Samples).
265
+
266
+
Below is a sample manifest file for the sample Drawing package. To download the entire package, click [sample Drawing package](https://github.com/Azure-Samples/am-creator-indoor-data-examples).
266
267
267
268
#### Manifest File
269
+
268
270
```JSON
269
271
{
270
272
"version": "1.1",
@@ -398,7 +400,7 @@ Below is a sample manifest file for the sample Drawing package. To download the
398
400
Once your Drawing package meets the requirements, you may use the [Azure Maps Conversion service](https://docs.microsoft.com/rest/api/maps/data/conversion) to convert the package to a map dataset. Then, you can use the dataset to generate an indoor map using the Indoor Maps module. Learn more about using the Indoor Maps module by reading the following articles:
399
401
400
402
> [!div class="nextstepaction"]
401
-
>[Creator for indoor maps](creator-for-indoor-maps.md)
403
+
>[Creator for indoor maps](creator-indoor-maps.md)
402
404
403
405
> [!div class="nextstepaction"]
404
406
> [Tutorial: Creating a Creator indoor map](tutorial-creator-indoor-maps.md)
0 commit comments