Skip to content

Commit a43e40a

Browse files
committed
replaced 'render v2' with 'render'.
1 parent 123153b commit a43e40a

File tree

5 files changed

+15
-16
lines changed

5 files changed

+15
-16
lines changed

articles/azure-maps/create-data-source-android-sdk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -773,7 +773,7 @@ Azure Maps adheres to the [Mapbox Vector Tile Specification], an open standard.
773773
- [Road tiles]
774774
- [Traffic incidents]
775775
- [Traffic flow]
776-
- Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render V2-Get Map Tile API]
776+
- Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render - Get Map Tile] API
777777

778778
> [!TIP]
779779
> When using vector or raster image tiles from the Azure Maps render service with the web SDK, you can replace `atlas.microsoft.com` with the placeholder `azmapsdomain.invalid`. This placeholder will be replaced with the same domain used by the map and will automatically append the same authentication details as well. This greatly simplifies authentication with the render service when using Azure Active Directory authentication.
@@ -1048,6 +1048,6 @@ See the following articles for more code samples to add to your maps:
10481048
[Road tiles]: /rest/api/maps/render-v2/get-map-tile
10491049
[Traffic incidents]: /rest/api/maps/traffic/gettrafficincidenttile
10501050
[Traffic flow]: /rest/api/maps/traffic/gettrafficflowtile
1051-
[Render V2-Get Map Tile API]: /rest/api/maps/render-v2/get-map-tile
1051+
[Render - Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
10521052
<!--------- External Links --------------->
10531053
[Mapbox Vector Tile Specification]: https://github.com/mapbox/vector-tile-spec

articles/azure-maps/create-data-source-ios-sdk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -312,7 +312,7 @@ Azure Maps adheres to the [Mapbox Vector Tile Specification], an open standard.
312312
- [Road tiles]
313313
- [Traffic incidents]
314314
- [Traffic flow]
315-
- Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render V2-Get Map Tile API]
315+
- Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render - Get Map Tile] API
316316

317317
> [!TIP]
318318
> When using vector or raster image tiles from the Azure Maps render service with the iOS SDK, you can replace `atlas.microsoft.com` with the `AzureMap`'s property' `domainPlaceholder`. This placeholder will be replaced with the same domain used by the map and will automatically append the same authentication details as well. This greatly simplifies authentication with the render service when using Azure Active Directory authentication.
@@ -498,6 +498,6 @@ See the following articles for more code samples to add to your maps:
498498
[Road tiles]: /rest/api/maps/render-v2/get-map-tile
499499
[Traffic incidents]: /rest/api/maps/traffic/gettrafficincidenttile
500500
[Traffic flow]: /rest/api/maps/traffic/gettrafficflowtile
501-
[Render V2-Get Map Tile API]: /rest/api/maps/render-v2/get-map-tile
501+
[Render - Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
502502
<!--------- External Links --------------->
503503
[Mapbox Vector Tile Specification]: https://github.com/mapbox/vector-tile-spec

articles/azure-maps/create-data-source-web-sdk.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Azure Maps adheres to the [Mapbox Vector Tile Specification], an open standard.
8080
* [Road tiles]
8181
* [Traffic incidents]
8282
* [Traffic flow]
83-
* Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render V2-Get Map Tile API]
83+
* Azure Maps Creator also allows custom vector tiles to be created and accessed through the [Render - Get Map Tile] API
8484

8585
> [!TIP]
8686
> When using vector or raster image tiles from the Azure Maps render service with the web SDK, you can replace `atlas.microsoft.com` with the placeholder `{azMapsDomain}`. This placeholder will be replaced with the same domain used by the map and will automatically append the same authentication details as well. This greatly simplifies authentication with the render service when using Azure Active Directory authentication.
@@ -271,7 +271,7 @@ See the following articles for more code samples to add to your maps:
271271
[Line layer]: map-add-line-layer.md
272272
[Mapbox Vector Tile Specification]: https://github.com/mapbox/vector-tile-spec
273273
[Polygon layer]: map-add-shape.md
274-
[Render V2-Get Map Tile API]: /rest/api/maps/render-v2/get-map-tile
274+
[Render - Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
275275
[Road tiles]: /rest/api/maps/render-v2/get-map-tile
276276
[SourceManager]: /javascript/api/azure-maps-control/atlas.sourcemanager
277277
[Symbol layer]: map-add-pin.md

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -252,11 +252,11 @@ For more information, see the [Indoor maps wayfinding service] how-to article.
252252

253253
## Using indoor maps
254254

255-
### Render V2-Get Map Tile API
255+
### Render - Get Map Tile API
256256

257-
The Azure Maps [Render V2-Get Map Tile API] has been extended to support Creator tilesets.
257+
The Azure Maps [Render - Get Map Tile] API has been extended to support Creator tilesets.
258258

259-
Applications can use the Render V2-Get Map Tile API to request tilesets. The tilesets can then be integrated into a map control or SDK. For an example of a map control that uses the Render V2 service, see [Indoor Maps Module].
259+
Applications can use the Render - Get Map Tile API to request tilesets. The tilesets can then be integrated into a map control or SDK. For an example of a map control that uses the Render service, see [Indoor Maps Module].
260260

261261
### Web Feature service API
262262

@@ -283,7 +283,7 @@ As you begin to develop solutions for indoor maps, you can discover ways to inte
283283
You can use the Azure Maps Creator List, Update, and Delete API to list, update, and delete your datasets, tilesets, and feature statesets.
284284

285285
>[!NOTE]
286-
>When you review a list of items to determine whether to delete them, consider the impact of that deletion on all dependent API or applications. For example, if you delete a tileset that's being used by an application by means of the [Render V2-Get Map Tile API], the application fails to render that tileset.
286+
>When you review a list of items to determine whether to delete them, consider the impact of that deletion on all dependent API or applications. For example, if you delete a tileset that's being used by an application by means of the [Render - Get Map Tile] API, the application fails to render that tileset.
287287
288288
### Example: Updating a dataset
289289

@@ -306,7 +306,7 @@ The following example shows how to update a dataset, create a new tileset, and d
306306
[Data maintenance]: #data-maintenance
307307
[feature statesets]: #feature-statesets
308308
[Indoor Maps module]: #indoor-maps-module
309-
[Render service]: #render-v2-get-map-tile-api
309+
[Render service]: #render---get-map-tile-api
310310
[tilesets]: #tilesets
311311
[Upload a drawing package]: #upload-a-drawing-package
312312

@@ -320,7 +320,7 @@ The following example shows how to update a dataset, create a new tileset, and d
320320
[Feature State service]: /rest/api/maps/v2/feature-state
321321
[Feature State Update API]: /rest/api/maps/v2/feature-state/update-states
322322
[Geofence service]: /rest/api/maps/spatial/postgeofence
323-
[Render V2-Get Map Tile API]: /rest/api/maps/render-v2/get-map-tile
323+
[Render - Get Map Tile]: /rest/api/maps/render-v2/get-map-tile
324324
[routeset]: /rest/api/maps/2023-03-01-preview/routeset
325325
[Style - Create]: /rest/api/maps/2023-03-01-preview/style/create
326326
[style]: /rest/api/maps/2023-03-01-preview/style

articles/azure-maps/understanding-azure-maps-transactions.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The following table summarizes the Azure Maps services that generate transaction
2222
|--------------------|----------|-------------------------|-------|
2323
| [Data v1]<br>[Data v2]<br>[Data registry] | Yes, except for `MapDataStorageService.GetDataStatus` and `MapDataStorageService.GetUserData`, which are nonbillable| One request = 1 transaction| <ul><li>Location Insights Data (Gen2 pricing)</li></ul>|
2424
| [Geolocation]| Yes| One request = 1 transaction| <ul><li>Location Insights Geolocation (Gen2 pricing)</li><li>Standard S1 Geolocation Transactions (Gen1 S1 pricing)</li><li>Standard Geolocation Transactions (Gen1 S0 pricing)</li></ul>|
25-
| [Render v1]<br>[Render v2] | Yes, except for Terra maps (`MapTile.GetTerraTile` and `layer=terra`) which are nonbillable.|<ul><li>15 tiles = 1 transaction</li><li>One request for Get Copyright = 1 transaction</li><li>One request for Get Map Attribution = 1 transaction</li><li>One request for Get Static Map = 1 transaction</li><li>One request for Get Map Tileset = 1 transaction</li></ul> <br> For Creator related usage, see the [Creator table]. |<ul><li>Maps Base Map Tiles (Gen2 pricing)</li><li>Maps Imagery Tiles (Gen2 pricing)</li><li>Maps Static Map Images (Gen2 pricing)</li><li>Maps Traffic Tiles (Gen2 pricing)</li><li>Maps Weather Tiles (Gen2 pricing)</li><li>Standard Hybrid Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard S1 Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Hybrid Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Rendering Transactions (Gen1 S1 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard S1 Weather Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li><li>Standard Weather Tile Transactions (Gen1 S0 pricing)</li><li>Maps Copyright (Gen2 pricing, Gen1 S0 pricing and Gen1 S1 pricing)</li></ul>|
25+
| [Render] | Yes, except for Terra maps (`MapTile.GetTerraTile` and `layer=terra`) which are nonbillable.|<ul><li>15 tiles = 1 transaction</li><li>One request for Get Copyright = 1 transaction</li><li>One request for Get Map Attribution = 1 transaction</li><li>One request for Get Static Map = 1 transaction</li><li>One request for Get Map Tileset = 1 transaction</li></ul> <br> For Creator related usage, see the [Creator table]. |<ul><li>Maps Base Map Tiles (Gen2 pricing)</li><li>Maps Imagery Tiles (Gen2 pricing)</li><li>Maps Static Map Images (Gen2 pricing)</li><li>Maps Traffic Tiles (Gen2 pricing)</li><li>Maps Weather Tiles (Gen2 pricing)</li><li>Standard Hybrid Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard Aerial Imagery Transactions (Gen1 S0 pricing)</li><li>Standard S1 Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Hybrid Aerial Imagery Transactions (Gen1 S1 pricing)</li><li>Standard S1 Rendering Transactions (Gen1 S1 pricing)</li><li>Standard S1 Tile Transactions (Gen1 S1 pricing)</li><li>Standard S1 Weather Tile Transactions (Gen1 S1 pricing)</li><li>Standard Tile Transactions (Gen1 S0 pricing)</li><li>Standard Weather Tile Transactions (Gen1 S0 pricing)</li><li>Maps Copyright (Gen2 pricing, Gen1 S0 pricing and Gen1 S1 pricing)</li></ul>|
2626
| [Route] | Yes | One request = 1 transaction<br><ul><li>If using the Route Matrix, each cell in the Route Matrix request generates a billable Route transaction.</li><li>If using Batch Directions, each origin/destination coordinate pair in the Batch request call generates a billable Route transaction. Note, the billable Route transaction usage results generated by the batch request has **-Batch** appended to the API name of your Azure portal metrics report.</li></ul> | <ul><li>Location Insights Routing (Gen2 pricing)</li><li>Standard S1 Routing Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
2727
| [Search v1]<br>[Search v2] | Yes | One request = 1 transaction.<br><ul><li>If using Batch Search, each location in the Batch request generates a billable Search transaction. Note, the billable Search transaction usage results generated by the batch request has **-Batch** appended to the API name of your Azure portal metrics report.</li></ul> | <ul><li>Location Insights Search</li><li>Standard S1 Search Transactions (Gen1 S1 pricing)</li><li>Standard Services API Transactions (Gen1 S0 pricing)</li></ul> |
2828
| [Spatial] | Yes, except for `Spatial.GetBoundingBox`, `Spatial.PostBoundingBox` and `Spatial.PostPointInPolygonBatch`, which are nonbillable.| One request = 1 transaction.<br><ul><li>If using Geofence, five requests = 1 transaction</li></ul> | <ul><li>Location Insights Spatial Calculations (Gen2 pricing)</li><li>Standard S1 Spatial Transactions (Gen1 S1 pricing)</li></ul> |
@@ -40,7 +40,7 @@ The following table summarizes the Azure Maps services that generate transaction
4040
| [Conversion] | Part of a provisioned Creator resource and not transactions based.| Not transaction-based | Map Provisioning (Gen2 pricing) |
4141
| [Dataset] | Part of a provisioned Creator resource and not transactions based.| Not transaction-based | Map Provisioning (Gen2 pricing)|
4242
| [Feature State] | Yes, except for `FeatureState.CreateStateset`, `FeatureState.DeleteStateset`, `FeatureState.GetStateset`, `FeatureState.ListStatesets`, `FeatureState.UpdateStatesets` | One request = 1 transaction | Azure Maps Creator Feature State (Gen2 pricing) |
43-
| [Render v2] | Yes, only with `GetMapTile` with Creator Tileset ID and `GetStaticTile`.<br>For everything else for Render v2, see Render v2 section in the above table.| One request = 1 transaction<br>One tile = 1 transaction | Azure Maps Creator Map Render (Gen2 pricing) |
43+
| [Render] | Yes, only with `GetMapTile` with Creator Tileset ID and `GetStaticTile`.<br>For everything else for Render, see Render section in the above table.| One request = 1 transaction<br>One tile = 1 transaction | Azure Maps Creator Map Render (Gen2 pricing) |
4444
| [Tileset] | Part of a provisioned Creator resource and not transactions based.| Not transaction-based | Map Provisioning    (Gen2 pricing) |
4545
| [WFS] | Yes| One request = 1 transaction | Azure Maps Creator Web Feature (WFS) (Gen2 pricing) |
4646

@@ -81,8 +81,7 @@ The following table summarizes the Azure Maps services that generate transaction
8181
[Geolocation]: /rest/api/maps/geolocation
8282
[Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
8383
[Pricing calculator]: https://azure.microsoft.com/pricing/calculator/
84-
[Render v1]: /rest/api/maps/render
85-
[Render v2]: /rest/api/maps/render-v2
84+
[Render]: /rest/api/maps/render-v2
8685
[Route]: /rest/api/maps/route
8786
[Search v1]: /rest/api/maps/search
8887
[Search v2]: /rest/api/maps/search-v2

0 commit comments

Comments
 (0)