Introduction

The TIGGE and S2S datasets will be migrated to the new ECMWF Data Store (ECDS) based on the Common Data Store Engine (CDS-E).

The current access method Web-API will be changed to the analogical CDS-API.

For more details about the migration schedule, visit Decommissioning of ECMWF Public Datasets Service

Purpose of this page is to describe the current and future access tools to both datasets.

Overview of current and future tools

* these tools will be still available in parallel with the new ECDS discovery tools 

**direct access to MARS is not publicly available

Data access

For data discovery (understanding which data is available) and generation of sample retrieval codes, the dedicated web portals are available (see table in the Overview section above).

For programmatic bigger data retrievals, the python API or direct access to MARS should be used (the direct access to MARS is not publicly available).

Data discovery

Newly to browse the available data, there are dedicated MARS catalogues available:

• https://apps.ecmwf.int/data-catalogues/tigge
• https://apps.ecmwf.int/data-catalogues/s2s

The previous ECMWF  web portals are still available too:

• https://apps.ecmwf.int/datasets/data/tigge
• https://apps.ecmwf.int/datasets/data/s2s

In the future, new dedicated discovery forms replacing the older ECMWF web portals might be available directly in the ECDS too.

Data retrievals

Currently there are 2 options how to access programmatically S2S or TIGGE data:

• direct MARS access (custome language)
• Web-API (Python)

The required data specification is the same in both options.

In the future, those options will be analogical:

• direct MARS access (custome language)
• CDS-API (Python)

The standard CDS-API data specification is virtualy the same as the current Web-API, only the Python modules and functions differ.

Registration

All users must register with ECDS to get the access to datasets using CDS-API. Although the portal shares similar infrastructure as the previous Copernicus Climate Data Store, the existing user tokens (API keys) cannot be reused in ECDS.

Users are asked to pay attention to state correctly details about Affiliation, Thematic activities and Activity sectors during the registration as that information helps to understand users needs and interests, which can trigger future changes of TIGGE or S2S datasets.

Examples of the current and future retrieval requests

retrieve,
class=ti,
date=2024-02-01/to/2024-02-02,
expver=prod,
grid=0.5/0.5,
levtype=sfc,
origin=ecmf,
param=121/122,
step=6/to/24/by/6,
time=00:00:00,
type=cf,
target="output"
        

#!/usr/bin/env python
from ecmwfapi import ECMWFDataServer

server = ECMWFDataServer()

server.retrieve({
    "class": "ti",
    "date": "2024-02-01/to/2024-02-02",
    "expver": "prod",
    "grid": "0.5/0.5",
    "levtype": "sfc",
    "origin": "ecmf",
    "param": "121/122",
    "step": "6/to/24/by/6",
    "time": "00:00:00",
    "type": "cf",
    "target": "output"
})
        

#!/usr/bin/env python
import cdsapi

client = cdsapi.Client()
            
dataset = 'tigge'
request = {
    "class": "ti",
    "date": "2024-02-01/to/2024-02-02",
    "expver": "prod",
    "grid": "0.5/0.5",
    "levtype": "sfc",
    "origin": "ecmf",
    "param": "121/122",
    "step": "6/to/24/by/6",
    "time": "00:00:00",
    "type": "cf"
}

target = "download.grib2"
client.retrieve(dataset, request, target)

          
        

--> cat ~/.ecmwfapirc
{
    "url"   : "https://api.ecmwf.int/v1",
    "key"   : "<personal token>",
    "email" : "<personal email>"
}

--> cat $HOME/.cdsapirc
url: https://ecds.ecmwf.int/api
key: <personal token>

client = cdsapi.Client(url="https://ecds.copernicus-climate.eu/api", key="<personal token>")