-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use UTC everywhere #8
Comments
I completely agree with this. Timezones should only be dealt with on the client side. This also clears up issues with DST for everything after the initial parse of GTFS source. The GTFS spec says:
Timetable can easily parse the GTFS source with this strategy, converting all times to UTC for everything downstream to use. I remember we said at some point that agency information would be available through |
So it seems like generally a good idea to use UTC on the backend, but I have a couple particular reasons:
Time.now
to determine whether to request real-time departures, so the timezone of the server matters. This could be a problem, since one host runs multiple agencies, but the containers server components run in have their own timezone. A container's timezone defaults to UTC.I think that the necessary steps would be to:
agency.rb
to know the agency's timezone. I imagine some future real-time applications will need to know the local agency time.The text was updated successfully, but these errors were encountered: