Skip to content

Commit a5399cd

Browse files
Merge pull request #229640 from eriklindeman/LinkUpdate
Link update
2 parents eee3200 + 800118d commit a5399cd

38 files changed

+616
-408
lines changed

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

Lines changed: 27 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Azure Maps is a collection of geospatial services and SDKs that use fresh mappin
2626

2727
Additionally, Azure Maps services are available through the Web SDK and the Android SDK. These tools help developers quickly develop and scale solutions that integrate location information into Azure solutions.
2828

29-
You can sign up for a free [Azure Maps account](https://azure.microsoft.com/services/azure-maps/) and start developing.
29+
You can sign up for a free [Azure Maps account] and start developing.
3030

3131
The following video explains Azure Maps in depth:
3232

@@ -54,7 +54,7 @@ Azure Maps consists of the following services that can provide geographic contex
5454

5555
### Data service
5656

57-
Data is imperative for maps. Use the Data service to upload and store geospatial data for use with spatial operations or image composition. Bringing customer data closer to the Azure Maps service will reduce latency, increase productivity, and create new scenarios in your applications. For details on this service, see the [Data service documentation](/rest/api/maps/data-v2).
57+
Data is imperative for maps. Use the Data service to upload and store geospatial data for use with spatial operations or image composition. Bringing customer data closer to the Azure Maps service will reduce latency, increase productivity, and create new scenarios in your applications. For details on this service, see [Data service].
5858

5959
### Geolocation service
6060

@@ -64,7 +64,7 @@ For more details, read the [Geolocation service documentation](/rest/api/maps/ge
6464

6565
### Render service
6666

67-
[Render service V2](/rest/api/maps/render-v2) introduces a new version of the [Get Map Tile V2 API](/rest/api/maps/render-v2/get-map-tile) that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 (where applicable) tile sizes and numerous map types such as road, weather, contour, or map tiles created using Azure Maps Creator. For a complete list, see [TilesetID](/rest/api/maps/render-v2/get-map-tile#tilesetid) in the REST API documentation. It's recommended that you use Render service V2 instead of Render service V1. You're required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service V2, either as basemaps or layers, in any third-party map control. For more information, see [How to use the Get Map Attribution API](how-to-show-attribution.md).
67+
[Render service V2](/rest/api/maps/render-v2) introduces a new version of the [Get Map Tile V2 API](/rest/api/maps/render-v2/get-map-tile) that supports using Azure Maps tiles not only in the Azure Maps SDKs but other map controls as well. It includes raster and vector tile formats, 256x256 or 512x512 (where applicable) tile sizes and numerous map types such as road, weather, contour, or map tiles created using Azure Maps Creator. For a complete list, see [TilesetID] in the REST API documentation. It's recommended that you use Render service V2 instead of Render service V1. You're required to display the appropriate copyright attribution on the map anytime you use the Azure Maps Render service V2, either as basemaps or layers, in any third-party map control. For more information, see [How to use the Get Map Attribution API](how-to-show-attribution.md).
6868

6969
:::image type="content" source="./media/about-azure-maps/intro_map.png" border="false" alt-text="Example of a map from the Render service V2":::
7070

@@ -168,19 +168,19 @@ Maps Creator service is a suite of web services that developers can use to creat
168168

169169
Maps Creator provides the following services:
170170

171-
* [Dataset service][Dataset service]. Use the Dataset service to create a dataset from a converted drawing package data. For information about Drawing package requirements, see Drawing package requirements.
171+
* [Dataset service]. Use the Dataset service to create a dataset from a converted drawing package data. For information about drawing package requirements, see drawing package requirements.
172172

173-
* [Conversion service][Conversion service]. Use the Conversion service to convert a DWG design file into drawing package data for indoor maps.
173+
* [Conversion service]. Use the Conversion service to convert a DWG design file into drawing package data for indoor maps.
174174

175-
* [Tileset service][Tileset]. Use the Tileset service to create a vector-based representation of a dataset. Applications can use a tileset to present a visual tile-based view of the dataset.
175+
* [Tileset service]. Use the Tileset service to create a vector-based representation of a dataset. Applications can use a tileset to present a visual tile-based view of the dataset.
176176

177-
* [Custom styling service][Custom styling] (preview). Use the [style service][style] or [visual style editor][style editor] to customize the visual elements of an indoor map.
177+
* [Custom styling service] (preview). Use the [style service] or [visual style editor] to customize the visual elements of an indoor map.
178178

179-
* [Feature State service][FeatureState]. Use the Feature State service to support dynamic map styling. Dynamic map styling allows applications to reflect real-time events on spaces provided by IoT systems.
179+
* [Feature State service]. Use the Feature State service to support dynamic map styling. Dynamic map styling allows applications to reflect real-time events on spaces provided by IoT systems.
180180

181-
* [WFS service][WFS]. Use the WFS service to query your indoor map data. The WFS service follows the [Open Geospatial Consortium API](https://docs.opengeospatial.org/is/17-069r3/17-069r3.html) standards for querying a single dataset.
181+
* [WFS service]. Use the WFS service to query your indoor map data. The WFS service follows the [Open Geospatial Consortium API] standards for querying a single dataset.
182182

183-
* [Wayfinding service][wayfinding-preview] (preview). Use the [wayfinding API][wayfind] to generate a path between two points within a facility. Use the [routeset API][routeset] to create the data that the wayfinding service needs to generate paths.
183+
* [Wayfinding service] (preview). Use the [wayfinding API] to generate a path between two points within a facility. Use the [routeset API] to create the data that the wayfinding service needs to generate paths.
184184

185185
### Elevation service
186186

@@ -210,7 +210,7 @@ For more information, see the [Get started with Azure Maps Power BI visual](powe
210210

211211
## Usage
212212

213-
To access Azure Maps services, go to the [Azure portal](https://portal.azure.com) and create an Azure Maps account.
213+
To access Azure Maps services, go to the [Azure portal] and create an Azure Maps account.
214214

215215
Azure Maps uses a key-based authentication scheme. When you create your account, two keys are generated. To authenticate for Azure Maps services, you can use either key.
216216

@@ -236,16 +236,22 @@ Try a sample app that showcases Azure Maps:
236236

237237
Stay up to date on Azure Maps:
238238

239-
[Azure Maps blog](https://azure.microsoft.com/blog/topics/azure-maps/)
239+
[Azure Maps blog]
240240

241+
[Data service]: /rest/api/maps/data-v2
241242
[Dataset service]: creator-indoor-maps.md#datasets
242243
[Conversion service]: creator-indoor-maps.md#convert-a-drawing-package
243-
[Tileset]: creator-indoor-maps.md#tilesets
244-
[Custom styling]: creator-indoor-maps.md#custom-styling-preview
245-
[style]: /rest/api/maps/v20220901preview/style
246-
[style editor]: https://azure.github.io/Azure-Maps-Style-Editor
247-
[FeatureState]: creator-indoor-maps.md#feature-statesets
248-
[WFS]: creator-indoor-maps.md#web-feature-service-api
249-
[wayfinding-preview]: creator-indoor-maps.md#wayfinding-preview
250-
[wayfind]: /rest/api/maps/v20220901preview/wayfinding
251-
[routeset]: /rest/api/maps/v20220901preview/routeset
244+
[Tileset service]: creator-indoor-maps.md#tilesets
245+
[Custom styling service]: creator-indoor-maps.md#custom-styling-preview
246+
[style service]: /rest/api/maps/v20220901preview/style
247+
[visual style editor]: https://azure.github.io/Azure-Maps-Style-Editor
248+
[Feature State service]: creator-indoor-maps.md#feature-statesets
249+
[WFS service]: creator-indoor-maps.md#web-feature-service-api
250+
[Wayfinding service]: creator-indoor-maps.md#wayfinding-preview
251+
[wayfinding API]: /rest/api/maps/v20220901preview/wayfinding
252+
[routeset API]: /rest/api/maps/v20220901preview/routeset
253+
[Open Geospatial Consortium API]: https://docs.opengeospatial.org/is/17-069r3/17-069r3.html
254+
[Azure portal]: https://portal.azure.com
255+
[Azure Maps account]: https://azure.microsoft.com/services/azure-maps/
256+
[TilesetID]: /rest/api/maps/render-v2/get-map-tile#tilesetid
257+
[Azure Maps blog]: https://azure.microsoft.com/blog/topics/azure-maps/

articles/azure-maps/add-tile-layer-map-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ A Tile layer loads in tiles from a server. These images can be pre-rendered and
1818

1919
* X, Y, Zoom notation - Based on the zoom level, x is the column and y is the row position of the tile in the tile grid.
2020
* Quadkey notation - Combination x, y, zoom information into a single string value that is a unique identifier for a tile.
21-
* Bounding Box - Bounding box coordinates can be used to specify an image in the format `{west},{south},{east},{north}`, which is commonly used by [web-mapping Services (WMS)](https://www.opengeospatial.org/standards/wms).
21+
* Bounding Box - Bounding box coordinates can be used to specify an image in the format `{west},{south},{east},{north}`, which is commonly used by [web-mapping services (WMS)](https://www.opengeospatial.org/standards/wms).
2222

2323
> [!TIP]
2424
> A TileLayer is a great way to visualize large data sets on the map. Not only can a tile layer be generated from an image, but vector data can also be rendered as a tile layer too. By rendering vector data as a tile layer, the map control only needs to load the tiles, which can be much smaller in file size than the vector data they represent. This technique is used by many who need to render millions of rows of data on the map.

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ For general information about authenticating with Azure AD, see [Authentication
5151

5252
## Managed identities for Azure resources and Azure Maps
5353

54-
[Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) provide Azure services with an automatically managed application based security principal that can authenticate with Azure AD. With Azure role-based access control (Azure RBAC), the managed identity security principal can be authorized to access Azure Maps services. Some examples of managed identities include: Azure App Service, Azure Functions, and Azure Virtual Machines. For a list of managed identities, see [Services that support managed identities for Azure resources](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md). For more information on managed identities, see [Manage authentication in Azure Maps](./how-to-manage-authentication.md).
54+
[Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) provide Azure services with an automatically managed application based security principal that can authenticate with Azure AD. With Azure role-based access control (Azure RBAC), the managed identity security principal can be authorized to access Azure Maps services. Some examples of managed identities include: Azure App Service, Azure Functions, and Azure Virtual Machines. For a list of managed identities, see [Azure services that can use managed identities to access other services](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md). For more information on managed identities, see [Manage authentication in Azure Maps](./how-to-manage-authentication.md).
5555

5656
### Configure application Azure AD authentication
5757

@@ -120,11 +120,11 @@ The following role definition types exist to support application scenarios.
120120
121121
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.
122122
123-
| Azure Maps Service | Azure Maps Role Definition |
123+
| Azure Maps service | Azure Maps Role Definition |
124124
| :--------------------- | :-------------------------- |
125-
| [Data](/rest/api/maps/data) | Azure Maps Data Contributor |
126-
| [Creator](/rest/api/maps-creator/) | Azure Maps Data Contributor |
127-
| [Spatial](/rest/api/maps/spatial) | Azure Maps Data Contributor |
125+
| [Data](/rest/api/maps/data) | Azure Maps Data Contributor |
126+
| [Creator](/rest/api/maps-creator/) | Azure Maps Data Contributor |
127+
| [Spatial](/rest/api/maps/spatial) | Azure Maps Data Contributor |
128128
| Batch [Search](/rest/api/maps/search) and [Route](/rest/api/maps/route) | Azure Maps Data Contributor |
129129
130130
For information about viewing your Azure RBAC settings, see [How to configure Azure RBAC for Azure Maps](./how-to-manage-authentication.md).
@@ -154,7 +154,7 @@ Assigning a role assignment to a resource group can enable access to multiple Az
154154
155155
## Disable local authentication
156156
157-
Azure Maps accounts support the standard Azure property in the [Azure Maps Management REST API](/rest/api/maps-management/) for `Microsoft.Maps/accounts` called `disableLocalAuth`. When `true`, all authentication to the Azure Maps data-plane REST API is disabled, except [Azure AD authentication](./azure-maps-authentication.md#azure-ad-authentication). This is configured using Azure Policy to control distribution and management of shared keys and SAS tokens. For more information, see [What is Azure Policy?](../governance/policy/overview.md).
157+
Azure Maps accounts support the standard Azure property in the [Management API](/rest/api/maps-management/) for `Microsoft.Maps/accounts` called `disableLocalAuth`. When `true`, all authentication to the Azure Maps data-plane REST API is disabled, except [Azure AD authentication](./azure-maps-authentication.md#azure-ad-authentication). This is configured using Azure Policy to control distribution and management of shared keys and SAS tokens. For more information, see [What is Azure Policy?](../governance/policy/overview.md).
158158
159159
Disabling local authentication doesn't take effect immediately. Allow a few minutes for the service to block future authentication requests. To re-enable local authentication, set the property to `false` and after a few minutes local authentication will resume.
160160
@@ -212,9 +212,9 @@ Consider the application topology where the endpoint `https://us.atlas.microsoft
212212

213213
As described in [Azure Maps rate limits](./azure-maps-qps-rate-limits.md), individual service offerings have varying rate limits that are enforced as an aggregate of the account.
214214

215-
Consider the case of **Search Service - Non-Batch Reverse**, with its limit of 250 queries per second (QPS) for the following tables. Each table represents estimated total successful transactions from example usage.
215+
Consider the case of **Search service - Non-Batch Reverse**, with its limit of 250 queries per second (QPS) for the following tables. Each table represents estimated total successful transactions from example usage.
216216

217-
The first table shows one token that has a maximum request per second of 500, and then actual usage of the application was 500 request per second for a duration of 60 seconds. **Search Service - Non-Batch Reverse** has a rate limit of 250, meaning of the total 30,000 requests made in the 60 seconds; 15,000 of those requests will be billable transactions. The remaining requests will result in status code `429 (TooManyRequests)`.
217+
The first table shows one token that has a maximum request per second of 500, and then actual usage of the application was 500 request per second for a duration of 60 seconds. **Search service - Non-Batch Reverse** has a rate limit of 250, meaning of the total 30,000 requests made in the 60 seconds; 15,000 of those requests will be billable transactions. The remaining requests will result in status code `429 (TooManyRequests)`.
218218

219219
| Name | Approximate Maximum Rate Per Second | Actual Rate Per Second | Duration of sustained rate in seconds | Approximate total successful transactions |
220220
| :---- | :---------------------------------- | :--------------------- | :------------------------------------ | :---------------------------------------- |

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

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -16,27 +16,27 @@ Azure Maps does not have any maximum daily limits on the number of requests that
1616

1717
Below are the QPS usage limits for each Azure Maps service by Pricing Tier.
1818

19-
| Azure Maps Service | QPS Limit: Gen 2 Pricing Tier | QPS Limit: Gen 1 S1 Pricing Tier | QPS Limit: Gen 1 S0 Pricing Tier |
19+
| Azure Maps service | QPS Limit: Gen 2 Pricing Tier | QPS Limit: Gen 1 S1 Pricing Tier | QPS Limit: Gen 1 S0 Pricing Tier |
2020
| ----------------- | :--------------------------: | :------------------------------: | :------------------------: |
21-
| Copyright Service | 10 | 10 | 10 |
21+
| Copyright service | 10 | 10 | 10 |
2222
| Creator - Alias, TilesetDetails | 10 | Not Available | Not Available |
2323
| Creator - Conversion, Dataset, Feature State, WFS | 50 | Not Available | Not Available |
24-
| Data Service | 50 | 50 | Not Available |
25-
| Elevation Service | 50 | 50 | Not Available |
26-
| Geolocation Service | 50 | 50 | 50 |
27-
| Render Service - Contour tiles, Digital Elevation Model (DEM) tiles and Customer tiles | 50 | 50 | Not Available |
28-
| Render Service - Traffic tiles and Static maps | 50 | 50 | 50 |
29-
| Render Service - Road tiles | 500 | 500 | 50 |
30-
| Render Service - Satellite tiles | 250 | 250 | Not Available |
31-
| Render Service - Weather tiles | 100 | 100 | 50 |
32-
| Route Service - Batch | 10 | 10 | Not Available |
33-
| Route Service - Non-Batch | 50 | 50 | 50 |
34-
| Search Service - Batch | 10 | 10 | Not Available |
35-
| Search Service - Non-Batch | 500 | 500 | 50 |
36-
| Search Service - Non-Batch Reverse | 250 | 250 | 50 |
37-
| Spatial Service | 50 | 50 | Not Available |
38-
| Timezone Service | 50 | 50 | 50 |
39-
| Traffic Service | 50 | 50 | 50 |
40-
| Weather Service | 50 | 50 | 50 |
24+
| Data service | 50 | 50 | Not Available |
25+
| Elevation service | 50 | 50 | Not Available |
26+
| Geolocation service | 50 | 50 | 50 |
27+
| Render service - Contour tiles, Digital Elevation Model (DEM) tiles and Customer tiles | 50 | 50 | Not Available |
28+
| Render service - Traffic tiles and Static maps | 50 | 50 | 50 |
29+
| Render service - Road tiles | 500 | 500 | 50 |
30+
| Render service - Satellite tiles | 250 | 250 | Not Available |
31+
| Render service - Weather tiles | 100 | 100 | 50 |
32+
| Route service - Batch | 10 | 10 | Not Available |
33+
| Route service - Non-Batch | 50 | 50 | 50 |
34+
| Search service - Batch | 10 | 10 | Not Available |
35+
| Search service - Non-Batch | 500 | 500 | 50 |
36+
| Search service - Non-Batch Reverse | 250 | 250 | 50 |
37+
| Spatial service | 50 | 50 | Not Available |
38+
| Timezone service | 50 | 50 | 50 |
39+
| Traffic service | 50 | 50 | 50 |
40+
| Weather service | 50 | 50 | 50 |
4141

4242
When QPS limits are reached, an HTTP 429 error will be returned. If you are using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps *Technical* Support Request in the [Azure portal](https://portal.azure.com/) to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier cannot be increased.

articles/azure-maps/creator-facility-ontology.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,13 @@ Facility ontology defines how Azure Maps Creator internally stores facility data
1919

2020
:::zone pivot="facility-ontology-v1"
2121

22-
The Facility 1.0 contains revisions for the Facility feature class definitions for [Azure Maps Services](https://aka.ms/AzureMaps).
22+
The Facility 1.0 contains revisions for the Facility feature class definitions for [Azure Maps services](https://aka.ms/AzureMaps).
2323

2424
:::zone-end
2525

2626
:::zone pivot="facility-ontology-v2"
2727

28-
The Facility 2.0 contains revisions for the Facility feature class definitions for [Azure Maps Services](https://aka.ms/AzureMaps).
28+
The Facility 2.0 contains revisions for the Facility feature class definitions for [Azure Maps services](https://aka.ms/AzureMaps).
2929

3030
:::zone-end
3131

0 commit comments

Comments
 (0)