Skip to content

Commit 204f26c

Browse files
authored
Merge pull request #193725 from stevemunk/SM-Upload-preview
Remove preview from links to data API
2 parents 3ed40c1 + 18472e7 commit 204f26c

File tree

5 files changed

+10
-10
lines changed

5 files changed

+10
-10
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Work with indoor maps in Azure Maps Creator
33
description: This article introduces concepts that apply to Azure Maps Creator services
44
author: stevemunk
55
ms.author: v-munksteve
6-
ms.date: 01/26/2022
6+
ms.date: 04/01/2022
77
ms.topic: conceptual
88
ms.service: azure-maps
99
services: azure-maps
@@ -57,7 +57,7 @@ Creator services create, store, and use various data types that are defined and
5757

5858
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](drawing-requirements.md).
5959

60-
Use the [Azure Maps Data Upload API](/rest/api/maps/data-v2/update-preview) 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.
60+
Use the [Azure Maps Data Upload API](/rest/api/maps/data-v2/update) 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.
6161

6262
## Convert a Drawing package
6363

articles/azure-maps/how-to-render-custom-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ To upload pins and path data:
164164
```
165165

166166
>[!TIP]
167-
>To obtain your own path and pin location information, use the [Data Upload API](/rest/api/maps/data-v2/upload-preview).
167+
>To obtain your own path and pin location information, use the [Data Upload API](/rest/api/maps/data-v2/upload).
168168
169169
### Check pins and path data upload status
170170

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ This tutorial uses the [Postman](https://www.postman.com/) application, but you
4141
4242
## Upload a Drawing package
4343

44-
Use the [Data Upload API](/rest/api/maps/data-v2/upload-preview) to upload the Drawing package to Azure Maps resources.
44+
Use the [Data Upload API](/rest/api/maps/data-v2/upload) to upload the Drawing package to Azure Maps resources.
4545

4646
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).
4747

@@ -55,7 +55,7 @@ To upload the Drawing package:
5555

5656
4. Select the **POST** HTTP method.
5757

58-
5. Enter the following URL to the [Data Upload API](/rest/api/maps/data-v2/upload-preview) The request should look like the following URL (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key)::
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 (replace `{Azure-Maps-Primary-Subscription-key}` with your primary subscription key)::
5959

6060
```http
6161
https://us.atlas.microsoft.com/mapData?api-version=2.0&dataFormat=dwgzippackage&subscription-key={Your-Azure-Maps-Primary-Subscription-key}

articles/azure-maps/tutorial-ev-routing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ for loc in range(len(searchPolyResponse["results"])):
164164

165165
## Upload the reachable range and charging points to Azure Maps Data service
166166

167-
On a map, you'll want to visualize the charging stations and the boundary for the maximum reachable range of the electric vehicle. To do so, upload the boundary data and charging stations data as geojson objects to Azure Maps Data service. Use the [Data Upload API](/rest/api/maps/data-v2/upload-preview).
167+
On a map, you'll want to visualize the charging stations and the boundary for the maximum reachable range of the electric vehicle. To do so, upload the boundary data and charging stations data as geojson objects to Azure Maps Data service. Use the [Data Upload API](/rest/api/maps/data-v2/upload).
168168

169169
To upload the boundary and charging point data to Azure Maps Data service, run the following two cells:
170170

@@ -326,7 +326,7 @@ routeData = {
326326

327327
## Visualize the route
328328

329-
To help visualize the route, you first upload the route data as a geojson object to Azure Maps Data service . To do so, use the Azure Maps [Data Upload API](/rest/api/maps/data-v2/upload-preview). Then, call the rendering service, [Get Map Image API](/rest/api/maps/render/getmapimage), to render the route on the map, and visualize it.
329+
To help visualize the route, you first upload the route data as a geojson object to Azure Maps Data service . To do so, use the Azure Maps [Data Upload API](/rest/api/maps/data-v2/upload). Then, call the rendering service, [Get Map Image API](/rest/api/maps/render/getmapimage), to render the route on the map, and visualize it.
330330

331331
To get an image for the rendered route on the map, run the following script:
332332

@@ -383,7 +383,7 @@ To explore the Azure Maps APIs that are used in this tutorial, see:
383383

384384
* [Get Route Range](/rest/api/maps/route/getrouterange)
385385
* [Post Search Inside Geometry](/rest/api/maps/search/postsearchinsidegeometry)
386-
* [Data Upload](/rest/api/maps/data-v2/upload-preview)
386+
* [Data Upload](/rest/api/maps/data-v2/upload)
387387
* [Render - Get Map Image](/rest/api/maps/render/getmapimage)
388388
* [Post Route Matrix](/rest/api/maps/route/postroutematrix)
389389
* [Get Route Directions](/rest/api/maps/route/getroutedirections)

articles/azure-maps/tutorial-geofence.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Azure Maps provides a number of services to support the tracking of equipment en
2323
> [!div class="checklist"]
2424
>
2525
> * Create an Azure Maps account with a global region.
26-
> * Upload [Geofencing GeoJSON data](geofence-geojson.md) that defines the construction site areas you want to monitor. You'll use the [Data Upload API](/rest/api/maps/data-v2/upload-preview) to upload geofences as polygon coordinates to your Azure Maps account.
26+
> * Upload [Geofencing GeoJSON data](geofence-geojson.md) that defines the construction site areas you want to monitor. You'll use the [Data Upload API](/rest/api/maps/data-v2/upload) to upload geofences as polygon coordinates to your Azure Maps account.
2727
> * Set up two [logic apps](../event-grid/handler-webhooks.md#logic-apps) that, when triggered, send email notifications to the construction site operations manager when equipment enters and exits the geofence area.
2828
> * Use [Azure Event Grid](../event-grid/overview.md) to subscribe to enter and exit events for your Azure Maps geofence. You set up two webhook event subscriptions that call the HTTP endpoints defined in your two logic apps. The logic apps then send the appropriate email notifications of equipment moving beyond or entering the geofence.
2929
> * Use [Search Geofence Get API](/rest/api/maps/spatial/getgeofence) to receive notifications when a piece of equipment exits and enters the geofence areas.
@@ -58,7 +58,7 @@ The Azure CLI command [az maps account create](/cli/azure/maps/account?view=azur
5858
In this tutorial, you''ll upload geofencing GeoJSON data that contains a `FeatureCollection`. The `FeatureCollection` contains two geofences that define polygonal areas within the construction site. The first geofence has no time expiration or restrictions. The second can only be queried against during business hours (9:00 AM-5:00 PM in the Pacific Time zone), and will no longer be valid after January 1, 2022. For more information on the GeoJSON format, see [Geofencing GeoJSON data](geofence-geojson.md).
5959

6060
>[!TIP]
61-
>You can update your geofencing data at any time. For more information, see [Data Upload API](/rest/api/maps/data-v2/upload-preview).
61+
>You can update your geofencing data at any time. For more information, see [Data Upload API](/rest/api/maps/data-v2/upload).
6262
6363
To upload the geofencing GeoJSON data:
6464

0 commit comments

Comments
 (0)