Do a query through CDSE Odata API

This is an example of how to use the cdsodatacli package to query and download data from the Copernicus Data Space Ecosystem (CDSE) Odata API. A query or a request on CDSE, only provides meta-data information about the products available, not the data itself.

queryCDS -h
# example of a query
queryCDS --collection SENTINEL-1 --startdate 20230101T00:00:00 --stopdate 20230105T10:10:10 --mode IW --product SLC --querymode seq --geometry "POINT (-5.02 48.4)"

or use the method cdsodatacli.query.fetch_data() see cdsodatacli API documentation: methods descriptions.

Download a listing of product

Once you have a listing of products (for example from a query), you can download the products. There are two main ways to download products:

2. Multi-threaded download with multiple users/accounts

For a multi-threaded download with multiple users/accounts, you can use the command line tool downloadMultiThreadMultiUserS3:

downloadMultiThreadMultiUserS3 -h
    usage: downloadMultiThreadMultiUserS3 [-h] [--verbose] [--forcedownload] [--logingroup LOGINGROUP] [--listing LISTING] --outputdir OUTPUTDIR [--cdsodatacli_conf_file CDSODATACLI_CONF_FILE]
                                        [--download-backend {zipper,s3endpoint}]

    download deamon CDSE

    options:
    -h, --help            show this help message and exit
    --verbose
    --forcedownload       True -> no test of existence of the products in spool and archive directories.
    --logingroup LOGINGROUP
                            name of the group of CDSE account in the localconfig.yml [default=logins]
    --listing LISTING     path of the listing of products to download containing (Id,safename) lines
    --outputdir OUTPUTDIR
                            pathwhere product will be stored
    --cdsodatacli_conf_file CDSODATACLI_CONF_FILE
                            path to the cdsodatacli configuration file .yml [optional, default is localconfig.yml then config.yml]

There are two download backends on CDSE: “zipper” or “s3endpoint”.: We decided to remove the “zipper” backend in cdsodatacli because S3 provides better performances.

The “s3endpoint” download backend gives download speed up to 32 Mo/s while “zipper” is closer to 12 Mo/s in average.

Here is a table of download speed to compare the 2 backends, on tests performed in 2026:

	backend	average download speed (Mo/s)	total duration (seconds)
2 IW OCN	s3endpoint	10.4 Mo/s (stdev: 0.5 Mo/s)	10.0
3 IW SLC	s3endpoint	32.1 Mo/s (stdev: 15.1 Mo/s)	524.287501
2 IW OCN	zipper	5.9 Mo/s (stdev: 1.3 Mo/s)	23.04
3 IW SLC	zipper	4.2 Mo/s (stdev: 2.5 Mo/s)	2896.931142

Note

5X faster downloads for S3 in some cases!

In addition, with “s3endpoint” backend, the products are already uncompressed at the end of the download.

Get CDSE Odata IDs for a list of products

get-odata-ids -h
    usage: get-odata-ids [-h] [--verbose] [--output-listing OUTPUT_LISTING] --input-listing INPUT_LISTING [--email EMAIL] [--password PASSWORD]

    example main

    options:
    -h, --help            show this help message and exit
    --verbose
    --output-listing OUTPUT_LISTING
                            output listing where the SAFE+id will be written [optional, default is input-listing+'.ids']
    --input-listing INPUT_LISTING
                            input SAFE listing path containing only SAFE basenames
    --email EMAIL         email of the CDSE account to use for queries [optional, default None -> use cdsodatacli default behavior]
    --password PASSWORD   password of the CDSE account to use for queries [optional, default None -> use cdsodatacli default behavior]

Get equivalent S1 product types

When you have a list of Sentinel-1 products, you may want to get the equivalent product types (for example to know which S1 GRD products correspond to a list of S1 SLC products). You can use the command line tool match_s1_product_types:

match_s1_prodtypes -h
    usage: match_s1_prodtypes [-h] (--safe SAFE_ID [SAFE_ID ...] | --input-listing FILE) --prodtype TYPE --output FILE [--dev] [--verbose]

    Match Sentinel-1 SAFE products to a given product type via OData.

    options:
    -h, --help            show this help message and exit
    --safe SAFE_ID [SAFE_ID ...]
                            One or more Sentinel-1 SAFE product IDs passed directly on the command line.
    --input-listing FILE  Path to a text file with one SAFE product ID per line (blank lines ignored).
    --prodtype TYPE       Target product type to search for. Choices: GRDH, GRDM, SLC_, OCN_, RAW_
    --output FILE         Output text file to write results to (one match per line).
    --dev                 Enable dev mode with reduced number of SAFE to treat.
    --verbose, -v         Enable DEBUG-level logging.

    Examples:
    # From an inline list, look for OCN products
    python s1_matchup.py --prodtype OCN_ \
        --safe S1A_IW_GRDH_1SDV_20230726T071112_... S1A_IW_GRDH_1SDV_20230726T071137_...

    # From a file (one SAFE ID per line), look for SLC products
    python s1_matchup.py --prodtype SLC_ --input-listing my_products.txt

    # Enable verbose/debug logging
    python s1_matchup.py --prodtype OCN_ --input-listing list.txt --verbose