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
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
Thanks for the report @alankessler! Off the top of my head I'm guessing that the tool doesn't check/respect the GTFS agency.txt agency_timezone field when loading the GTFS data.
FWIW, we developed the tool in the Eastern timezone, and I think the bulk of testing occurred within DST
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I imported a week of captured Trimet data and ran it against the tool. The output looks like:
(d = scheduled_deviation/60000 to get minutes)
The cluster around 60 minutes makes me suspect that there's a timezone or DST issue.
The text was updated successfully, but these errors were encountered: