New Beta API still does not work but no mitigation strategy seems in place

In the last couple of weeks, we experienced different types of issues with the new (beta) API for ERA5 (Reanalysis and Land), for instance, increased latency and errors in downloading specific data that are perfectly fine if downloaded with the old API.

Yet, this page insists on the notion that “the old API will be decommissioned on Sep 26, if you are a legacy user, switch to the new one”, completely missing the point that it is not the user who does not want to switch, it is the new API that still does not work properly.

In spite of the tone of Headlines in this page, the fact that the adoption of the new API might not be as widespread as expected is a responsibility of the Data Provider, and not of the user.

Is there a way to bring this misconception to the attention of the decision makers and change the terms of the Headline?

Thank you very much

3 Likes