Merge pull request #252135 from stevemunk/creator-data-service-deprecation

denrea · web-flow · commit 66ffe7ddccdc · 2023-10-12T14:22:35.000-07:00
Update Creator articles to deprecate the data service and use data registry.
diff --git a/articles/azure-maps/about-creator.md b/articles/azure-maps/about-creator.md
@@ -56,10 +56,11 @@ This section provides a high-level overview of the indoor map creation workflow.
     describing the drawings. You can use the [Azure Maps Creator onboarding tool] to
     create new and edit existing [manifest files].
 
-1. **Upload**. Upload your drawing packages into your Azure Maps
-    account. Upload drawing packages using the [Data Upload API].
+1. **Upload**. Upload your drawing packages into your Azure Storage
+    account. For more information, see [How to create data registry].
 
-1. **Convert**. Once the drawing package is uploaded into your Azure Maps account,
+1. **Convert**. Once the drawing package is uploaded into your Azure Storage account,
+1. **Convert**. Once the drawing package is uploaded into your Azure Storage account,
     use the [Conversion] service to validate the data in the uploaded drawing
     package and convert it into map data.
 
@@ -116,7 +117,6 @@ This section provides a high-level overview of the indoor map creation workflow.
 [Create dataset using GeoJson package]: how-to-dataset-geojson.md
 [Custom styling for indoor maps]: how-to-create-custom-styles.md
 [custom styling]: creator-indoor-maps.md#custom-styling-preview
-[Data Upload API]: /rest/api/maps/data-v2/upload
 [dataset]: creator-indoor-maps.md#datasets
 [Drawing error visualizer]: drawing-error-visualizer.md
 [Drawing package guide]: drawing-package-guide.md?pivots=drawing-package-v2
@@ -126,6 +126,7 @@ This section provides a high-level overview of the indoor map creation workflow.
 [Facility Ontology]: creator-facility-ontology.md
 [Features API]: /rest/api/maps/2023-03-01-preview/features
 [features]: glossary.md#feature
+[How to create data registry]: how-to-create-data-registries.md
 [Implement Dynamic styling for indoor maps]: indoor-map-dynamic-styling.md
 [Indoor map concepts]: creator-indoor-maps.md
 [Indoor maps wayfinding service]: how-to-creator-wayfinding.md
diff --git a/articles/azure-maps/creator-indoor-maps.md b/articles/azure-maps/creator-indoor-maps.md
@@ -60,7 +60,10 @@ Creator services create, store, and use various data types that are defined and
 
 Creator collects indoor map data by converting an uploaded drawing package. The drawing package represents a constructed or remodeled facility. For information about drawing package requirements, see [Drawing package requirements].
 
-Use [Data Upload] to upload a drawing package. After the Drawing packing is uploaded, the Data Upload API returns a user data identifier (`udid`). The `udid` can then be used to convert the uploaded package into indoor map data.
+Follow the steps outlined in the [How to create data registry] article to upload the drawing package into your Azure storage account then register it in your Azure Maps account.
+
+> [!IMPORTANT]
+> Make sure to make a note of the unique identifier (`udid`) value, you will need it. The `udid` is required to convert the uploaded package into indoor map data.
 
 ## Convert a drawing package
 
@@ -228,7 +231,7 @@ An application can use a feature stateset to dynamically render features in a fa
 
 ### Wayfinding (preview)
 
-The [Wayfinding service] enables you to provide your customers with the shortest path between two points within a facility. Once you've imported your indoor map data and created your dataset, you can use that to create a [routeset]. The routeset provides the data required to generate paths between two points. The wayfinding service takes into account things such as the minimum width of openings and may optionally exclude elevators or stairs when navigating between levels as a result.
+The [Wayfinding service] enables you to provide your customers with the shortest path between two points within a facility. Once you've imported your indoor map data and created your dataset, you can use that to create a [routeset]. The routeset provides the data required to generate paths between two points. The wayfinding service takes into account things such as the minimum width of openings and can optionally exclude elevators or stairs when navigating between levels as a result.
 
 Creator wayfinding is powered by [Havok].
 
