You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present for the itinerary start and end times to be presented correctly to the user, otpr needs to be running in the same time zone as the OTP graph that is being queried.
This is because otp_get_times() uses the R as.POSIXct() function to convert from the epoch time returned by OTP. By default, as.POSIXct will assume the current system time zone (i.e. on the system that is running otpr).
To fix this probably need:
Ability to specify the timezone of the graph - perhaps this should be done as part of otp_connect() ?
OTP handling of Time Zones is a bit opaque and a current discussion topic amongst the key developers. What I am understanding is that OTP is only intended to work across a single time zone and that this is picked up from the agency GTFS file. Needs further investigation. Therefore as there is a single graph per router, setting it as part of otp_connect() may make sense?
The text was updated successfully, but these errors were encountered:
At present for the itinerary start and end times to be presented correctly to the user, otpr needs to be running in the same time zone as the OTP graph that is being queried.
This is because
otp_get_times()
uses the Ras.POSIXct()
function to convert from the epoch time returned by OTP. By default, as.POSIXct will assume the current system time zone (i.e. on the system that is running otpr).To fix this probably need:
otp_connect()
?otp_connect()
may make sense?The text was updated successfully, but these errors were encountered: