Maybe uses wrong base date when parsing Buienradar time #3

Closed
opened 2022-02-13 16:59:22 +01:00 by paul · 4 comments
Owner

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.

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.
paul added the
bug
label 2022-02-13 16:59:22 +01:00
Author
Owner

With the chrono-tz crate it should possible to take the date from the Europe/Amsterdam time zone and then convert it to UTC?

With the `chrono-tz` crate it should possible to take the date from the Europe/Amsterdam time zone and then convert it to UTC?
Collaborator

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?

Buienradar maps (pollen and UVI) are already in UTC: forcast for 2022-02-18 20:00 has filename 0220218**1900**__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?
Author
Owner

Also, timestamps can cross the day limit, this also goes wrong. Or it can even go backward because it sometimes provides older forecasts.

Also, timestamps can cross the day limit, this also goes wrong. Or it can even go backward because it sometimes provides older forecasts.
paul self-assigned this 2022-02-19 15:39:30 +01:00
Author
Owner

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?

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).

> Buienradar maps (pollen and UVI) are already in UTC: forcast for 2022-02-18 20:00 has filename 0220218**1900**__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? 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).
paul closed this issue 2022-02-20 17:42:18 +01:00
paul added this to the version 0.1.0 milestone 2022-03-14 17:03:50 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: paul/sinoptik#3
No description provided.