...

Introduction

...

...

...

...

...

...

...

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

Overview of current and future tools

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

...

For programmatic bigger data retrievals, the python CDS-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 data portals are still available too:

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

In the futurecase of S2S, new dedicated discovery forms replacing the older ECMWF web portals might be are available directly in the ECDS too.:

• forecasts: https://ecds.ecmwf.int/datasets/s2s-forecasts?tab=download
• reforecasts: https://ecds.ecmwf.int/datasets/s2s-reforecasts?tab=download

Data retrievals

Currently there are Up to now, there have been 2 options how to access programmatically S2S or TIGGE data:

...

The required data specification is the same in both options.

In the futureECDS, those options will be are 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, methods and functions differ.

Registration

All users must register with ECDS to get the access to its datasets using CDS-API. Although the portal shares similar infrastructure as the previous Copernicus Climate Data Store, the existing The user tokens (API keys) cannot be reused in ECDScan be used to access any dataset across all  data stores run by ECMWF (CDS, ADS, EWDS, 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

...

older (Web-API) and new (CDS-API) 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.

ecmwf.

int/api", key="<personal token>")