...
The ECDS is powered by CDS technology (access via CDS-API, discovery forms etc). It shares the same authentication system, so that users can access any dataset across all data stores (CDS, ADS, EWDS, ECDS) with their ECMWF User account and the same API key which is shared between all data stores.
...
| Warning | ||
|---|---|---|
| ||
For access to |
...
different data stores |
...
(cds.ecmwf.int, ecds.ecmwf.int, etc.) |
...
...
the user must have separate .cdsapirc files |
...
with the correct |
...
URL for given data store. Alternatively, the |
...
URL and user token can be part of the Python client definition as |
...
per Examples in User guide for migration of S2S and TIGGE to ECDS. |
Find all information how to access a dataset in ECDS and the available tools and tutorials in the the ECDS home page
How to get data
...
- Install CDS-API personal access token and client.
- Search for data and generate CDS-API request by using dedicated ECDS forms (TIGGE, S2S real-time forecasts, and S2S reforecast) or MARS data catalogue (TIGGE and S2S).
- Please be aware that there are different versions of CDS-API syntaxes generated by ECDS form and by MARS catalogue. Full details and examples are available inUser guide for migration of S2S and TIGGE to ECDS.
Warning title Please take into account some considerations about the content: - Different ECMWF Public Datasets ECDS datasets include different "parameters" , "times", and "steps"
- In each ECMWF Public Dataset each ECDS dataset not all the "parameters" are available from all "steps"
- In each ECMWF Public Dataset not each ECDS dataset not all the "steps" are available from all "times"
- Please be aware that there are different versions of CDS-API syntaxes generated by ECDS form and by MARS catalogue. Full details and examples are available inUser guide for migration of S2S and TIGGE to ECDS.
- Tailor CDS-API request as needed and run it following Use the CDS API client for data access to get the requested data.
...