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
...
- 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.
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).
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).
|
Overview of current and future tools
| current | new | |
|---|---|---|
| data retrieval |
|
|
| data discovery | dedicated |
|---|
web portals * | 1) dedicated ECDS |
portal |
|
|
|
2) dedicated MARS catalogues |
| data history | the same as before | |
|---|---|---|
| main web portal | the 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:
- forecasts: https://ecds.ecmwf.int/datasets/s2s-forecasts?tab=download
- reforecasts: https://ecds.ecmwf.int/datasets/s2s-reforecasts?tab=download
Data retrievals
Up to now, there have been 2 options how to access programmatically S2S or TIGGE data:
- direct MARS access (custome language)
- Web WEB-API (Python)
The required data specification is the same has been analogical in both options (using MARS syntax).
In the new ECDS, those options are analogicalsimilar:
- 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.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
| example | MARS language |
|---|
| current WEB-API | new CDS-API (MARS like) | new CDS-API ("beautified") | |
|---|---|---|---|
| request | |
|
|
|
|
|
|
|
|
|
| #!/usr/bin/env python | |||
| 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", | Alternatively the url and token can be part of the Python client definition: client = cdsapi.Client(url="https://ecds.ecmwf.int/api", |