Maybe uses wrong base date when parsing Buienradar time #3
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: paul/sinoptik#3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The time in the rain text output is interpreted within the local date. However, when running this on a machine that is not in the Europe/Amsterdam time zone, the current date may different from the date in said time zone.
With the
chrono-tz
crate it should possible to take the date from the Europe/Amsterdam time zone and then convert it to UTC?Buienradar maps (pollen and UVI) are already in UTC: forcast for 2022-02-18 20:00 has filename 02202181900__820x988_False_False_False_0_24_0_0_0.png
Luchtmeetnet also uses UTC in its forecasts.
The only service that does not use UTC is the Buienradar API.
Isn't it easier to convert the Buienradar API timestamp to UTC and use UTC throughout the rest of the application?
Also, timestamps can cross the day limit, this also goes wrong. Or it can even go backward because it sometimes provides older forecasts.
Yes, but this is talking about the conversion process. You have to start with local time first and now it uses the server's local time instead of Europa/Amsterdams time (which Buienradar uses in its output).