- What is CREODIAS?
- Computing & Cloud
- Data & Processing
- Pricing Plans
- Fight with COVID-19
- Examples of usage
- Processing Sentinel-5P data using HARP and Python
- EO Data Access (R)evolution
- Land cover classification using remote sensing and AI/ML technology
- AI-based satellite image enhancer and mosaicking tools
- Monitoring air pollution using Sentinel-5P data
- Species classification of forests
- Enabling AI / ML workflows with CREODIAS vGPUs
- Satellite remote sensing analyses of the forest
- Satellite-based Urban Heat Island Mapping on CREODIAS
- Old but gold - historical EO data immediately available and widely used on CREODIAS
- CREODIAS for emergency fire management
- AgroTech project as an example of how CREODIAS can be used for food and environmental research
- Monitoring Air Quality of Germany in Pre vs During COVID Lockdown Period
- EO4UA
- Common Agricultural Policy monitoring with Earth Observation
- Applications of CREODIAS data
- Meteorological data usage on the CREODIAS platform
- Building added value under Horizon Europe with CREODIAS
- CREODIAS: Introduction to SAR Sentinel-1 data
- Land subsidence and landslides monitoring based on satellite data
- Satellite imagery in support of the Common Agriculture Policy (CAP) and crop statistics
- Useful tools for data processing, available on CREODIAS platform
- CREODIAS for hydrological drought modelling
- CREODIAS for managing Urban Heat Islands
- CREODIAS for Digitising Green Spaces
- CREODIAS for Air Quality
- Advanced data processors on CREODIAS
- CREODIAS for your application
- Solutions for agriculture with CREODIAS
- Earth Observation data for Emergency response
- Security Applications with Satellite Data
- Climate Monitoring with Satellite Data
- Water Analysis on CREODIAS
- CREODIAS for land and agriculture monitoring
- Solutions for atmospheric analysis
- Example of tool usage
- Processing EO Data and Serving www services
- Processing and Storing EO
- Embedding OGC WMS Services into Your website
- GPU Use Case
- Using the EO Browser
- EO Data Finder API Manual
- Use of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of WMS Configurator
- DNS as a Service - user documentation
- Use of Sinergise Sentinel Hub on the CREODIAS EO Data Hub
- Load Balancer as a Service
- Jupyter Hub
- Use of CREODIAS Finder for ordering data
- ESRI ArcGIS on CREODIAS
- Use of CEMS data through CREODIAS
- Searching, processing and analysis of Sentinel-5P data on CREODIAS
- ASAR data available on CREODIAS
- Satellite remote sensing analyses of the forest
- EO Data Catalogue API Manual
- Public Reporting Dashboards
- Sentinel Hub Documentation
- Legal Matters
- FAQ
- News
- Partner Services
- About Us
- Forum
- Knowledgebase
Sentinel Hub Documentation
Sentinel Hub is a multi-spectral and multi-temporal big data satellite imagery service, capable of fully automated archiving, real-time processing and distribution of remote sensing data and related EO products, managed by Sinergise Ltd. For more information on Sinergise go to Third Party Services.
WMTS request
The Sentinel WMTS (Web Map Tile Service) service conforms to the WMTS standard. It provides access to Sentinel-2's 13 unprocessed bands (B01 through B12, with B8A following B08) as well as processed products such as true color imagery and NDVI. Access to the service is done via a custom server instance URL which will be provided to you upon registration. Provides access to the same bands product and additional informational layers as the WMS request except only one layer can be specified at once, even when only raw Sentinel-2 bands are used. As with the WMS service, WMTS is also only available via a user-preconfigured custom server instance URL.
The base URL for the WMTS service:
http://services.sentinel-hub.com/ogc/wmts/{INSTANCE_ID}
The service supports the same output formats as the WMS request and supports the standard WMTS requests GetTile
, GetCapabilities
. It supports WMTS version 1.0.0.
The WMTS service output image type can be a 1 or 3 component 8-bit PNG or JPEG; alternatively also an n-component 8 or 16-bit TIFF. Use the proper type when setting the "FORMAT" parameter. For JPEG, use "image/jpeg" or "image/jpg" and for PNG use "image/png". For TIFF, if you use just "image/tiff", the service will generate 8-bit TIFF for the products and 16-bit TIFF for the raw Sentinel-2 bands. If you want to force a specific TIFF bit depth, use "image/tiff;depth=8" or "image/tiff;depth=16". When PNG or TIFF is requested the "TRANSPARENT" parameter determines whether the produced image will have transparent pixels where no input data is available or not. For a list of supported coordinate reference systems check the GetCapabilities
result.
Check GetCapabilities
for a list of supported tile matrix sets which can be used for the TILEMATRIX and TILEMATRIXSET parameters.
WMTS parameters
Standard common WMTS URL parameters (names are case insensitive):
WMTS parameter | info |
---|---|
SERVICE |
Required, must be "WMTS". |
VERSION |
WMTS version standard. Optional, default: "1.0.0". Supported values: "1.0.0". |
REQUEST |
What is requested, valid values: |
TIME |
(when REQUEST = |
In addition to the standard WMTS request parameters, the WMTS service also supports many custom URL parameters. See Custom service URL parameters for details.
Standard GetTile
request URL parameters:
WMTS parameter | info |
---|---|
TILEMATRIXSET |
The matrix set to be used for the output tile. Check |
TILEMATRIX |
The matrix to be used for the output tile. Check |
TILECOL |
The column index of the output tile. Check |
TILEROW |
The column index of the output tile. Check |
LAYER |
The preconfigured (in the instance) layer for which to generate the output tile. |
FORMAT |
The returned image format. Optional, default: "image/png". Detailed information about supported values. |
Examples
Example below shows how to create the configuration for accessing a WMTS from a GetCapabilities response:
<!DOCTYPE html> <html> <head> <title>WMTS Layer from Capabilities</title> <link rel="stylesheet" href="http://openlayers.org/en/v3.17.1/css/ol.css" type="text/css"> <script src="http://openlayers.org/en/v3.17.1/build/ol.js"></script> </head> <body> <div id="map" class="map"></div> <script> var parser = new ol.format.WMTSCapabilities(); var map; fetch('<ENTER YOUR WMTS URL HERE>?REQUEST=GetCapabilities').then(function(response) { return response.text(); }).then(function(text) { var result = parser.read(text); var options = ol.source.WMTS.optionsFromCapabilities(result, {layer: 'TRUE_COLOR', matrixSet: 'PopularWebMercator512'}); map = new ol.Map({ layers: [ new ol.layer.Tile({ source: new ol.source.OSM(), opacity: 0.7 }), new ol.layer.Tile({ opacity: 1, source: new ol.source.WMTS(options) }) ], target: 'map', view: new ol.View({ center: [19412406.33, -5050500.21], zoom: 5 }) }); }); </script> </body> </html>