@@ -314,7 +317,6 @@ The following example shows how to update a dataset, create a new tileset, and d
 [Alias API]: /rest/api/maps/v2/alias
 [Conversion service]: /rest/api/maps/v2/conversion
 [Creator - map configuration Rest API]: /rest/api/maps/2023-03-01-preview/map-configuration
-[Data Upload]: /rest/api/maps/data-v2/update
 [Dataset Create]: /rest/api/maps/v2/dataset/create
 [Dataset service]: /rest/api/maps/v2/dataset
 [Feature State service]: /rest/api/maps/v2/feature-state
@@ -343,6 +345,7 @@ The following example shows how to update a dataset, create a new tileset, and d
 [Create custom styles for indoor maps]: how-to-create-custom-styles.md
 [Drawing package requirements]: drawing-requirements.md
 [Drawing package warnings and errors]: drawing-conversion-error-codes.md
+[How to create data registry]: how-to-create-data-registries.md
 [Indoor maps wayfinding service]: how-to-creator-wayfinding.md
 [Instantiate the Indoor Manager]: how-to-use-indoor-module.md#instantiate-the-indoor-manager
 [Manage authentication in Azure Maps]: how-to-manage-authentication.md
diff --git a/articles/azure-maps/drawing-error-visualizer.md b/articles/azure-maps/drawing-error-visualizer.md
@@ -21,11 +21,14 @@ The *Drawing Error Visualizer* is a stand-alone web application that displays [D
 * A [subscription key]
 * A [Creator resource]
 
-This tutorial uses the [Postman] application, but you may choose a different API development environment.
+This tutorial uses the [Postman] application, but you can choose a different API development environment.
 
 ## Download
 
-1. Upload your drawing package to the Azure Maps Creator service to obtain a `udid` for the uploaded package. For steps on how to upload a package, see [Upload a drawing package].
+1. Follow the steps outlined in the [How to create data registry] article to upload the drawing package into your Azure storage account then register it in your Azure Maps account.
+
+    > [!IMPORTANT]
+    > Make sure to make a note of the unique identifier (`udid`) value, you will need it. The `udid` is is how you reference the drawing package you uploaded into your Azure storage account from your source code and HTTP requests.
 
 2. Now that the drawing package is uploaded, use `udid` for the uploaded package to convert the package into map data. For steps on how to convert a package, see [Convert a drawing package].
 
@@ -60,7 +63,7 @@ Unzip the _VisualizationTool.zip_ folder. It contains the following items:
 * _static_ folder: source code
 * _index.html_ file: the web application.
 
-Open the _index.html_ file using any of the following browsers, with the respective version number. You may use a different version, if the version offers equally compatible behavior as the listed version.
+Open the _index.html_ file using any of the following browsers, with the respective version number. You can use a different version, if the version offers equally compatible behavior as the listed version.
 
 * Microsoft Edge 80
 * Safari 13
@@ -77,7 +80,7 @@ The  _ConversionWarningsAndErrors.json_ file has been placed at the root of the
 
 :::image type="content" source="./media/drawing-errors-visualizer/loading-data.gif" alt-text="Drawing Error Visualizer App - Drag and drop to load data":::
 
-The _ConversionWarningsAndErrors.json_ contains a list of your drawing package errors and warnings. To view detailed information about an error or warning, select the **Details** link. An intractable section appears below the list. You may now navigate to each error to learn more details on how to resolve the error.
+The _ConversionWarningsAndErrors.json_ contains a list of your drawing package errors and warnings. To view detailed information about an error or warning, select the **Details** link. An intractable section appears below the list. You can now navigate to each error to learn more details on how to resolve the error.
 
 :::image type="content" source="./media/drawing-errors-visualizer/errors.png" alt-text="Drawing Error Visualizer App - Errors and Warnings":::
 
@@ -95,6 +98,6 @@ Learn more by reading:
 [Creator resource]: how-to-manage-creator.md
 [Drawing package requirements]: drawing-requirements.md
 [Drawing package warnings and errors]: drawing-conversion-error-codes.md
+[How to create data registry]: how-to-create-data-registries.md
 [Postman]: https://www.postman.com/
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
-[Upload a drawing package]: tutorial-creator-indoor-maps.md#upload-a-drawing-package
diff --git a/articles/azure-maps/how-to-dataset-geojson.md b/articles/azure-maps/how-to-dataset-geojson.md
@@ -21,6 +21,7 @@ Azure Maps Creator enables users to import their indoor map data in GeoJSON form
 - An [Azure Maps account]
 - A [Subscription key]
 - An Azure Maps [Creator resource]
+- An [Azure storage account]
 - Basic understanding of [Creator for indoor maps]
 - Basic understanding of [Facility Ontology 2.0]
 - Zip package containing all required GeoJSON files. If you don't have GeoJSON files, you can download the [Contoso building sample].
@@ -36,33 +37,10 @@ For more information on the GeoJSON package, see the [Geojson zip package requir
 
 ### Upload the GeoJSON package
 
-Use the [Data Upload API] to upload the Drawing package to Azure Maps Creator account.
+Follow the steps outlined in the [How to create data registry] article to upload the GeoJSON package into your Azure storage account then register it in your Azure Maps account.
 
-The Data Upload API is a long running transaction that implements the pattern defined in [Creator Long-Running Operation API V2].
-
-To upload the GeoJSON package:
-
-1. Execute the following HTTP POST request that uses the [Data Upload API]:
-
-    ```http
-    https://us.atlas.microsoft.com/mapData?api-version=2.0&dataFormat=zip&subscription-key={Your-Azure-Maps-Subscription-key}
-    ```
-
-    1. Set `Content-Type` in the **Header** to `application/zip`.
-
-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 upload, which is explained in the next section.
-
-### Check the GeoJSON package upload status
-
-To check the status of the GeoJSON package and retrieve its unique identifier (`udid`):
-
-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:
-
-```http
-https://us.atlas.microsoft.com/mapData/operations/{operationId}?api-version=2.0&subscription-key={Your-Azure-Maps-Subscription-key}
-```
-
-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.
+> [!IMPORTANT]
+> Make sure to make a note of the unique identifier (`udid`) value, you will need it. The `udid` is is how you reference the GeoJSON package you uploaded into your Azure storage account from your source code and HTTP requests.
 
 ### Create a dataset
 
@@ -73,7 +51,7 @@ A dataset is a collection of map features, such as buildings, levels, and rooms.
 
 To create a dataset:
 
-1. Enter the following URL to the dataset service. The request should look like the following URL (replace {udid} with the `udid` obtained in [Check the GeoJSON package upload status] section):
+1. Enter the following URL to the dataset service. The request should look like the following URL (replace {udid} with the `udid` obtained in [Upload the GeoJSON package] section):
 
   ```http
   https://us.atlas.microsoft.com/datasets?api-version=2023-03-01-preview&udid={udid}&subscription-key={Your-Azure-Maps-Subscription-key}
@@ -154,29 +132,29 @@ Feature IDs can only contain alpha-numeric (a-z, A-Z, 0-9), hyphen (-), dot (.)
 [Access to Creator services]: how-to-manage-creator.md#access-to-creator-services
 [area]: creator-facility-ontology.md?pivots=facility-ontology-v2#areaelement
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
-[Check the GeoJSON package upload status]: #check-the-geojson-package-upload-status
 [Contoso building sample]: https://github.com/Azure-Samples/am-creator-indoor-data-examples
 [Convert a drawing package]: tutorial-creator-indoor-maps.md#convert-a-drawing-package
 [Create a dataset]: #create-a-dataset
 [Create a tileset]: tutorial-creator-indoor-maps.md#create-a-tileset
 [Creator for indoor maps]: creator-indoor-maps.md
-[Creator Long-Running Operation API V2]: creator-long-running-operation-v2.md
 [Creator resource]: how-to-manage-creator.md
-[Data Upload API]: /rest/api/maps/data-v2/upload
 [Dataset Create API]: /rest/api/maps/2023-03-01-preview/dataset/create
 [Dataset Create]: /rest/api/maps/v2/dataset/create
 [dataset]: creator-indoor-maps.md#datasets
 [Facility Ontology 2.0]: creator-facility-ontology.md?pivots=facility-ontology-v2
 [facility]: creator-facility-ontology.md?pivots=facility-ontology-v2#facility
 [Geojson zip package requirements]: #geojson-zip-package-requirements
+[How to create data registry]: how-to-create-data-registries.md
 [level]: creator-facility-ontology.md?pivots=facility-ontology-v2#level
 [line]: creator-facility-ontology.md?pivots=facility-ontology-v2#lineelement
 [Next steps]: #next-steps
 [openings]: creator-facility-ontology.md?pivots=facility-ontology-v2#opening
 [point]: creator-facility-ontology.md?pivots=facility-ontology-v2#pointelement
 [RFC 7946]: https://www.rfc-editor.org/rfc/rfc7946.html
+[Azure storage account]: /azure/storage/common/storage-account-create?tabs=azure-portal
 [structures]: creator-facility-ontology.md?pivots=facility-ontology-v2#structure
 [Subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [units]: creator-facility-ontology.md?pivots=facility-ontology-v2#unit
+[Upload the GeoJSON package]: #upload-the-geojson-package
 [verticalPenetrations]: creator-facility-ontology.md?pivots=facility-ontology-v2#verticalpenetration
 [Visual Studio]: https://visualstudio.microsoft.com/downloads/
diff --git a/articles/azure-maps/how-to-manage-creator.md b/articles/azure-maps/how-to-manage-creator.md
@@ -73,14 +73,12 @@ Creator usage data is incorporated in your Azure Maps usage charts and activity
 
 Creator services and services that use data hosted in Creator (for example, Render service), are accessible at a geographical URL. The geographical URL determines the location selected during creation. For example, if Creator is created in a region in the United States geographical location, all calls to the Conversion service must be submitted to `us.atlas.microsoft.com/conversions`. To view mappings of region to geographical location, [see Creator service geographic scope].
 
-Also, all data imported into Creator should be uploaded into the same geographical location as the Creator resource. For example, if Creator is provisioned in the United States, all raw data should be uploaded via `us.atlas.microsoft.com/mapData/upload`.
-
 ## Next steps
 
 Introduction to Creator services for indoor mapping:
 
 > [!div class="nextstepaction"]
-> [Data upload]
+> [Upload a drawing package]
 
 > [!div class="nextstepaction"]
 > [Data conversion]
@@ -111,11 +109,11 @@ Learn how to use the Creator services to render indoor maps in your application:
 [Azure Maps pricing]: https://aka.ms/CreatorPricing
 [Azure portal]: https://portal.azure.com
 [Data conversion]: creator-indoor-maps.md#convert-a-drawing-package
-[Data upload]: creator-indoor-maps.md#upload-a-drawing-package
 [Dataset]: creator-indoor-maps.md#datasets
 [Feature State set]: creator-indoor-maps.md#feature-statesets
 [Indoor map dynamic styling]: indoor-map-dynamic-styling.md
 [Manage authentication in Azure Maps]: how-to-manage-authentication.md
 [see Creator service geographic scope]: creator-geographic-scope.md
 [Tileset]: creator-indoor-maps.md#tilesets
+[Upload a drawing package]: creator-indoor-maps.md#upload-a-drawing-package
 [Use the Indoor Maps module]: how-to-use-indoor-module.md
diff --git a/articles/azure-maps/tutorial-creator-indoor-maps.md b/articles/azure-maps/tutorial-creator-indoor-maps.md
