-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Investigate alternative response layouts #143
Comments
Hey, it might be helpful to see the layout from the bund.dev proxy: https://dwd.api.proxy.bund.dev/v30/stationOverviewExtended?stationIds=10865 |
@jdemaeyer any news on this topic? |
I would find aggregated values great too, but am I misunderstanding something? First of all, this is just a loop for the included days. I just take the first 24 hours in an array and calculate min and max. Then it goes on the next 24 hours. I do this as often as the days are needed. The function can be used again and again or are the projects so different? |
Yes, it is not difficult to do it manually :) |
With alerts (#106) and daily aggregates (#117, #119), we'll be hitting the limits of our current response layout, where
weather
is an array of hourly records.We can possibly squeeze these new data structures into the current response layout, keeping the current key
weather
instead of the more adequatehourly
(but can we stick tosources
being an array of sources, given that the sources will be different fordaily
andalerts
?):But we could also seize the opportunity to start from scratch, maybe using the layout of OpenWeatherMap's One Call API:
or Dark Sky's layout:
The text was updated successfully, but these errors were encountered: