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/how-to-create-data-registries.md
+28-36Lines changed: 28 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Create Data Registry (preview)
3
3
titleSuffix: Azure Maps
4
4
description: Learn how to create Data Registry.
5
5
author: stevemunk
6
-
ms.author: v-munksteve
6
+
ms.author: eriklind
7
7
ms.date: 2/14/2023
8
8
ms.topic: how-to
9
9
ms.service: azure-maps
@@ -12,22 +12,22 @@ services: azure-maps
12
12
13
13
# How to create data registry (preview)
14
14
15
-
The [data registry][data registry] service enables you to register data content in an Azure Storage Account with your Azure Maps account. An example of data might include a collection of Geofences used in the Azure Maps Geofencing Service. Another example is ZIP files containing drawing packages (DWG) or GeoJSON files that Azure Maps Creator uses to create or update indoor maps.
15
+
The [data registry] service enables you to register data content in an Azure Storage Account with your Azure Maps account. An example of data might include a collection of Geofences used in the Azure Maps Geofencing Service. Another example is ZIP files containing drawing packages (DWG) or GeoJSON files that Azure Maps Creator uses to create or update indoor maps.
16
16
17
17
## Prerequisites
18
18
19
-
-[Azure Maps account][Azure Maps account].
20
-
-[Subscription key][subscription key].
21
-
- An [Azure storage account][create storage account].
19
+
-[Azure Maps account]
20
+
-[Subscription key]
21
+
- An [Azure storage account][create storage account]
22
22
23
23
>[!IMPORTANT]
24
24
>
25
25
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your account 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).
26
26
> - In the URL examples in this article you will need to replace:
27
-
> -`{Azure-Maps-Subscription-key}` with your Azure Maps [subscription key][subscription key].
27
+
> -`{Azure-Maps-Subscription-key}` with your Azure Maps [subscription key].
28
28
> -`{udid}` with the user data ID of your data registry. For more information, see [The user data ID](#the-user-data-id).
29
29
30
-
## Preparing to register data in Azure Maps
30
+
## Prepare to register data in Azure Maps
31
31
32
32
Before you can register data in Azure Maps, you need to create an environment containing all of the required components. You need a storage account with one or more containers that hold the files you wish to register and managed identities for authentication. This section explains how to prepare your Azure environment to register data in Azure Maps.
33
33
@@ -41,15 +41,15 @@ Use the following steps to create a managed identity, add it to your Azure Maps
41
41
42
42
Create a system assigned managed identity:
43
43
44
-
1. Go to your Azure Maps account in the [Azure portal][Azure portal].
44
+
1. Go to your Azure Maps account in the [Azure portal].
45
45
1. Select **Identity** from the left menu.
46
46
1. Toggle the **Status** to **On**.
47
47
48
48
# [user-assigned](#tab/User-assigned)
49
49
50
50
Create a user assigned managed identity:
51
51
52
-
1. Go to the [Azure portal][Azure portal] and select **Create a resource**.
52
+
1. Go to the [Azure portal] and select **Create a resource**.
53
53
1. In the **Search services and marketplace** control, enter **user assigned managed identity**.
54
54
1. In the **Create User Assigned Managed Identity** page, select your subscription, resource group, region and a name for your managed identify.
55
55
1. Select **Review + create**, then once ready, **Create**.
@@ -62,7 +62,7 @@ Create a user assigned managed identity:
62
62
1. In the **Add user assigned managed identity** screen, select the desired **Subscription** and managed identity.
63
63
1. Select **Add**
64
64
65
-
:::image type="content" source="./media/data-registry/add-user-assigned-managed-identity.png" lightbox="./media/data-registry/add-user-assigned-managed-identity.png" alt-text="Add user assigned managed identity screenshot.":::
65
+
:::image type="content" source="./media/data-registry/add-user-assigned-managed-identity.png" lightbox="./media/data-registry/add-user-assigned-managed-identity.png" alt-text="A screenshot that demonstrates how to add a user assigned managed identity.":::
66
66
67
67
The user defined managed identity should now be added to your Azure Maps account.
68
68
@@ -74,7 +74,7 @@ For more information, see [managed identities for Azure resources][managed ident
74
74
75
75
Before adding files to a data registry, you must upload them into a container in your [Azure storage account][storage account overview]. Containers are similar to a directory in a file system, they're how your files are organized in your Azure storage account.
76
76
77
-
To create a container in the [Azure portal][Azure portal], follow these steps:
77
+
To create a container in the [Azure portal], follow these steps:
78
78
79
79
1. From within your Azure storage account, select **Containers** from the **Data storage** section in the navigation pane.
80
80
1. Select **+ Container** in the **Containers** pane to bring up the **New container** pane.
@@ -174,7 +174,7 @@ The value used for the `msiClientId` property is the client ID of a user assigne
174
174
#### The blobUrl property
175
175
176
176
The `blobUrl` property is the path to the file being registered. You can get this value from the container that it was added to.
177
-
177
+
[data registry]
178
178
1. Select your **storage account** in the **Azure portal**.
179
179
1. Select **Containers** from the left menu.
180
180
1. A list of containers will appear. Select the container that contains the file you wish to register.
@@ -196,7 +196,7 @@ The user data ID (`udid`) of the data registry is a user-defined GUID that must
196
196
197
197
## Create a data registry
198
198
199
-
Now that you have your storage account with the desired files linked to your Azure Maps account through the datastore and have gathered all required properties, you're ready to use the [data registry][data registry] API to register those files. If you have multiple files in your Azure storage account that you want to register, you'll need to run the register request for each file (`udid`).
199
+
Now that you have your storage account with the desired files linked to your Azure Maps account through the datastore and have gathered all required properties, you're ready to use the [data registry] API to register those files. If you have multiple files in your Azure storage account that you want to register, you'll need to run the register request for each file (`udid`).
200
200
201
201
> [!NOTE]
202
202
> The maximum size of a file that can be registered with an Azure Maps datastore is one gigabyte.
@@ -238,24 +238,19 @@ The value of the **Operation-Location** key is the status URL that you'll use to
238
238
239
239
### Check the data registry creation status
240
240
241
-
To (optionally) check the status of the data registry creation process:
242
-
243
-
1. Enter the status URL you copied in the [Create a data registry](#create-a-data-registry) section, and add your subscription key as a query string parameter. The request should look similar to the following URL:
241
+
To (optionally) check the status of the data registry creation process, enter the status URL you copied in the [Create a data registry](#create-a-data-registry) section, and add your subscription key as a query string parameter. The request should look similar to the following URL:
The following is a sample response showing three possible statuses, completed, running and failed:
261
256
@@ -324,14 +319,11 @@ The data returned when running the list request is similar to the data provided
324
319
325
320
Once you've uploaded one or more files to an Azure storage account, created and Azure Maps datastore to link to those files, then registered them using the [register][register or replace] API, you can access the data contained in the files.
326
321
327
-
To get the content of a file registered in an Azure Maps account:
322
+
Use the `udid` to get the content of a file registered in an Azure Maps account:
328
323
329
-
1. Using the `udid` of the file you want to access, execute the following **HTTP GET request**:
The contents of the file will appear in the body of the response. For example, a text based GeoJSON file will appear similar to the following example:
337
329
@@ -369,10 +361,10 @@ If you need to replace a previously registered file with another file, rerun the
369
361
370
362
When you register a file in Azure Maps using the data registry API, an MD5 hash is created from the contents of the file, encoding it into a 128-bit fingerprint and saving it in the `AzureBlob` as the `contentMD5` property. The MD5 hash stored in the `contentMD5` property is used to ensure the data integrity of the file. Since the MD5 hash algorithm always produces the same output given the same input, the data validation process can compare the `contentMD5` property of the file when it was registered against a hash of the file in the Azure storage account to check that it's intact and unmodified. If the hash isn't the same, the validation fails. If the file in the underlying storage account changes, the validation will fail. If you need to modify the contents of a file that has been registered in Azure Maps, you'll need to register it again.
0 commit comments