Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

The

...

TIGGE and S2S

...

datasets are 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

...

...

  • Service
  • Purpose of this page is to describe the current and future access tools to

...

  • both datasets.

The current TIGGE and S2S users can easily adapt their retrieval requests following the new CDS-API, MARS like, syntax (see in the table below with the examples). 

  • this kind of requests is generated automatically using dedicated MARS catalogues

All users are encouraged  to try the new,  ECDS dedicated, version of the retrieval requests, which some may find more user friendly (see new CDS-API ("beautified") example).

  • this kind of requests is generated automatically using forms in ECDS portal
Overview of current and future tools

currentnew
data retrieval
Web
  • WEB-API  (python)
  • direct MARS access**
  • CDS-API (python)
  • direct MARS access**
data discovery

dedicated

ECMWF data

web portals *

1) dedicated ECDS

portals

portal

without ECDS
forecasts
-reforecastsforecasts and reforecasts:
without ECDS
      • with new forms)

2) dedicated MARS catalogues

(option to ECDS forms)

data historythe same as before
main web portalthe same as before

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

**direct access to MARS is not publicly available

...

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

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, Users have two options to browse the available data, there are S2S or TIGGE data - new dedicated ECDS portal and new dedicated MARS catalogues available:

...

.

...

See exact links in table above with the overview of all available tools.

Data retrievals

Until

...

The previous ECMWF  web data portals are still available too:

In case of S2S, new dedicated discovery forms replacing the older ECMWF web portals are available directly in the ECDS:

Data retrievals

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

The required data specification is the same has been analogical in both options (using MARS syntax).

In the new ECDS, those options are analogicalsimilar:

The standard CDS-API data specification is virtualy the same as the current Web-API, only the Python modules, methods and functions differ.requests can be using MARS like syntax or newly more user friendly "beautified" version of it (i.e. the meta data and values are written in more self-explaining way) 

Registration

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

exampleMARS language
Web
current  WEB-API new CDS-API (MARS like)new CDS-API ("beautified")
request
retrieve,
class=ti,
date=2024-02-01/to/2024-02-
02
03,
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
03",
    "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'
"tigge-forecasts"
request = { "class": "ti", "date": "2024-02-01
/to
/2024-02-
02
03",
    "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
output"
client.retrieve(dataset, request, target)
#!/usr/bin/env python
import cdsapi
client = cdsapi.Client()

dataset = "tigge-forecasts"

request = {
  "year": ["2024"],
  "month": ["02"],
  "day": ["01", "02", "03"],
  "grid": "0.5/0.5",
  "level_type": "single_level",
  "origin": "ecmf",
  "variable": ["maximum_2m_temperature_last_6_hours",
     "minimum_2m_temperature_last_6_hours"],
  "leadtime_hour": "6/to/360/by/6",
  "time": "00:00:00",
  "forecast_type": "control_forecast",
  "data_format": "grib"
}

target = "output"
client.retrieve(dataset, request, target)
API key

Direct access to MARS database needed

(not publicly available)


--> 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>
--> cat $HOME/.cdsapirc
url: https://ecds.ecmwf.int/api
key: <personal token>
Alternatively the url and token can be part of the Python client definition:
client = cdsapi.Client(url="https://ecds.ecmwf.int/api", 
key="<personal token>")
Alternatively the url and token can be part of the Python client definition:
client = cdsapi.Client(url="https://ecds.ecmwf.int/api", 
key="<personal token>")