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

[weather] openweathermap One Call 2.5 will be finally closed in June 2024 #3424

Open
khassel opened this issue Apr 17, 2024 · 2 comments
Open

Comments

@khassel
Copy link
Collaborator

khassel commented Apr 17, 2024

via mail:

"Dear OpenWeather user,

We would like to inform you about our plans to complete the migration from One Call 2.5 to One Call 3.0 that started 2 years ago. In line with this, access to One Call 2.5 will be finally closed in June 2024.

One Call 3.0 provides you with significantly advanced business-demanded features such as a minute forecast for 1 hour, 4 days forecast for any timestamp, a daily forecast for 8 days, including a human-readable summary, historical data (45-year archive) for timestamps, and with daily aggregation, 1.5-year long-term forecast with daily aggregation, and others."

We have still 2.5 in the provider file as default, must be changed to 3.0.

@mlcampbe
Copy link

I too got the email about the change to the onecall 3.0 and have tried to do some testing and it seems that we need to change the apiVersion from 2.5 to 3.0 but we also need to change the weatherEndpoint from /weather to /onecall (at least when using the default type=current).

For example, this call works fine:
curl -v "https://api.openweathermap.org/data/3.0/onecall?lat=xxx&lon=yy&appid=zzzz"

but this fails with a 404 error:
curl -v "https://api.openweathermap.org/data/3.0/weather/?lat=xxx&lon=yy&appid=zzzz"

Is this correct in that we need to change both the apiVersion and the weatherEndpoint parameters to use the 3.0 calls after June?

@sdetweil
Copy link
Collaborator

this issue says, we need to change to fix the coming api change. whatever it takes.

you have pointed out another thing to address.

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

3 participants