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

Time Zones: UTC offset vs. named time zones #30

Open
Namoshek opened this issue Oct 13, 2020 · 1 comment
Open

Time Zones: UTC offset vs. named time zones #30

Namoshek opened this issue Oct 13, 2020 · 1 comment

Comments

@Namoshek
Copy link
Contributor

Currently, the time zone of an EVSE can be given in the address object in form of a UTC offset, e.g. UTC+02:00. Especially in Central Europe, where most countries are using a different UTC offset for summer time, this comes with the drawback that published data becomes inaccurate the moment we change our clocks.

I therefore suggest switching to named time zones as they can be found in the list of tz database time zones which is published by IANA.

Such an API change could in theory be (mostly) backwards and forwards compatible, since for most countries there is only one timezone and a simple mapping from country to time zone and vice versa is already sufficient.

@Namoshek Namoshek changed the title Time Zones: UTC offset vs. Time Zones: UTC offset vs. named time zones Oct 13, 2020
@erkkiat
Copy link

erkkiat commented Oct 6, 2024

Please advise how we can ensure that a driver knows if a location is open or closed, if summer/winter time is not considered. @mhassan-hubject

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants