...
As the ECDS portal shares similar infrastructure as the Copernicus Climate Data Store, the existing user tokens (CDS-API keys) can be reused in ECDS. After first log in, a user must accept the ECDS terms and conditions and TIGGE/S2S licence to get the access to the data.
Be aware that currently to access 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 (this can change in near future). Alternatively the URL and user token can be part of the Python client definition as per Examples below. |
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.
...
| example | MARS language | current WEB-API | new CDS-API (MARS like) | new CDS-API ("beautified" - generated by ECDS) * |
|---|---|---|---|---|
| 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", |
...