Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt ERA5 cmoriser for new CDS API format #3790

Open
alistairsellar opened this issue Oct 23, 2024 · 1 comment
Open

Adapt ERA5 cmoriser for new CDS API format #3790

alistairsellar opened this issue Oct 23, 2024 · 1 comment

Comments

@alistairsellar
Copy link
Contributor

alistairsellar commented Oct 23, 2024

Is your feature request related to a problem? Please describe.
ECMWF have updated the grib-to-netCDF converter used in downloading the netCDF version of ERA5 (and presumably also for ERA-Interim): https://confluence.ecmwf.int/display/CKB/GRIB+to+netCDF+conversion+on+new+CDS+and+ADS+systems.
This has changed the format of the ERA5 files, and the ESMValTool ERA5 on-the-fly cmoriser might need to be updated to work with the new format. I say might because there are a couple of problems with the format that I've requested be fixed at source:

In the meantime, here is some guidance to ESMValTool users downloading ERA5 data:

  • Use ECMWF's legacy converter.
  • Avoid the last few months of the timeseries. My understanding (though I've not fully investigated) is that that if the data overlaps with the near-real-time "initial release" period (see https://climate.copernicus.eu/climate-reanalysis) then it adds an additional coordinate which breaks the ESMValTool cmorisor, and also will double the size of your netCDF file.

@ESMValGroup/obs-maintainers, where do you think would be the appropriate places to document the above interim advice? Is an issue the best place for advice that might evolve quite quickly?

Would you be able to help out?
Yes

@bettina-gier
Copy link
Contributor

This also relates to #3750.

I would personally wait a little before adapting to the new CDS since there are still a few things that might change. We could potentially look into pinning one of these issues so it doesn't get drowned in between other things. That might also remind us to keep it more up-to-date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants