TRAITEMENTS À LA DEMANDE

Chaque traitement proposé est décrit ici ainsi que dans le centre de traitements, la description comprend :

  • Un titre décrivant le traitement succinctement
  • Une description expliquant le traitement en détail, bandes spectrales utilisées …, les paramètres choisis pour le traitement, parfois une image démonstrative d’un résultat
  • La compatibilité avec les produits/types de produits en entrée disponibles dans PEPS
  • Le format de sortie du résultat du traitement
  • Les limitations du traitement
  • Les sources utilisées si elles sont publiques.
  • L’user est transmis par l’APIKEY, il n’est donc pas nécessaire de le transmettre dans le fichier data.json

ORTHO-RECTIFICATION S1 SUR LA GRILLE S2

Description:

Ortho-rectification and tiling of Sentinel-1 GRD products on the Sentinel-2 grid (MGRS)This treatment has been set up to facilitate :

  • Superimposing a set of Sentinel-1 images
  • Sentinel-1, Sentinel-2 multi-sensor processing
  • Overlay of Sentinel-1 and Sentinel-2 images
  • Sentinel-1 and Sentinel-2 mosaicking

The coverage rate of an MGRS tile by the Sentinel-1 product footprint must be at least 1% for the corresponding ortho-rectified image to be generated.
The first step is gamma calibration.

Command:

The APIKEY.

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/ortho-s1-grd/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Product id of the S1 GRD product to be processed.

Features:

Average running time is 20 minutes.

Output format:

The result is a zip file containing all the tiles generated in GeoTiff format.

How to launch ?

Limitations:

The treatment does not produce results in the following cases:

  • for latitudes above 60° or below -60°
  • for products with a Digital Terrain Model (DTM) coverage rate of less than 100% for target MGRS tiles

Sources:

  • This process was provided by T. KOLECK : link s1tiling
  • Processing is based on OTB version 6.6.1: link to the orfeo-toolbox
  • The DTM used is the SRTM at 30m (SRTMGL1 version 003 of 2000.02.11, DOI: 10.5067/MEaSUREs/SRTM/SRTMGL1.003).
  • Documentation is available here

ORTHO-RECTIFICATION S1 SUR LA GRILLE S2 en mode multi-temporel (Ortho MT)

Description:

Ortho MT processing enables ortho-rectification to be carried out on one or more tiles, over a given period. This processing was implemented to facilitate :

  • Overlaying a set of Sentinel-1 images
  • Sentinel-1, Sentinel-2 multi-sensor processing
  • Superimposition of Sentinel-1 and Sentinel-2 images
  • Sentinel-1 and Sentinel-2 mosaicking

The coverage rate of an MGRS tile by the Sentinel-1 product footprint must be at least 1% for the corresponding ortho-rectified image to be generated.nerated.

Command:

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/ortho-s1-grd-mt/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"mgrs_list": "TILE_LIST", # separated with a comma like this : "31TCJ,01CDS,29MNM" 
"start_date": "YYYY-MM-DD", 
"end_date": "YYYY-MM-DD", 
"polarisation": "[VV VH OR VV OR HH OR HH HV]", 
"orbit_direction": "[all OR ascending OR descending]", 
"sensor_mode": "[SM OR EW OR IW]", 
"relative_orbit_number": -1, 
"calibration": "[sigma OR beta OR gamma]", 
"notif-email": true # or false, 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Product id of the S1 GRD product to be processed. See above for more details about the input parameters.  

Features:

Average running time is 60 minutes.

Output format:

The result is a zip file containing all the tiles generated in GeoTiff format.

How to launch ?

Limitations:

The treatment does not produce results in the following cases:

  • for latitudes above 60° or below -60°
  • for products with a Digital Terrain Model (DTM) coverage rate of less than 100% for target MGRS tiles

Sources:

  • This process was provided by T. KOLECK : link s1tiling
  • Processing is based on OTB version 6.6.1: link to the orfeo-toolbox
  • The DTM used is the SRTM at 30m (SRTMGL1 version 003 of 2000.02.11, DOI: 10.5067/MEaSUREs/SRTM/SRTMGL1.003).
  • Documentation is available here

EXTRACT_POLARIZATION

Description:

The average size of the SLC product is around 3.5Go. This treatment/process extracts data linked to one or other of the polarization for bipolarized products (HH+HV or VV+VH)

Command:

Here is the command to use to start the process :

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/extract-polarization-s1/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"polarization": "vv", # any from "[vv, vh, hh, hv]", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Product id of the S1 SLC product to be processed and desired polarization (vv, vh, hh, or hv)

Features:

Average runtime is 15 minutes.

Output format:

Archive {Product_id}.SAGE_extract_{Polarization}.zip containing the original archive minus the data related to the unwanted polarization.

Limitations:

This treatment only takes in bipolarized S1 SLC product (HH+HV or VV+VH).

How to launch ?

EXTRACT_METADATA_S2ST

Description:

This process downloads a Sentinel-2 product without the image files (jpg2000).

Command:

Here is the command to use to start the process

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/extract-metadata-s2st/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Sentinel 2 product type L1C

Features:

Average Runtime is 15 min

Output format:

Archive {Product_id}.SAFE_extract_meta_data.zip containing the product archive without image files.

Limitations:

Only Sentinel-2 L1C products are processed.

How to launch ?

MAJA

Description:

The MAJA chain (MACCS ATCOR Joint Algorithm, pronounced « maya ») is a cloud detection and atmospheric correction chain, suitable for processing time series of high-resolution images acquired from constant or near-constant viewing angles.

In particular, it is used to process data from SENTINEL-2. It is based on the MACCS chain developed by the CNES and CESBIO since 2008, and has incorporated methods from the DLR ATCOR chain since 2016. It is therefore now the subject of collaboration between CNES, DLR and CESBIO, and has also received financial support from ESA.

Command:

Here is the command to use to start the process :

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/maja/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Sentinel-2 tile product id to be processed

Features:

Average runtime is 45 minutes.

Output format:

The result is a zip file containing all the outputs relative to the requested date.

Limitations:

  • Data type must be SENTINEL-2
  • Treatment level should be LEVEL1C
  • Images must contain more than 90% cloud
  • The products must have an acquisition date after 06 December 2016. (It may not work correctly on products acquired before this date because re-tiles from Sentinel-2 products in datatake format).

How to launch ?

FULL MAJA

Description:

FULL_MAJA processing applies MAJA processing over a defined period for a given tile (see MAJA processing description for information on the algorithm used). It should be used for a period of between 2 months and 1 year.

Command:

Here is the command to use to start the process :

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/full-maja/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"startDate": "YYYY-MM-DD", 
"completionDate": "YYYY-MM-DD", 
"tileid": "WXYZ", 
"relativeOrbitNumber": "none" (or an "integer"), 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

  • Start date
  • End date
  • Tile
  • Relative Orbit Number

Features:

Average runtime is 8H – 24H. it depends on the number of the products that will be processed.

Output format:

The results are multiple zip files containing all the outputs relative to the requested dates.

Limitations:

  • Processing does not work for images containing more than 90% clouds. Calculation time may be affected by demand,
  • Processing takes between 30 and 40 hours when run on a year’s worth of images,
  • It is currently limited to a maximum of one year and a minimum of two months, it is also limited to the processing of 10 tiles in parallel for all the users in the world,
  • It also relies on a robot (HPSS) that downloads the Sentinel-2 data stored on tapes. When HPSS is overloaded, it happens that some products are not provided in time and not processed resulting in data gaps in the time series.

How to launch ?

RGB_S2ST / SWIR_S2ST / IRGB_S2ST / TCI_S2ST

Description:

This workflow offers 3 color composition processes RGB, IRGB, SWIR: Extraction in 16-bit format of bands at 10m for color composition with :
1 = B4 (665 nm – 10 m)
2 = B3 (560 nm – 10 m)
3 = B2 (490 nm – 10 m)
4 = B8 (490 nm – 10 m)
5 = B11 (490 nm – 20 m resampled to 10m with linear interpolation)

The WMS link shows the results of RGB (r=1,g=2,b=3), IRGB (r=4,g=1,b=2) and SWIR (r=5,g=4,b=1) color composition at 20m resolution.

It also offers TCI processing: Extraction in GeoTIFF format of the True Color Image band of S2 Single Tile products in 8-bit integer.

According the following image, (RGB = B04, B03, B02), (IRGB= B08, B03, B04) and (SWIR= B11, B08, B04).

Command:

Here is the command to use to start the process :

  • rgb-s2st
curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/rgb-s2st/execution"
  • irgb-s2st
curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/irgb-s2st/execution"
  • swir-s2st
curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/swir-s2st/execution"
  • tci-s2st
curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/tci-s2st/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive
}

Inputs:

Sentinel-2 tile product id to be processed

Features:

Average runtime is 10 minutes.

Output format:

The result is a zip file containing all the outputs relative to the requested date.

Limitations:

  • Data S2 Single Tile
  • Data type must be SENTINEL-2
  • Treatment level should be L1C and L2A

How to launch ?

NDVI_S2ST

Description:

NDVI is the Normalized Difference Vegetation Index. The index is calculated in float mode at full resolution (10 m) using the following bands:

  • B8 (842 nm)
  • B4 (665 nm)

Command:

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/ndvi-s2st/execution"

You first need to get and export your APIKEY as described in https://geodes.cnes.fr/support/api/ and create a json file named « data.json » with the following information needed for the process :

{
"inputs": { 
"product-title": "PRODUCT_NAME", 
"notif-email": "true" # or "false", 
"restoration": false # or true if the data need to be restored from the archive   
}

Input:

Sentinel-2 tile product id to be processed

Features:

The average execution time is 10 minutes if the data is online.

Output:

The result is tiled according to the Cloud Optimized Geotiff recommendation and losslessly compressed with DEFLATE.

Limitations:

This processing only takes as input S2 Single Tile data of levels L1C and L2A.

How to launch ?

Sources:

Treatment is based on OTB version 6.6.1: link to the orfeo-toolbox

GDM_SAR

Command:

curl -XPOST -k --data "@data.json" -H "Content-Type:application/json" -H "X-API-Key: $APIKEY" -H "Prefer:respond-async" "https://geodes-portal.cnes.fr/processing/processes/gdm-sar/execution"

example:

{  
"inputs": {
    "product-ids": "S1A_IW_SLC__1SDV_20220204T055231_20220204T055258_041759_04F828_E0F1,S1A_IW_SLC__1SDV_20220204T055206_20220204T055233_041759_04F828_74D2,S1A_IW_SLC__1SDV_20220123T055231_20220123T055258_041584_04F239_4E5D,S1A_IW_SLC__1SDV_20220123T055206_20220123T055233_041584_04F239_474F",
    "name": "template_grenoble_iw123_noatmo",
    "atmo": "no",
    "bbox": "5.5371,44.9382,5.807,45.3382",
    "priority": "normal",
    "provider": "nsbas-gdmsar",
    "sub-swath": "iw1,iw2,iw3",
    "rlooks-int": "4",
    "rlooks-unw": "4",
    "unw-method": "mpd",
    "polarisation": "vv",
    "nsbas-config": "expert_mode=no",
    "unw-seed-lat": "45.18513422001137",
    "unw-seed-lng": "5.603027343750001",
    "relative-orbit": "D37",
    "notify-url": "https://gdm.poleterresolide.fr/scripts/setStatus"
 }
}

Input

GDM-SAR is a very sensitive process in terms of inputs. For instance, the products chosen must respect a few rules. They must be contained in the bbox, and have the same relative orbit than the one chosen. For the polarisation, unw-seed lat and lng, they are optional.

Name is the name you give the process you lanch.

Priority is for the priority in the process chain, put it to normal.

nsbas-config allow the user to chose the config for the process, if you want the nominal process put expert_mode=no

notify-url is the url launching the process.

Atmo allow the user to chose which kind of atmospheric correction to do if any.

Specificity

This process is not like the others available on GEODES. It is not launch-able from the GEODES portal but from different website such as https://gdm.poleterresolide.fr

Also, this process will not send an email when it is finished and does not require its products to be restored to the tier 2.

How to Launch

Launch follow-up

It is possible to view the status of a specific job using its ID or the status of all the launched jobs for a specific user using his email address.

i. The case of visualizing the status of a specific job: 

The following command lists the status of a specific launched job:

curl -XGET-H "X-API-Key: $APIKEY"-k "https://geodes-portal.cnes.fr/processing/jobs/JOB_ID"

JOB_ID should be replaced by the ID of the job! 

Timeout

All process ccan be lunched with the additional « timeout » parameter

Restoration of product on the Tier 3

When the input of your process is on the tier 3 of the datalake, you must restore it to the tier 2 for your process to be executed.

To do so you need to add the field « restoration » with the value true in the input JSON.

Here’s an example :

{
"inputs": {
 "product-title": "NOM_PRODUIT",
 "notif-email": "true",
 "restoration": false # or true if the data need to be restored from the archive
 }
}

Rechercher