-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
deprecated dataset in Geosphere, update needed in endpoint #1286
Comments
By the way, I would love to help contributing to updating this if you are alright with it :) |
Dear @bluearrow98 , thanks for reporting the change! It would be great if you setup a PR and I'll guarantee quick merge! Do you need assistance? |
Yes, I am working on it! All the parameters need to be updated as well unfortunately and this is causing some problems. Currently, debugging it. I'll notify you once I update it :) |
If you have some pain points that really had troubled you, please let me know and I'll try to add that to the docs! |
Just set up a PR. Noticed that the request function was setting the start_date to be default even when a user gives one (but no end_date). Fixed that as well. Also, it is painful to see such hardcoded parameter for each resolution haha. I plan to take this up as a small project to automate this somehow ;) |
Describe the bug
Geosphere recently seemed to have updated their dataset resource. I was trying to retrieve the snow depth data in a certain region, however it is shown missing when I access through wetterdienst. On comparing the data directly accessing from Geopshere API, I discovered that the resource used in wetterdienst is deprecated.
To Reproduce
Steps to reproduce the behavior:
Request the data:
The output I get:
Expected behavior
The data is available. But Geosphere seem to have updated their dataset resource. You can find all the list of deprecated resources here: https://dataset.api.hub.geosphere.at/v1/docs/user-guide/resource.html. There is also alternative endpoint name suggested for all those resources.
The text was updated successfully, but these errors were encountered: