Tileset - Get
Use to get the details of a tileset.
Submit Get Request
The Get
API is an HTTP GET
request used to fetch the details of a tileset.
GET https://{geography}.atlas.microsoft.com/tilesets/{tilesetId}?api-version=2023-03-01-preview
URI Parameters
Name | In | Required | Type | Description |
---|---|---|---|---|
geography
|
path | True |
string |
This parameter specifies where the Azure Maps Creator resource is located. Valid values are us and eu. |
tileset
|
path | True |
string |
The Tileset Id |
api-version
|
query | True |
string |
Version number of Azure Maps API. |
Request Header
Name | Required | Type | Description |
---|---|---|---|
x-ms-client-id |
string |
Specifies which account is intended for usage in conjunction with the Microsoft Entra ID security model. It represents a unique ID for the Azure Maps account and can be retrieved from the Azure Maps management plane Account API. To use Microsoft Entra ID security in Azure Maps see the following articles for guidance. |
Responses
Name | Type | Description |
---|---|---|
200 OK |
List tileset request completed successfully. The response body contains a list of all tilesets. |
|
Other Status Codes |
An unexpected error occurred. |
Security
AADToken
These are the Azure Active Directory OAuth2 Flows. When paired with Azure role-based access control it can be used to control access to Azure Maps REST APIs. Azure role-based access controls are used to designate access to one or more Azure Maps resource account or sub-resources. Any user, group, or service principal can be granted access via a built-in role or a custom role composed of one or more permissions to Azure Maps REST APIs.
To implement scenarios, we recommend viewing authentication concepts. In summary, this security definition provides a solution for modeling application(s) via objects capable of access control on specific APIs and scopes.
Notes
- This security definition requires the use of the
x-ms-client-id
header to indicate which Azure Maps resource the application is requesting access to. This can be acquired from the Maps management API.
The Authorization URL
is specific to the Azure public cloud instance. Sovereign clouds have unique Authorization URLs and Azure Active directory configurations.
*
The Azure role-based access control is configured from the Azure management plane via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.
*
Usage of the Azure Maps Web SDK allows for configuration based setup of an application for multiple use cases.
- Currently, Azure Active Directory v1.0 or v2.0 supports Work, School, and Guests but does not support Personal accounts.
Type:
oauth2
Flow:
implicit
Authorization URL:
https://login.microsoftonline.com/common/oauth2/authorize
Scopes
Name | Description |
---|---|
https://atlas.microsoft.com/.default | https://atlas.microsoft.com/.default |
subscription-key
This is a shared key that is provisioned when you Create an Azure Maps account in the Azure portal or using PowerShell, CLI, Azure SDKs, or REST API.
With this key, any application can access all REST API. In other words, this key can be used as a master key in the account that they are issued in.
For publicly exposed applications, our recommendation is to use the confidential client applications approach to access Azure Maps REST APIs so your key can be securely stored.
Type:
apiKey
In:
query
SAS Token
This is a shared access signature token is created from the List SAS operation on the Azure Maps resource through the Azure management plane via Azure portal, PowerShell, CLI, Azure SDKs, or REST APIs.
With this token, any application is authorized to access with Azure role-based access controls and fine-grain control to the expiration, rate, and region(s) of use for the particular token. In other words, the SAS Token can be used to allow applications to control access in a more secured way than the shared key.
For publicly exposed applications, our recommendation is to configure a specific list of allowed origins on the Map account resource to limit rendering abuse and regularly renew the SAS Token.
Type:
apiKey
In:
header
Examples
Gets the details for a single tileset
Sample Request
GET https://us.atlas.microsoft.com/tilesets/{tilesetId}?api-version=2023-03-01-preview
Sample Response
{
"tilesetId": "{tilesetId}",
"datasetId": "{datasetId}",
"description": "My first tileset",
"minZoom": 16,
"maxZoom": 18,
"bbox": [
-122.13595,
47.636524,
-122.1329,
47.637525
]
}
Definitions
Name | Description |
---|---|
Error |
The resource management error additional info. |
Error |
The error detail. |
Error |
Error response |
Feature |
Feature configuration for tileset configuration. |
Layer |
Layer object for tileset configuration. |
Tileset |
Detail information for the data. |
Tileset |
Tileset configuration top-level fields. A tileset configuration is a JSON object that must contain the following top-level fields: |
ErrorAdditionalInfo
The resource management error additional info.
Name | Type | Description |
---|---|---|
info |
object |
The additional info. |
type |
string |
The additional info type. |
ErrorDetail
The error detail.
Name | Type | Description |
---|---|---|
additionalInfo |
The error additional info. |
|
code |
string |
The error code. |
details |
The error details. |
|
message |
string |
The error message. |
target |
string |
The error target. |
ErrorResponse
Error response
Name | Type | Description |
---|---|---|
error |
The error object. |
Feature
Feature configuration for tileset configuration.
Name | Type | Description |
---|---|---|
featureClasses |
string[] |
The list of feature classes that will be used to build the layer. The valid feature classes can be found in its ontology definition. For example, Facility Ontology |
filter |
object |
Removes features that do not match a pattern. Refer to MapLibre filter expression |
LayerObject
Layer object for tileset configuration.
Name | Type | Description |
---|---|---|
features |
Specifies the feature classes and filters. |
|
maxZoom |
integer |
The highest zoom level for the layer to build. |
minZoom |
integer |
The lowest zoom level for the layer to build. |
Tileset
Detail information for the data.
Name | Type | Description |
---|---|---|
bbox |
number[] |
Bounding box which all features of the tileset lay within. Projection used - EPSG:3857. Format : 'minLon, minLat, maxLon, maxLat'. |
datasetId |
string |
The unique dataset Id used to create the tileset. |
defaultMapConfigurationId |
string |
The default generated map configuration id for the tileset |
description |
string |
The description the caller provided when creating the tileset. Maximum length 1024 characters. |
maxZoom |
integer |
The highest tile zoom level tile generated for the tileset. |
minZoom |
integer |
The lowest tile zoom level tile generated for the tileset. |
ontology |
string |
The ontology version of this dataset. |
tilesetConfiguration |
Tileset configuration which is used to build the tileset. |
|
tilesetId |
string |
The unique tileset id for the tileset. |
TilesetConfiguration
Tileset configuration top-level fields. A tileset configuration is a JSON object that must contain the following top-level fields:
Name | Type | Description |
---|---|---|
layers |
<string,
Layer |
The names of the layers and their configuration options. The configuration layers object contains key-value pairs associating the names of tile layers with their configuration. For each key-value pair, the key is the name of the layer, and the value is a LayerObject containing the configuration and options for the layer. Each layer must have a name. This is the unique identifier for the layer of data in your final tileset. In any tileset, each layer name must be unique. The layer name must be a string with only underscores (_) and alphanumeric characters. The corresponding LayerObject for each layer name describes how that vector tile layer should be created. It specifies which feature classes to retrieve feature data, the precision of the data through zoom levels, and how to transform features and render them into tiles. |
version |
integer |
The version of Azure Maps Tiling service configuration reference that the tileset configuration uses. Currently only version 1 is allowed. Using any version other the current version or a previous version will result in an error. |