Skip to content

Commit de4b5c7

Browse files
committed
Added retirement banners
1 parent 43dbbf0 commit de4b5c7

14 files changed

+82
-42
lines changed

articles/azure-maps/about-azure-maps.md

Lines changed: 2 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Azure Maps is a collection of geospatial services and SDKs that use fresh mappin
1919
* Various routing options; such as point-to-point, multipoint, multipoint optimization, isochrone, electric vehicle, commercial vehicle, traffic influenced, and matrix routing.
2020
* Traffic flow view and incidents view, for applications that require real-time traffic information.
2121
* Time zone and Geolocation services.
22-
* Geofencing service and mapping data storage, with location information hosted in Azure.
22+
* Geofencing service with location information hosted in Azure.
2323
* Location intelligence through geospatial analytics.
2424

2525
Additionally, Azure Maps services are available through the Web SDK. These tools help developers quickly develop and scale solutions that integrate location information into Azure solutions.
@@ -56,16 +56,6 @@ Use the Azure Maps Android SDK to create mobile mapping applications.
5656

5757
Azure Maps consists of the following services that can provide geographic context to your Azure applications.
5858

59-
### Data registry service
60-
61-
Data is imperative for maps. Use the Data registry service to access geospatial data, used with spatial operations or image composition, previously uploaded to your [Azure Storage]. By bringing customer data closer to the Azure Maps service, you reduce latency and increase productivity. For more information, see [Data registry] in the Azure Maps REST API documentation.
62-
63-
> [!NOTE]
64-
>
65-
> **Azure Maps Data service retirement**
66-
>
67-
> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data registry] service by 9/16/24. For more information, see [How to create data registry].
68-
6959
### Geolocation service
7060

7161
Use the Geolocation service to retrieve the two-letter country/region code for an IP address. This service can help you enhance user experience by providing customized application content based on geographic location.
@@ -113,12 +103,6 @@ The Search service also provides advanced features such as:
113103

114104
For more information, see [Search] in the Azure Maps REST API documentation.
115105

116-
### Spatial service
117-
118-
The Spatial service quickly analyzes location information to help inform customers of ongoing events happening in time and space. It enables near real-time analysis and predictive modeling of events.
119-
120-
The service enables customers to enhance their location intelligence with a library of common geospatial mathematical calculations. Common calculations include closest point, great circle distance, and buffers. For more information about the Spatial service and its various features, see [Spatial] in the Azure Maps REST API documentation.
121-
122106
### Timezone service
123107

124108
The Time zone service enables you to query current, historical, and future time zone information. You can use either latitude and longitude pairs or an [IANA ID] as an input. The Time zone service also allows for:
@@ -223,15 +207,11 @@ Stay up to date on Azure Maps:
223207
[Azure Maps blog]
224208

225209
<!--------- learn.microsoft.com links --------------->
226-
[Azure Storage]: ../storage/common/storage-introduction.md
227210
[Get started with Azure Maps Power BI visual]: power-bi-visual-get-started.md
228211
[How to use the Get Map Attribution API]: how-to-show-attribution.md
229212
[Quickstart: Create a web app]: quick-demo-map-app.md
230-
[v1]: /rest/api/maps/data?view=rest-maps-1.0&preserve-view=true
231-
[v2]: /rest/api/maps/data
232-
[How to create data registry]: how-to-create-data-registries.md
213+
233214
<!--------- REST API Links --------------->
234-
[Data registry]: /rest/api/maps/data-registry
235215
[Geolocation]: /rest/api/maps/geolocation
236216
[Get Map Tile]: /rest/api/maps/render/get-map-tile
237217
[Get Weather along route API]: /rest/api/maps/weather/getweatheralongroute
@@ -241,7 +221,6 @@ Stay up to date on Azure Maps:
241221
[REST APIs]: /rest/api/maps/
242222
[Route]: /rest/api/maps/route
243223
[Search]: /rest/api/maps/search?view=rest-maps-1.0&preserve-view=true
244-
[Spatial]: /rest/api/maps/spatial
245224
[TilesetID]: /rest/api/maps/render/get-map-tile#tilesetid
246225
[Timezone]: /rest/api/maps/timezone
247226
[Traffic]: /rest/api/maps/traffic

