Viewing
The viewing interface is implemented following the Web Map Tile Service (WMTS) as well as the Web Map Service (WMS) . Both services are implemented by a wide range of client software which makes it as simple as possible to integrate the viewing service as needed.
Service endpoints optimized for performance as well as for flexibility are provided alongside each other.
Performance optimized service
The performance optimized service variant is provided under the path
/cache/ows?
.
This endpoint offers access to predefined visualizations via WMTS and WMS. The GetTile as well as GetMap requests are answered from image tiles cached on object storage when possible. :numref:`fig_wmts_tiles` below shows the three predefined visualizations, true color, false color, and NDVI of the same image tile.
WMTS Tiles - True color, false color, and NDVI
Image tiles not yet present in the cache are stored upon first hit for consecutive requests. This is the so-called on-demand caching. The operator might decide for optimal performance, even for the first request, to pre-seed the cache. Also a mixed variant with a partly pre-seeded cache for example up to a certain zoom level is possible.
However, this is done fully transparent to the users and the only impact is that they might need to wait slightly longer when they are the first to visualize a certain product.
This service offers access on collection level only. Individual products can be
addressed using the time
parameter given that they do not cover one another
on the time axis.
The best performance is offered at the WMTS interface which serves images tiles as they are cached without the need of any reprocessing. WMS responses are generated on-the-fly from image tiles and might thus need some reprocessing to stitch together and scale image tiles.
TODO: full layers
More sophisticated reprocessing like reprojection or custom color adjustments are not offered at this endpoint.
Flexible service
The other service variant offered is optimized for the best possible flexibility
and can be accessed at the path /ows?
.
This endpoint offers the following customizations via WMS:
- Access to individual products via ID (
cql=identifier='ID'
) - Access to entire collections/datasets supporting
time
parameter - Various layers as defined by the Earth Observation Application Profile of WMS like one
showing outlines of products (
__outlines
) - Additional useful layers like one showing both, products and outlines,
correctly rendering topology of outlines (
__outlined
) or one showing a validity mask (__validity
) or applied validity mask (___masked_validity
) - Numerous styles for layer where feasible like outlines or NDVI
(
layers=ID__NDVI&STYLES=coolwarm
) - Reprojection to operator configured coordinate reference systems
- Color adjustment via custom linear stretch
dim_range=<low-red-or-grey> <high-red-or-grey>[,<low-green> <high-green>,<low-blue> <high-blue>]
- Filtering of products to render into collection/dataset visualizations via
Common Query Language (CQL) for example
&cql=cloudCover<1
- All other standard WMS parameters like
transparent
,format
, etc.
All these customization parameters can of course be combined as needed.
Loading in QGIS
WMS loading in QGIS
WMS loading in QGIS
Continue reading about the provided :ref:`downloading` services.