-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
So it seems like generally a good idea to use UTC on the backend, but I have a couple particular reasons:
- Since GTFS is set to the agency's timezone, clients are expected to query in the "right timezone" of the agency. This works fine if the client is in the same region, but breaks if the client is outside the agency's timezone. Me checking BART in Indiana returns different results than someone checking it in California.
- Providence uses
Time.nowto 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:
- translate stop times in Timetable from the the agency timezone to UTC
- configure clients / providence to use UTC for all time-related queries
- (future-proofing) configure providence's
agency.rbto know the agency's timezone. I imagine some future real-time applications will need to know the local agency time. - clarify the request timezone in this repo
faultyserver