Provider

NB: This documentation is for user that want to use the providers. For documentation on how to implement a new provider, see Developer-Guide/Providers.

Providers are implemented in order to download scenes. They are called one by one until the corresponding image is found.

  • Copernicus: Sentinel scenes
  • Creodias: Sentinel scenes
  • GCS: any scenes stored in GCS (can be used to retrieve the annotations of an Sentinel1 archive stored in GCS)
  • Local: any scenes stored locally
  • OneAtlas: Airbus scenes (SPOT, Pleiades, PNEO)
  • ASF: sentinel1 & 2 scenes
  • Landsat AWS: Landsat 8&9

The scenes to be downloaded are sent to the Downloader Service, then the tiles to be processed are sent to the Processor Service.

If an autoscaler is configured, the downloading and the processing are done in parallel using all available machines.

Creodias

Creodias account credentials are needed.

creodias-username and creodias-password workflow and downloader arguments must be defined.

https://finder.creodias.eu/resto/api/collections/<constellation>/search.json endpoint is use to request Creodias.

and https://auth.creodias.eu/auth/realms/DIAS/protocol/openid-connect/token in order to get JWT Token.

For more information see: Creodias Documentation

Copernicus

Copernicus account credentials are needed.

copernicus-username and copernicus-password downloader arguments must be defined.

For more information see: Copernicus Documentation

GCS

The downloader service must have the rights to read files on buckets.

gs-provider-buckets workflow and downloader arguments must be defined.

List of constellation:bucket comma-separated.

bucket can contain several {IDENTIFIER} than will be replaced according to the sceneName.

IDENTIFIER must be one of SCENE, MISSION_ID, PRODUCT_LEVEL, DATE(YEAR/MONTH/DAY), TIME(HOUR/MINUTE/SECOND), PDGS, ORBIT, TILE (LATITUDE_BAND/GRID_SQUARE/GRANULE_ID)

For more information see: GCS Documentation

Local directory

No credentials needed.

local-path downloader argument must be defined (local path where images are stored)

OneAtlas

OneAtlas account credentials are needed.

oneatlas-username and oneatlas-apikey workflow and downloader arguments must be defined.

By default, OneAtlas uses:

  • https://access.foundation.api.oneatlas.airbus.com/api/v1/items as download endpoint
  • https://data.api.oneatlas.airbus.com as order endpoint
  • https://authenticate.foundation.api.oneatlas.airbus.com/auth/realms/IDP/protocol/openid-connect/token as authentication endpoint

It's possible to use another endpoint by defining oneatlas-download-endpoint, oneatlas-order-endpoint and oneatlas-auth-endpoint.

Important: concerning pricing, OneAtlas provider will be process and download image while credits are available.

For more information see: OneAtlas Documentation

ASF

Asf account credentials are needed.

asf-token downloader argument must be defined.

Asf uses https://datapool.asf.alaska.edu/SLC/S{MISSION_VERSION}/{SCENE}.zip for SLC product and https://datapool.asf.alaska.edu/GRD-HD/S{MISSION_VERSION}/{SCENE}.zip for GRD products.

ASF Documentation

Landsat AWS

AWS credentials are needed (pay-on-request): - --landsat-aws-access-key-id: Landsat AWS access key id - --landsat-aws-secret-access-key: Landsat AWS secret access key

Landsat AWS