articles/azure-maps/azure-maps-authentication.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -125,12 +125,13 @@ The following role definition types exist to support application scenarios.
125125
126126
Some Azure Maps services may require elevated privileges to perform write or delete actions on Azure Maps REST APIs. Azure Maps Data Contributor role is required for services, which provide write or delete actions. The following table describes what services Azure Maps Data Contributor is applicable when using write or delete actions. When only read actions are required, the Azure Maps Data Reader role can be used in place of the Azure Maps Data Contributor role.
127127
128-
| Azure Maps service | Azure Maps Role Definition |
129-
| :--------------------------| :-------------------------- |
130-
| [Data] | Azure Maps Data Contributor |
131-
| [Creator] | Azure Maps Data Contributor |
132-
| [Spatial] | Azure Maps Data Contributor |
133-
| Batch [Search] and [Route] | Azure Maps Data Contributor |
128+
| Azure Maps service | Azure Maps Role Definition |
129+
| :----------------------------------| :-------------------------- |
130+
| [Creator] (Deprecated<sup>1</sup>) | Azure Maps Data Contributor |
131+
| [Spatial] (Deprecated<sup>1</sup>) | Azure Maps Data Contributor |
132+
| Batch [Search] and [Route] | Azure Maps Data Contributor |
133+
134+
<sup>1</sup> Azure Maps Creator, and the Data registry and Spatial services are now deprecated and will be retired on 9/30/25.
134135
135136
For information about viewing your Azure RBAC settings, see [How to configure Azure RBAC for Azure Maps].
136137

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

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,9 @@ 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-
| Creator - Alias | 10 | Not Available | Not Available |
28-
| Creator - Conversion, Dataset, Feature State, Features, Map Configuration, Style, Routeset, TilesetDetails, Wayfinding | 50 | Not Available | Not Available |
29-
| Data registry service | 50 | 50 |  Not Available  |
30-
| Data service (Deprecated<sup>1</sup>) | 50 | 50 |  Not Available  |
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 |
29+
| Data registry service (Deprecated<sup>1</sup>) | 50 | 50 |  Not Available  |
3130
| Geolocation service | 50 | 50 | 50 |
3231
| Render service - Road tiles | 500 | 500 | 50 |
3332
| Render service - Satellite tiles | 250 | 250 | Not Available |
@@ -39,12 +38,12 @@ The following list shows the QPS usage limits for each Azure Maps service by Pri
3938
| Search service - Batch | 10 | 10 | Not Available |
4039
| Search service - Non-Batch | 500 | 500 | 50 |
4140
| Search service - Non-Batch Reverse | 250 | 250 | 50 |
42-
| Spatial service | 50 | 50 |  Not Available  |
41+
| (Deprecated<sup>1</sup>) Spatial service | 50 | 50 |  Not Available  |
4342
| Timezone service | 50 | 50 | 50 |
4443
| Traffic service | 50 | 50 | 50 |
4544
| Weather service | 50 | 50 | 50 |
4645

47-
<sup>1</sup> The Azure Maps Data service (both [v1] and [v2]) is now deprecated and will be retired on 9/16/24. To avoid service disruptions, all calls to the Data service will need to be updated to use the Azure Maps [Data Registry] service by 9/16/24. For more information, see [How to create data registry].
46+
<sup>1</sup> Azure Maps Creator, and the Data registry and Spatial services are now deprecated and will be retired on 9/30/25.
4847

4948
When QPS limits are reached, an HTTP 429 error is returned. If you're using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps *Technical* Support Request in the [Azure portal] to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier can't be increased.
5049

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

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

1414
# Creator for indoor maps
1515

16+
> [!NOTE]
17+
>
18+
> **Azure Maps Creator retirement**
19+
>
20+
> The Azure Maps Creator is now deprecated and will be retired on 9/30/25.
21+
1622
This article introduces concepts and tools that apply to Azure Maps Creator. We recommend that you read this article before you begin to use the Azure Maps Creator API and SDK.
1723

1824
You can use Creator to develop applications with map features that are based on indoor map data. This article describes the process of uploading, converting, creating, and using your map data. Typically, the workflow is completed by two different personas with distinct areas of expertise and responsibility:

articles/azure-maps/how-to-create-data-registries.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,12 @@ ms.subservice: data-registry
1212

1313
# How to create data registry
1414

15+
> [!NOTE]
16+
>
17+
> **Azure Maps Data registry service retirement**
18+
>
19+
> The Azure Maps Data registry service is now deprecated and will be retired on 9/30/25.
20+
1521
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.
1622

1723
## Prerequisites
@@ -142,11 +148,13 @@ The `AzureBlob` is a JSON object that defines properties required to create the
142148
| Property | Description |
143149
|----------------|------------------------------------------------------------------------------------------|
144150
| `kind` | Defines what type of object being registered. Currently **AzureBlob** is the only kind that is supported. |
145-
| `dataFormat` | The data format of the file located in **blobUrl**. Its format can either be **GeoJSON** for the spatial service or **ZIP** for the conversion service. |
151+
| `dataFormat` | The data format of the file located in **blobUrl**. Its format can either be **GeoJSON** for the spatial service (Deprecated<sup>1</sup>) or **ZIP** for the conversion service (Deprecated<sup>1</sup>). |
146152
| `msiClientId` | The ID of the managed identity being used to create the data registry. |
147153
|`linkedResource`| The ID of the datastore registered in the Azure Maps account.<BR>The datastore contains a link to the file being registered. |
148154
| `blobUrl` | A URL pointing to the Location of the AzurebBlob, the file imported into your container. |
149155

156+
<sup>1</sup> Azure Maps Creator, and the Data registry and Spatial services are now deprecated and will be retired on 9/30/25.
157+
150158
The following two sections provide you with details how to get the values to use for the [msiClientId], [blobUrl] properties.
151159

152160
#### The msiClientId property

articles/azure-maps/how-to-use-spatial-io-module.md

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

1313
# How to use the Azure Maps Spatial IO module
1414

15+
> [!NOTE]
16+
>
17+
> **Azure Maps Spatial service retirement**
18+
>
19+
> The Azure Maps Spatial service is now deprecated and will be retired on 9/30/25.
20+
1521
The Azure Maps Web SDK provides the [Spatial IO module], which integrates spatial data with the Azure Maps web SDK using JavaScript or TypeScript. The robust features in this module allow developers to:
1622

1723
- [Read and write spatial data]. Supported file formats include: KML, KMZ, GPX, GeoRSS, GML, GeoJSON and CSV files containing columns with spatial information. Also supports Well-Known Text (WKT).

articles/azure-maps/migrate-from-google-maps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,11 @@ If you don't have an Azure subscription, create a [free account] before you begi
3131
3232
## Azure Maps platform overview
3333

34-
Azure Maps provides developers from all industries powerful geospatial capabilities. The capabilities are packed with regularly updated map data to provide geographic context for web, and mobile applications. Azure Maps has an Azure One API compliant set of REST APIs. The REST APIs offer Maps Rendering, Search, Routing, Traffic, Time Zones, Geolocation, Geofencing, Map Data, Weather, and Spatial Operations. Operations are accompanied by both Web and Android SDKs to make development easy, flexible, and portable across multiple platforms.
34+
Azure Maps provides developers from all industries powerful geospatial capabilities. The capabilities are packed with regularly updated map data to provide geographic context for web, and mobile applications. Azure Maps has an Azure One API compliant set of REST APIs. The REST APIs offer Maps Rendering, Search, Routing, Traffic, Time Zones, Geolocation, Geofencing, Map Data, and Weather. Operations are accompanied by both Web and Android SDKs to make development easy, flexible, and portable across multiple platforms.
3535

3636
## High-level platform comparison
3737

38-
The table provides a high-level list of Azure Maps features, which correspond to Google Maps features. This list doesn't show all Azure Maps features. Other Azure Maps features include: accessibility, geofencing, isochrones, spatial operations, direct map tile access, batch services, and data coverage comparisons (that is, imagery coverage).
38+
The table provides a high-level list of Azure Maps features, which correspond to Google Maps features. This list doesn't show all Azure Maps features. Other Azure Maps features include: accessibility, geofencing, isochrones, direct map tile access, batch services, and data coverage comparisons (that is, imagery coverage).
3939

4040
| Google Maps feature | Azure Maps support |
4141
|-----------------------------|:--------------------------------------:|

articles/azure-maps/release-notes-spatial-module.md

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

1313
# Spatial IO Module release notes
1414

15+
> [!NOTE]
16+
>
17+
> **Azure Maps Spatial service retirement**
18+
>
19+
> The Azure Maps Spatial service is now deprecated and will be retired on 9/30/25.
20+
1521
This document contains information about new features and other changes to the Azure Maps Spatial IO Module.
1622

1723
## [0.1.8] (February 22, 2024)

articles/azure-maps/spatial-io-add-simple-data-layer.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,12 @@ ms.subservice: web-sdk
1313

1414
# Add a simple data layer
1515

16+
> [!NOTE]
17+
>
18+
> **Azure Maps Spatial service retirement**
19+
>
20+
> The Azure Maps Spatial service is now deprecated and will be retired on 9/30/25.
21+
1622
The spatial IO module provides a `SimpleDataLayer` class. This class makes it easy to render styled features on the map. It can even render data sets that have style properties and data sets that contain mixed geometry types. The simple data layer achieves this functionality by wrapping multiple rendering layers and using style expressions. The style expressions search for common style properties of the features inside these wrapped layers. The `atlas.io.read` function and the `atlas.io.write` function use these properties to read and write styles into a supported file format. After adding the properties to a supported file format, the file can be used for various purposes. For example, the file can be used to display the styled features on the map.
1723

1824
In addition to styling features, the `SimpleDataLayer` provides a built-in popup feature with a popup template. The popup displays when a feature is selected. The default popup feature can be disabled, if desired. This layer also supports clustered data. When a cluster is clicked, the map zooms into the cluster and expands it into individual points and subclusters.

articles/azure-maps/spatial-io-connect-wfs-service.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ ms.subservice: web-sdk
1111

1212
# Connect to a WFS service
1313

14+
> [!NOTE]
15+
>
16+
> **Azure Maps Spatial service retirement**
17+
>
18+
> The Azure Maps Spatial service is now deprecated and will be retired on 9/30/25.
19+
1420
A Web Feature Service (WFS) is a web service for querying spatial data that has a standardized API defined by the Open Geospatial Consortium (OGC). The `WfsClient` class in the spatial IO module lets developers connect to a WFS service and query data from the service.
1521

1622
The `WfsClient` class supports the following features:

0 commit comments

Comments
 (0)