-
Notifications
You must be signed in to change notification settings - Fork 28
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
Migration CDS/ADS -- anticipated package failure #128
Comments
Oof.. annoying. With luck, a lot of the package code can be reused and adapted. It would be nice to have a date, and also a test server to prepare changes.. |
There is nothing there to work with I'm afraid. Hope this won't be to much of a change. I'll keep an eye out for a press release, but with no set deadline this is rather difficult. Ping me here or on Mastodon should you see something on an update. |
Beta API endpoint: https://cds-beta.climate.copernicus.eu/api - to validate functionality (will start new branch) |
See #131 - waiting for press release for roll-out |
Addin needs to be accomodated for the new API format specs on the CDS (beta) website - separate entry for transition (no set date on depreciation of the old CDS and or website migration). NEWdataset = "reanalysis-era5-land" OLDc.retrieve( |
This spring the whole CDS/ADS framework will be redone. Aside from this very brief communication:
https://confluence.ecmwf.int/display/CKB/Please+read%3A+CDS+and+ADS+migrating+to+new+infrastructure%3A+Common+Data+Store+%28CDS%29+Engine
There is little information on the structure and or general setup of the new API. There is no way to anticipate changes, which seem to be profound in some cases (full reset accounts). This might break the package profoundly.
@eliocamp
The text was updated successfully, but these errors were encountered: