Goodbye legacy Climate Data Store, Hello New Climate Data Store (CDS)!

Announcements C3S - Announcements
1

Today 26th September 2024, CDS-Beta has officially become the new CDS:

https://cds.climate.copernicus.eu/

The legacy system is now decommissioned and no longer accessible. All API requests attempting to retrieve data from the legacy system will systematically fail. However, no further support will be provided on the legacy system.

If you are a CDS-beta API user, requests will be automatically redirected from the beta URL to the proper one until 20th October 2024. You are advised to update the URL in your .cdsapirc file at your earliest convenience by 20th October 2024 (login here to check URL to use in .cdsapirc file).

url: https://cds-beta.climate.copernicus.eu/api → url: https://cds.climate.copernicus.eu/api
key: xx-xx-xx-xx-xx

Following the CDS-Beta phase, the new CDS is in its early days of full operations and still undergoing enhancements and fine tuning. Some disruptions are to be expected with the implementation of improvements. Some issues are yet to be fully addressed: for example we are aware of unexpectedly long queue times and are actively working at improving the situation.

We thank you all again for your patience during this significant modernisation of our Data Stores and eagerly await for your constructive feedback. Your feedback is key to improve the user experience on the new CDS for the benefit of everyone.

Thank you.

ECMWF Support
on behalf of the Data Stores team

2 Likes
2

Is the deadline 2024 or 2026? There are two different dates here.

3

Well spotted @Peter_Richardson!
Should have read 2024, not 2026!
That was a regrettable typo! :frowning:
Sorry about that!

4

how can i access to GloFAS data from CDS dataset

5

All CEMS datasets (e.g. GloFAS data) are available from the new CEMS Early Warning Data Store (CEMS EWDS).
If you are retrieving data using the API, please check the URL in your .cdsapirc file points to the EWDS as shown here.

1 Like
6

The programmatic API for ERA5 reanalysis still does not work. We cannot yet download near real-time data. For instance, temperature in Bangladesh is not available later than 2024.09.15:

:: WARNING: Incomplete file on the  2024.09.15
:: WARNING: There may be a problem with the ERA5 latency.

Support is unresponsive. Are we the only one with this issue?

1 Like
7

Hello,

thank you for your work. I have questions regarding daily climate values:

  1. When can one expect the new ERA5 Daily means feature?
  2. How will the feature generally handle daily means of hourly data? If the data represent values for hourly time points (e.g. temperature), I assume the correct mean should consider the 2 values from Day at 00:00 and Day+1 at 00:00 , take their mean, and put this together with the other 23 values (from Day at 01:00 to Day at 23:00) to get the daily mean temperature. Is this correct?
  3. Will the feature correctly handle accumulative data (e.g. precipitation), where the sum over 24 hours for a Day is found in the hourly value for Day+1 at 00:00?
  4. Will it be possible to get correct daily values for different time zones, i.e. not UTC?
8

requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://cds.climate.copernicus.eu/api/v2/resources/reanalysis-era5-land。I have this problem all time

1 Like
9

Is anyone else having new issues since a few days, where requesting era5-land with the following:

{
    "date": "2024-10-04",
    "time": [
        "00:00",
        "01:00",
        "02:00",
        "03:00",
        "04:00",
        "05:00",
        "06:00",
        "07:00",
        "08:00",
        "09:00",
        "10:00",
        "11:00",
        "12:00",
        "13:00",
        "14:00",
        "15:00",
        "16:00",
        "17:00",
        "18:00",
        "19:00",
        "20:00",
        "21:00",
        "22:00",
        "23:00"
    ],
    "variable": [
        "10m_u_component_of_wind",
        "10m_v_component_of_wind",
        "2m_dewpoint_temperature",
        "2m_temperature",
        "potential_evaporation",
        "skin_temperature",
        "soil_temperature_level_1",
        "soil_temperature_level_2",
        "surface_net_solar_radiation",
        "surface_pressure",
        "total_evaporation",
        "total_precipitation",
        "volumetric_soil_water_layer_1",
        "volumetric_soil_water_layer_2"
    ],
    "format": "netcdf.zip",
    "area": [
        55.5,
        -7.4,
        49.8,
        0.0
    ]
}

Results in zip files that now contain gribs instead of netcdf files? This only became a problem past 2024-10-07, and seems to be a change in behaviour.

10

Hi @George_Onoufriou ,
Apologies, a bug was introduced one Monday in how we handle the legacy syntax. The fix will be released next week, however I would still advise to update to use the updated syntax where we have separated the data-format (grib or netcdf) from the download-format (zip or unarchived/not-zipped). Therefore, you should replace:

    "format": "netcdf.zip",

with:

 "data_format": "netcdf",
 "download_format": "zip",

Many thanks,
Eddy

1 Like
11

Cheers @Edward_Comyn-Platt that works beautifully!

12

Has there been a reply to this issue? I am getting this error when downloading sis-agrometeorological-indicators. I have updated my cdsapi as well as the .cdsapirc file but the error persists. What could be the problem?

1 Like
13

For me the new CDS doesn’t work well. It’s a shame because the old one was great.

14

Please be aware that as initially published in this topic, the cds-beta URL was planned to be discontinued and users were advised to update the URL in their .cdsapirc file by 20th October 2024.

We can confirm that the cds-beta URL is now discontinued. And this explains why some users are getting some SSL: CERTIFICATE_VERIFY_FAILED errors.

If you have not already done so, please update the URL in your .cdsapirc file as shown below:

url: https://cds.climate.copernicus.eu/api
key: xx-xx-xx-xx-xx

Alternatively, login here to check URL to use in .cdsapirc file.

Thank you

ECMWF Support
on behalf of the Data Stores team

2 Likes
15

Why do I keep getting the error message like,
HTTPError: 404 Client Error: Not Found for url: https://cds.climate.copernicus.eu/api/resources/reanalysis-era5-single-levels?
Please help!

1 Like
16

For me, for one month era5land data (one variable) was around 9 GB (before CDS update), but now is around 3 GB. It is both in “netcdf4” format. Can anyone tell what happened?