Language
OneAtlas Data Guide
  1. View Service
    1. Preview Images
    2. Full Resolution Images
    3. WMS, WMTS and WCS
      1. Streaming on the Fly
      2. Streaming from Your Workspace
        1. Panchromatic and Multispectral
    4. Access Imagery from GIS Tools
      1. QGIS
      2. ArcGIS Desktop
        1. ArcGIS Desktop - OneAtlas Data AddIn
      3. ArcGIS Enterprise
    5. Access Imagery from your Own Code
      1. Using WMS protocol
      2. Using WMTS protocol

View Service

The OneAtlas Data View service allow users to easily access to images without having to download and maintain DIMAP products. This guide will walk you though using WMS and WMTS to stream on the fly.

Prerequisites: If you haven’t already, see our Authentication Guide for information on how to acquire an API key and generate tokens to access to our endpoints. If you would like to try the examples in this guide, ensure that GDAL Geospatial Data Abstraction Library is installed.

Preview Images

A preview is simple way to get a rapid insight of the imagery. The preview images include three bands (Blue, Red and Green), the pixel depth is 8 bits. A preview is neither orthorectified nor geolocalized. There are two kinds available:

KindDescription
ThumbnailsThe thumbnail is a very reduced size version of the image.
Its size depends of each image but is approximately 150 × 300 pixels.
QuicklookThe quicklook is a reduced size version of the image.
Its size depends of each image but is approximately 2500 × 5000 pixels.

The endpoints follow always the same pattern:

Preview typeEndpoint
thumbnailhttps://view.oneatlas.geoapi-airbusds.com/thumbnail/<image_id>
quicklookhttps://view.oneatlas.geoapi-airbusds.com/quicklook/<image_id>

To access a thumbnail or a quicklook you first need to perform a search in our Living Library to grab the corresponding id. You can see an example of a quicklook within our Search Guide. Alternatively we can grab the quicklook url by inputting the sourceIdentifier into this cURL command:

curl -k -L --silent -X GET "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch?sourceIdentifier=DS_PHR1B_201805071126173_FR1_PX_W004N43_0309_01462" |python -m json.tool | grep "/quicklook" \
    -H "Cache-Control: no-cache" \
    -H "Authorization: Bearer <access_token>"
Not available.
Not available.

Here you can see the quicklook url returned:

"href": "https://view.oneatlas.geoapi-airbusds.com/items/<image_id>/quicklook",

To download the quicklook image you can use an additional request. You can also specify the width of the quicklook by using parameters at the end of the url (e.g. ?width=xxx).

curl --silent -X GET  "https://view.oneatlas.geoapi-airbusds.com/items/<image_id>/quicklook" > quicklook.jpg \
  -H "Authorization: Bearer <access_token>"
Not available.
Not available.

Now we can retrieve detailed information such as the size of the image using the gdalinfo utilitary:

> gdalinfo quicklook.jpg
Driver: JPEG/JPEG JFIF
Files: quicklook.jpg
Size is 909, 735
Coordinate System is `'
Image Structure Metadata:
  COMPRESSION=JPEG
  INTERLEAVE=PIXEL
  SOURCE_COLOR_SPACE=YCbCr
Corner Coordinates:
Upper Left  (    0.0,    0.0)
Lower Left  (    0.0,  735.0)
Upper Right (  909.0,    0.0)
Lower Right (  909.0,  735.0)
Center      (  454.5,  367.5)
Band 1 Block=909x1 Type=Byte, ColorInterp=Red
  Overviews: 455x368, 228x184
  Image Structure Metadata:
    COMPRESSION=JPEG
Band 2 Block=909x1 Type=Byte, ColorInterp=Green
  Overviews: 455x368, 228x184
  Image Structure Metadata:
    COMPRESSION=JPEG
Band 3 Block=909x1 Type=Byte, ColorInterp=Blue
  Overviews: 455x368, 228x184
  Image Structure Metadata:
    COMPRESSION=JPEG

Full Resolution Images

The OGC (Open Geospatial Consortium) is an international not for profit organization committed to making quality open standards for the global geospatial community. These standards are made through a consensus process and are freely available for anyone to use to improve sharing of the world’s geospatial data.


In the frame of the OneAtlas Data service, the WMTS, WMS and WCS protocols are provided to ease the use and the display of imagery in desktop GIS applications (QGIS, ArcMap) or any web mapping platforms that provide WMTS, WMS or WCS support.


The protocols provide the access to OneAtlas data images referenced in the public catalog, as well as your processed products in your private workspace up to their full resolution.


There are three kinds of images available:

Multispectral- Multispectral images include three multispectral (color) bands (Blue, Red and Green), the pixel depth is 8 bits.
- The product pixel size is 6m for SPOT images and 2m for Pleiades images.
- Images with optimized true color rendering (Display) - adjusted luminosity and contrast and preserved color balance.
- The images are orthorectified with a geolocation accuracy of 10m CE 90.
  
Panchromatic- Panchromatic images include includes only one black and white band.
- The pixel depth is 8 bits.
- The product pixel size is 1.5m for SPOT images and 0.5m for Pleiades images.
- The images are orthorectified with a geolocation accuracy of 10m CE 90.
  
Pan-sharpened - Available on the fly- Pan-sharpened products combine the visual information of the multispectral data with the spatial information of the panchromatic data, resulting in a higher resolution 0.5-m color product.
- The pixel depth is 8 bits.
- The product pixel size is 1.5m for SPOT images and 0.5m for Pleiades images.
- Images with optimized true color rendering (Display)- adjusted luminosity and contrast and preserved color balance.
- The images are orthorectified with a geolocation accuracy of 10m CE 90.

WMS, WMTS and WCS

WMS

The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not.


WMTS

The Web Map Tile Service (WMTS) service conforms to the WMTS Simple profile norm.  According the reference, this service provides a pyramid of tiles in two different projections: WebMercator (EPSG:3857) and Geographic (EPSG:4326), these will be discussed in further detail.


WCS

The OpenGIS® Web Coverage Service (WCS) provides an open specification for sharing raster datasets on the web. A WCS service returns data in a format that can be used as input for analysis and modeling. This is in contrast with the OGC Web Map Service (WMS), which only returns a picture of the data.

Streaming On the Fly

Note: This requires a streaming plan. See our Manage contract guide if you do not yet have a subscription.

If you have sufficient tiles, OneAtlas Data will allow you to stream pansharpened imagery on the fly just by searching through our Living Library. The simple example below using the /opensearch endpoint retrieves everything within the Living Library:

curl -X GET \
  'https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch' \
  -H 'Authorization: Bearer <access_token>' \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \
var data = null;

var xhr = new XMLHttpRequest();
xhr.withCredentials = true;

xhr.addEventListener("readystatechange", function () {
  if (this.readyState === 4) {
    console.log(this.responseText);
  }
});

xhr.open("GET", "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch");
xhr.setRequestHeader("Authorization", "Bearer <access_token>");
xhr.setRequestHeader("Content-Type", "application/json");

xhr.send(data);
import requests

url = "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch"

headers = {
    'Authorization': "Bearer <access_token>",
    'Content-Type': "application/json"
    }

response = requests.request("GET", url, headers=headers)

print(response.text)

To learn how to search by AOI, resolution, id and more, refer to our Search guide. Once you have ordered your product, you will retrieve your WMTS, WMS and WCS urls:

"wmts": {
    "href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts",
    "name": "WMTS",
    "type": "WMTS"
},
"wms": {
    "href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wms",
    "name": "WMS",
    "type": "WMS"
}
"wcs": {
    "href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wcs",
    "name": "WCS",
    "type": "WCS"
}

We will look at how you can use these urls in more detail further in the guide.

Streaming from Your Workspace

Your workspace provides your contract with an area of all purchased imagery. All users on the same contract will have access to the same workspace. These images will be in type bundle which will allow you to stream either Panchromatic or Multispectral images. If you wish to stream imagery already within your workspace, you can filter using your workspaceId:

curl -X GET \
  'https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch?workspaceId=<workspace_id>' \
  -H 'Authorization: Bearer <access_token>' \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \

var data = null;

var xhr = new XMLHttpRequest();
xhr.withCredentials = true;

xhr.addEventListener("readystatechange", function () {
  if (this.readyState === 4) {
    console.log(this.responseText);
  }
});

xhr.open("GET", "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch?workspaceId=<workspace_id>");
xhr.setRequestHeader("Authorization", "Bearer <access_token>");
xhr.setRequestHeader("Content-Type", "application/json");

xhr.send(data);
import requests

url = "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch"

querystring = {"workspaceId":"<workspace_id>"}

headers = {
    'Authorization': "Bearer <access_token>",
    'Content-Type': "application/json"
    }

response = requests.request("GET", url, headers=headers, params=querystring)

print(response.text)

Alternatively, you can do this in one cURL command bif you know the sourceIdentifier:

curl --silent -k -L -X GET "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch?sourceIdentifier=DS_PHR1B_201805071126173_FR1_PX_W004N43_0309_01462" \
   -H "Authorization: Bearer <access_token>" \
   -H "Cache-Control: no-cache" \
   | python -m json.tool | egrep "href"
Not available.
Not available.

This will return all urls related to the sourceIdentifier that you have provided:

"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/metadata",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/delete",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/quicklook",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/thumbnail",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wms",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wcs"

Panchromatic and Multispectral

By using the WMTS url above, this will stream Panchromatic imagery by default. If you wish to stream Multispectral you can use the Metadata urls returned in your workspace:

"imagesMetadata": [
    {
        "href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/9c41e689-3069-409a-ace7-af8cc512223e/images/1e2cf2fa-449a-43fe-ae2e-60df4bbbe5f7/metadata",
        "name": "panchromatic",
        "type": "application/geo+json"
    },
    {
        "href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/9c41e689-3069-409a-ace7-af8cc512223e/images/6950d957-58af-442d-ab3f-d684b917f423/metadata",
        "name": "multispectral",
        "type": "application/geo+json"
    }
  ]

You will need to amend your url to fit the Multispectral metadata url as follows:

# Example of WMS request for multispectral
https://view.oneatlas.geoapi-airbusds.com/api/v1/items/9c41e689-3069-409a-ace7-af8cc512223e/images/6950d957-58af-442d-ab3f-d684b917f423/wms

# Example of WMTS request for multispectral
https://view.oneatlas.geoapi-airbusds.com/api/v1/items/9c41e689-3069-409a-ace7-af8cc512223e/images/6950d957-58af-442d-ab3f-d684b917f423/wmts

# Example of WCS request for multispectral
https://view.oneatlas.geoapi-airbusds.com/api/v1/items/9c41e689-3069-409a-ace7-af8cc512223e/images/6950d957-58af-442d-ab3f-d684b917f423/wcs

Access Imagery from GIS Tools

The OneAtlas Data streaming services follows rigorously the OGC norm for its WMTS, WMS and WCS implementation. Consequently, the integration of our urls in these GIS tools is straight forward.

QGIS

You can easily access to the OneAtlas data imagery with OSGeo's QGIS Desktop application. QGIS in an Open Source Geographic Information System (GIS) licensed under the GNU General Public License. QGIS currently can act as a WMS, WMTS and WCS client.


The procedure to follow is documented directly on the QGIS website.


You will need to provide your WMS/WMTS/WCS url. To ensure a secure experience, the user and password are mandatory to access to OneAtlas Data images. The credentials to used are listed in the table below:

UsernameAPIKEY
Passwordinsert_your_api_key

The resulting dialog box filled out should looks like:

qgis_login.png

And the result in QGIS is:

qgis_result.png

Note: if no tiles are returned, please ensure checkboxes : “Invert axis orientation (WMS 1.3/WMTS)” and “Invert axis orientation” are selected.

ArcGIS Desktop

You can easily access to the OneAtlas Data imagery with ESRI ArcGIS Desktop, a commercial product used by GIS professionals to compile, use, and manage geographic information. The procedure to follow is documented directly on the ESRI website.


You will need to provide:

  • The WMTS, WMS or WCS endpoint , e.g. https://view.oneatlas.geoapi-airbusds.com/api/v1/items/image_id/wmts
  • Credentials to be authorized to display the image
UsernameAPIKEY
Passwordinsert_your_api_key

The resulting dialog box filled out looks should look like:

arcgis_wmts_config.png

The result in ArcGIS Desktop will look like:

arcgis_desktop.png

ArcGIS Desktop OneAtlas Data AddIn

You can display a set of search and selected images by using the ArcGIS Desktop.

Prerequisites

ArcGIS for Desktop 10.5 or higher.

Installation

Double click on OneAtlas Data AddIn file. 1.png Launch ArcMap and activate toolbar by clicking on “Customize > Toolbars > OneAtlas Data Plugin”.

2.png 3.png

Overview of the AddIn


Search for OneAtlas Data Images 4.png Draw a rectangular Area Of Interest 5.png Draw a polygon Area Of Interest 6.png Erase current Area Of Interest 7.png Change connection settings 8.png

Searching and displaying images


Draw an Area Of Interest by using the rectangular tool

9.gif Open search window, define search criterias and launch the search by clicking on “Search By AOI”

10.png Put your OneAtlas Data API Key, and press validation button 11.png Click on “Search with limitations” buttons, the bounding box of all the images found in catalog is displayed.

12.gif Select images to view the metadata. 13.gif Click on “Add Selected Images as Layers” button to display the image in full resolution using WMTS endpoint. 14.gif 15.gif

ArcMap layers available


“AOI & Search Criteria” layer, store Area Of Interest bounding box and the criterias used for your search 16.gif “Search Results” layer, store bounding box and metadata of the images found 17.gif

Searching by ID

Put the IDs of the images, and click on button “Search By IDs” 18.gif Select images to view the metadata. 19.gif Click on “Add Selected Images as Layers” button to display the image in full resolution using WMTS endpoint. 20.gif

ArcGIS Enterprise

Go to your ArcGIS Enterprise instance and authenticate.
Click on the “Map” menu then on “Modify Map” on the upper right corner of the map, next to the “Sign In” button.
Select “Add Layer from the Web” and “A WMTS OGC Web Service” from the drop down list as type of data to reference. You will need to provide:
- The WMTS endpoint of the Living Library Image (see Search results)
- Credentials (an APIKEY) to be authorized to display the Living Library Image (see Authenticate Guide)

ArcGIS_enterprise.png The layer name will be displayed in the ArcGIS Enterprise “Table Of Content” on the left hand side of the map. Meanwhile, the layer will display on the map.

Access Imagery from Your Own Code

As an example, we will use the following area of San Francisco International Airport:

arcgis_map.png

The coordinates of the bounding box to extract are:

LongitudeLatitude
Upper left corner-122,38594651222237,6203332456312
Bottom right corner-122,38220214843737,6176733171484

The first step is to select the image from which we want to extract a subpart:

curl --silent -k -L -X GET   "https://search.oneatlas.geoapi-airbusds.com/api/v1/opensearch?itemsPerPage=1&startPage=1&relation=intersects&geometry=POLYGON((-122.38594651222229%2037.61767331714846%2C-122.3822021484375%2037.61767331714846%2C-122.3822021484375%2037.62033324563128%2C-122.38594651222229%2037.62033324563128%2C-122.38594651222229%2037.61767331714846))" \
  -H "Authorization: Bearer <access_token>" \
  -H "Cache-Control: no-cache" |python -m json.tool |egrep "href"
Not available.
Not available.

This example searches for an image with the specified polygon coordinates and extracts all urls relating to this image (including WMS, WMTS and WCS):

"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/metadata",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/quicklook",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/thumbnail",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wms",
"href": "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts",

Using WMS Protocol

You can use the WMS protocol to access to a subpart of an image. In this example we show a number of parameters needed to make a successful GetMap request:

curl -X GET \
  'https://access.foundation.api.oneatlas.airbus.com/api/v1/items/<item_id>/images/<Images_Id>/wms?REQUEST=GetMap&VERSION=1.3.0&LAYERS=layer_0&CRS=EPSG:4326&BBOX=<BBOXCoordinates>&WIDTH=600&HEIGHT=400&FORMAT=image/png'\
  -H 'Authorization: Bearer <access_token>' \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \
Not available
Not available
https://view.oneatlas.geoapi-airbusds.com/api/v1/items/image_id/wmsThis is the URL corresponding to the image and to the product type from which the request has to be done.
VERSION=1.3.0This is the most recent WMS request version.
REQUEST=GetMapThis is the request name.
CRSThis is the spatial reference value. The value could be EPSG:4326 or EPSG:3857
BBOXThis is the ounding box for map extent. The value is 'minX, minY, maxX, maxY' in units of the SRS.
WIDTH / HEIGHTThis is the width or height of the requested image in pixels.
FORMAT=image/pngThis is the requested image format.

Here we can see the PNG result of the request above for the requested pixel size (600 × 400) satisfying our bounding box:

arcgis_pic.png

Using WMTS Protocol

This section details how to use the WMTS protocol from your own code. It’s a bit more complex that using the WMS protocol, but your efforts will be rewarded with better performance. To do so, you will need to convert the from geographic coordinates into tiles coordinates.

GetCapabilities

To retrieve the endpoint to access to a single tile, you should use the GetCapabilities file corresponding to the image from which you want to extract tiles.


The characteristics of the endpoint to access to the GetCapabilities are:

API Endpoint<wmts_url>?request=GetCapabilities
REST verbGET
AuthenticationBearer access token
API ReferenceView API

Here is an example of a GetCapabilities request:

curl -X GET "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts?request=GetCapabilities"
  -H "Authorization: Bearer <access_token>"
  -H "Cache-Control: no-cache"
Not available.
Not available.

This will return an XML file with tiles. Below you can see an extract the XML file:

<TileMatrix>
  <ows:Identifier>12</ows:Identifier>
  <ScaleDenominator>68247.34668319309</ScaleDenominator>
  <TopLeftCorner>90.000000 -180.000000</TopLeftCorner>
  <TileWidth>256</TileWidth>
  <TileHeight>256</TileHeight>
  <MatrixWidth>8192</MatrixWidth>
  <MatrixHeight>4096</MatrixHeight>
</TileMatrix>

Get Tiles for a Geographic Tile Matrix Set

If you intend to get the tiles coordinates for the Geographic tile matrix set, you should use the formula below:

  • x = [ (longitude + π) / (2 × π) ] × MatrixWidth
  • y = [1 - [ (latitude + π/2 ) / π ] ] × MatrixHeight

Note: latitude and longitude should be in radians.

The Geographic tile matrix set is described as follows:

  • CRS Name: urn:ogc:def:crs:OGC:1.3:CRS84 CRS84
  • Top left corner: [ -180 , 90 ]
  • Tile size: 256 × 256 pixels
Zoom level idScale DenominatorPixel Size (degrees)Pixel Size (m)*Matrix WidthMatrix Height
-1559082264.02871781.4062511
0279541132.01435890.70312570312.521
1139770566.00717940.35156250035156.2542
269885283.003589720.17578125017578.12584
334942641.501794868.78906250 × 10-28789.063168
417471320.750897434.39453125 × 10-24394.5313216
58735660.3754487152.19726562500 × 10-22197.2666432
64367830.1877243571.09863281250 × 10-21098.63312864
72183915.0938621795.49316406250 × 10-3549.316256128
81091957.5469310892.74658203125 × 10-3274.658512256
9545978.77346554471.37329101562500 × 10-3137.3291024512
10272989.38673277236.86645507812500 × 10-468.66520481024
11136494.69336638623.43322753906250 × 10-434.33240962048
1268247.346683193091.71661376953125 × 10-417.16681924096
1334123.673341596548.58306884765625 × 10-58.5831163848192
1417061.836670798274.29153442382812 × 10-54.29153276816384
158530.9183353991362.14576721191406 × 10-52.14586553632768
164265.4591676995681.07288360595703 × 10-51.072913107265536
172132.7295838497845.36441802978516 × 10-60.53644262144131072

* Approximation at the equator


The matrix width and height depends on the zoom level. You can pick the correct value using the table provided above. Be aware that the size of the tile matrix differs between the Geographic and the Web Mercator tile matrix set.


The request returns an XML response which is conformed to the OGC specification. By aggregating different elements such as the style, the tile matrix set with the ResourceURL value and integrating the tiles coordinates, you can access a single tile.


The below example contains the following elements which make up the url to retrieve a tile:

  • EPSG - in this example it is “EPSG4326”
  • Zoom level - in this example this is “17”
  • Upper left tile - in this example it is “41955”
  • Bottom right tile - in this example it is “38143”
curl -X GET "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts/tiles/1.0.0/default/rgb/EPSG4326/17/41955/38143.png"
  -H "Authorization: Bearer <access_token>" \
  -H "Cache-Control: no-cache"
Not available.
Not available.

Here you can see the result displaying one tile:

tile_4326_17_41955_38143.png

For this example the result is made up of 9 tiles. The overall size of the composite image is 728 (3 × 256) pixels per 728 pixels (3 × 256 pixels) and the returned BBOX exceeded the initial BBOX requested.

tiles_crop.png

Geographic Converter (EPSG:4326)

Note: The converter uses input type degrees

To retrieve a url for a single tile, you can use our simple Geographic converter below. You will require the following:

  • The longitude and latitude for the top left and bottom right corner. These can be found within your AOI coordinates.
  • The zoom level you would like to access. These are shown within the GetCapabilities XML result.
  • The id of the image. You should have used this previously for the GetCapabilities result.




Your Geographic url results:

* Required fields


Get Tiles for a Web Mercator Tile Matrix Set

If you intend to get the tiles coordinates for the Web Mercator tile matrix set, you will have to first reproject the coordinates to the Mercator projection (from EPSG:4326 to EPSG:3857). Then you will be required to transform the range of latitude and longitude to 0 - 1 and shift origin to top left corner:

  • n = 2 ^zoom
  • xtile = n × ((longitude + π) / (2 × π))
  • ytile = (1 - (log(tan(latitude) + sec(latitude)) / π)) / (2 × n)

Note: latitude and longitude are required in radians.

The Web Mercator tile matrix set is described as follows:

  • CRS Name: urn:ogc:def:crs:EPSG:6.18:3:3857
  • Top left corner: [ -20037508.3427892 , 20037508.3427892 ]
  • Tile size: 256 × 256 pixels
Zoom level idScale DenominatorPixel Size (m)Matrix WidthMatrix Height
0559082264.0287178156543.033928041011
1279541132.014358978271.5169640204822
2139770566.007179439135.7584820102344
369885283.0035897219567.8792410051288
434942641.501794869783.9396205025611616
517471320.750897434891.9698102512803232
68735660.3754487152445.9849051256406464
74367830.1877243571222.992452562820128128
82183915.093862179611.4962262814100256256
91091957.546931089305.7481131407048512512
10545978.7734655447152.874056570352510241024
11272989.386732772376.4370282851762420482048
12136494.693366386238.2185141425881340964096
1368247.3466831930919.109257071294068192819zoom_wm2
1434123.673341596549.5546285356470321638416384
1517061.836670798274.7773142678235163276832768
168530.9183353991362.3886571339117586553665536
174265.4591676995681.194328566955879131072131072
182132.7295838497840.5971642834779395262144262144

You can use the same principle explained for the geographic tile grid. You must include the following elements within the url:

  • EPSG - in this example it is “EPSG3857”
  • Zoom level - in this example this is “17”
  • Upper left tile - in this example it is “41955”
  • Bottom right tile - in this example it is “38143”
curl -X GET  "https://view.oneatlas.geoapi-airbusds.com/api/v1/items/<image_id>/wmts/tiles/1.0.0/default/rgb/EPSG3857/17/41955/38143.png" \
  -H "Authorization: Bearer <access_token>" \
  -H "Cache-Control: no-cache"
Not available.
Not available.

Web Mercator Converter (EPSG:3857)

Note: The converter uses input type degrees.

To retrieve a url for a single tile, you can use our simple Web Mercator converter below. You will require the following:

  • The longitude and latitude for the top left and bottom right corner. These can be found within your AOI coordinates.
  • The zoom level you would like to access. These are shown within the GetCapabilities XML result.
  • The id of the image. You should have used this previously for the GetCapabilities result.




Your Web Mercator url results:

* Required fields