GetTile
The GetTile operation allows clients to request:
- a particular Tile
- of a particular layer
- of a particular tileMatrixSet
- in a particular format
The GetTile URL
The client can request a GetTile operation from the WMTS server in order to get the actual imagery Tile of a particular tileMatrixSet in a predefined format. This operation has some parameters in common with WMS GetMap but it has been deliberately simplified.
| https://evwhs.digitalglobe.com/earthservice/wmtsaccess?SERVICE=WMTS&VERSION=1.0.0&STYLE=&REQUEST=GetTile&CONNECTID=**<CONNECTID>**&LAYER=DigitalGlobe:ImageryTileService&FORMAT=image/jpeg&TileRow=18200&TileCol=27207&TileMatrixSet=EPSG:4326&TileMatrix=EPSG:4326:16&featureProfile=Consumer_Profile Note: Replace <CONNECTID> with the connectId provided by Maxar. Parameters are not required to be in the same order as shown above. |
GetTile Request Parameters
The parameters required for the GetTile request are shown below. The client provides the following information in a Key-Value Pair (KVP) format, where the "name" field is the key, and the "value" field is the value; the data is supplied in the format "key=value"; for example, "service=WMTS".
Name | Value | Short Description |
---|---|---|
WMTS | Web Map Tile Service | |
1.0.0 | Request version | |
GetTile | Request name | |
One or more of the available layers, such as digitalglobe:ImageryTileService | The layers available from the Online Catalogs; if more than one layer is requested they are in a comma-separated list. Available layers are listed in the GetCapabilities response. See below for a description of available layers. | |
String; supported values are: EPSG:4326 EPSG:3857 EPSG:3395 | The tileMatrixSet to be used to generate the response. A complete list of supported values are found in the GetCapabilities response. | |
String; supported values are: EPSG:4326:0 through EPSG:4326:20 EPSG:3857:0 through EPSG:3857:20 | The tileMatrix identifier of the tileMatrix in the tileMatrixSet requested that has the desired scale denominator that you want to request. 4326 is WGS84, that is, uses latitude/longitude, while 3857 provides Tiles in the spherical Mercator projection. | |
Integer | The Row location of the Tile in the defined tileMatrixSet. The value must be in the valid range provided in the capabilities response. | |
Integer | The Column location of the tile in the defined tileMatrixSet. The value must be in the valid range provided in the capabilities response. | |
Mime type of the tile to be returned, for example: image/png image/jpeg image/vnd.jpeg-png application/vnd.quantized-mesh | The tile format to return. See below for a description of available formats. | |
Character string | Value for this parameter is a unique 32-digit alphanumeric value given by Maxar (see Connect ID). A valid Connect ID is mandatory for every request. | |
The current profiles include: Accuracy_Profile Aerial_CIR_Profile Cloud_Cover_Profile Consumer_Profile Currency_Profile Currency_RGB_Profile Default_Profile True_Currency_Profile | These profiles describe the imagery stacking rules for an account. The user can choose a profile in a request by specifying the featureProfile request parameter. The available profiles are listed in the GetCapabilities response. | |
application/vnd.ogc.se_xml | Format in which exceptions will be reported; the default is XML unless otherwise specified. | |
Character string | Vendor parameter: Filter expressed in ECQL (Extended Common Query Language) to be applied on returned imagery Features involved in the getTile request. The filtering will not be applied to base_mosaic. | |
Comma separated values of band names | Allows band selection. This may be used as an instance when accessing a SWIR 8-band product type, to render a reduced subset of them (i.e., bands="R,G,B") | |
The layer style | Some layers can be rendered in different ways; check the capabilities document for allowed values on a layer-by-layer basis. |
The Format Parameter
The FORMAT parameter specifies the desired tile format of the response to a request operation. Not all layers are available in the same formats, check the capabilities document for allowed formats in different layers.
|
|
Format MIME Type | Description and Notes |
---|---|
image/jpeg | Format to serve opaque tile images using lossy compression. EXIF Tag (USER_COMMENT) can be embedded in the file to include the tile Feature composition in either CSV or XML format (also known as "dog tag"). |
image/png | Format supporting transparency and lossless compression. |
image/vnd.jpeg-png | Format that supports transparency by encoding png if the map actually contains non opaque pixels (or if the image is paletted) and using jpeg instead if the image is fully opaque. |
application/vnd.quantized-mesh | Format used to serve terrain Tiles in quantized mesh format, typically used in Cesium based front-ends. |
The Layer Parameter
This is a list of layers available in the capabilities document. Your account privileges determine which layers you may access.
OGC Layers | Description |
---|---|
ImageryTileService | Tiled imagery for all data layers available to the account, with the default display for a location determined by stacking profile. |
CitySphereTileService | Tiled imagery from the Global Basemap City Program. Stacking profiles do not apply. |
CountryCoverageTileService | Tiled imagery from the Global Basemap Country Program. Stacking profiles do not apply. |
CrisisEventTileService | Contains only strips from the "crisis_event" data layer. |
FirstLookTileService | Contains only strips from the "crisis_event" data layer (same as CrisisEventTileService). |
TerrainTileService | Terrain maps based on DEM raster sources. There are four styles available for this layer, showing the terrain as colored map (terrain), contours (contours), shaded relief (relief) and combination of shaded relief and colored map (terrainRelief). |
Terrain3DTileService | Terrain data served as TIN data in quantized mesh format. |
The CQL_Filter Parameter
Catalog Query Language is a simple filter language loosely based on SQL. It is thus possible to perform simple comparisons ('=', '<', '<=', '>=','>','<>'), logic composition ('AND', 'NOT', 'OR') and string matching ("LIKE '%foo%').
The filter can use the attribute names as the finishedFeature WFS Feature type (e.g., Feature ID, dataLayer, source,...). Check a WFS GetFeature or DescribeFeatureType output for a full list of parameters, like the following:
| http://evwhs.digitalglobe.com/wfsservice/wfsaccess?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=FinishedFeature&connectId=<CONNECTID> Note: Replace <CONNECTID> with the connectId provided by Maxar. Parameters are not required to be in the same order as shown above. |
The Bands Parameter
The bands parameter allows the client to perform on-the-fly false color image generation by picking 3 bands as R, G, and B from 8-band features. In order for this parameter to make sense a CQL_FILTER should be added that selects only the desired type imagery, for example, by selecting a specific feature by Feature ID using "CQL_FILTER=feature_id%3D%27<FeatureID>%27", and ensure that the feature you select has the appropriate product type (e.g., MS1_MS2, SWIR 8-band).
Examples of usage of the bands parameter are "bands=C,Y,RE" or "bands=S1,S4,S7".
For 8-band products, the band IDs and descriptions are:
R | Red |
G | Green |
B | Blue |
C | Coastal |
Y | Yellow |
RE | Red Edge |
N | NIR (Near Infrared) |
N2 | NIR2 (Near Infrared 2) |
For SWIR products, the bands IDs are S1, S2, S3, S4, S5, S6, S7.
GetTile Response
The response to a GetTile Request is a Map Tile in the requested format and projection. All image based WMTS Tiles are 256x256 pixels; no other Tile sizes are currently supported. Some specific formats might not have a corresponding Tile size notion (e.g., quantized mesh Tiles).
Exceptions
In the event that a WMTS encounters an error while processing a request or receives an unrecognized request, it will generate an XML document indicating that an error has occurred. An <ExceptionReport> element will contain one or more processing exceptions specified using the <Exception> element. Individual <Exception> elements contain exceptionCode, which specifies the actual exception that occurred.
The following example of an exception report indicates that a parameter value is missing and a parameter value is invalid in the request URL.
<?xml version="1.0" encoding="UTF-8"?>
<ExceptionReport
xmlns="http://www.opengis.net/ows/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/ows/1.1 owsExceptionReport.xsd" version="1.0.0" xml:lang="en">
<Exception exceptionCode="MissingParameterValue" locator="service"/>
<Exception exceptionCode="InvalidParameterValue" locator="version"/>
</ExceptionReport>