Skip to content

Commit e82fc96

Browse files
committed
Retirement.
1 parent 08e32b4 commit e82fc96

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

articles/azure-maps/azure-maps-qps-rate-limits.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
2424
| Azure Maps service | QPS Limit: Gen 2 Pricing Tier | QPS Limit: Gen 1 S1 Pricing Tier | QPS Limit: Gen 1 S0 Pricing Tier |
2525
| ----------------- | :--------------------------: | :------------------------------: | :------------------------: |
2626
| Copyright service | 10 | 10 | 10 |
27-
| (Deprecated<sup>1</sup>) Creator - Alias | 10 | Not Available | Not Available |
28-
| (Deprecated<sup>1</sup>) Creator - Conversion, Dataset, Feature State, Features, Map Configuration, Style, Routeset, TilesetDetails, Wayfinding | 50 | Not Available | Not Available |
27+
| Creator - Alias (Deprecated<sup>1</sup>) | 10 | Not Available | Not Available |
28+
| Creator - Conversion, Dataset, Feature State, Features, Map Configuration, Style, Routeset, TilesetDetails, Wayfinding (Deprecated<sup>1</sup>) | 50 | Not Available | Not Available |
2929
| Data registry service (Deprecated<sup>1</sup>) | 50 | 50 |  Not Available  |
3030
| Geolocation service | 50 | 50 | 50 |
3131
| Render service - Road tiles | 500 | 500 | 50 |
@@ -38,7 +38,7 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
3838
| Search service - Batch | 10 | 10 | Not Available |
3939
| Search service - Non-Batch | 500 | 500 | 50 |
4040
| Search service - Non-Batch Reverse | 250 | 250 | 50 |
41-
| (Deprecated<sup>1</sup>) Spatial service | 50 | 50 |  Not Available  |
41+
| Spatial service (Deprecated<sup>1</sup>) | 50 | 50 |  Not Available  |
4242
| Timezone service | 50 | 50 | 50 |
4343
| Traffic service | 50 | 50 | 50 |
4444
| Weather service | 50 | 50 | 50 |

articles/azure-maps/how-to-creator-wayfinding.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@ ms.subservice: creator
1212

1313
# Indoor maps wayfinding service (preview)
1414

15+
> [!NOTE]
16+
>
17+
> **Azure Maps Creator retirement**
18+
>
19+
> The Azure Maps Creator indoor map service is now deprecated and will be retired on 9/30/25. For more information, see [End of Life Announcement of Azure Maps Creator](https://aka.ms/AzureMapsCreatorDeprecation).
20+
1521
The Azure Maps Creator [wayfinding service] allows you to navigate from place to place anywhere within your indoor map. The service utilizes stairs and elevators to navigate between floors and provides guidance to help you navigate around physical obstructions. This article describes how to generate a path from a starting point to a destination point in a sample indoor map.
1622

1723
## Prerequisites
@@ -101,12 +107,6 @@ The `facilityId`, a property of the routeset, is a required parameter when searc
101107

102108
## Get a wayfinding path
103109

104-
> [!NOTE]
105-
>
106-
> **Azure Maps Creator retirement**
107-
>
108-
> The Azure Maps Creator indoor map service is now deprecated and will be retired on 9/30/25. For more information, see [End of Life Announcement of Azure Maps Creator](https://aka.ms/AzureMapsCreatorDeprecation).
109-
110110
Use the [wayfinding API] to generate a path from the routeset you created in the previous section. The wayfinding API requires a query that contains start and end points in an indoor map, along with floor level ordinal numbers. For more information about Creator wayfinding, see [wayfinding] in the concepts article.
111111

112112
To create a wayfinding query:

articles/azure-maps/how-to-use-best-practices-for-routing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ With the Azure Maps Route Direction APIs, developers can request details for eac
183183
The following query sets the `sectionType` to `traffic`. It requests the sections that contain traffic information from Seattle to San Diego.
184184

185185
```http
186-
https://atlas.microsoft.com/route/directions/json?subscription-key={Your-Azure-Maps-Subscription-key}&api-version=1.0&sectionType=traffic&query=47.6062,-122.3321:32.7157,-117.1611
186+
https://atlas.microsoft.com/map/tile?subscription-key={Your-Azure-Maps-Subscription-key}&api-version=2024-04-01&tilesetId=microsoft.base.road&zoom=15&x=5236&y=12665&tileSize=256
187187
```
188188

189189
The response contains the sections that are suitable for traffic along the given coordinates.

0 commit comments

Comments
 (0)