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

Potential shift from trip_id to stop path for historical travel times lookup #247

Open
rbarcham opened this issue Nov 12, 2021 · 0 comments · May be fixed by #255
Open

Potential shift from trip_id to stop path for historical travel times lookup #247

rbarcham opened this issue Nov 12, 2021 · 0 comments · May be fixed by #255

Comments

@rbarcham
Copy link

Is your enhancement request to replace an existing functionality within TheTransitClock?
Yes, potential to enhance/replace current understanding of historical travel times on a trip basis.

Is your enhancement request related to a problem? Please describe.
Historical travel times based on trip_id are brittle to changes in trip_id - there are implications not only for inconsistent GTFS, but more importantly for service changes/disruptions.

Describe the solution you'd like
Could potentially replace cache keyed off trip_id with something was route + stop path based; would also need time bucket component.

Describe alternatives you've considered
Various other approaches possible.

Additional context
May require and/or be linked to additional cache performance improvements.

Example datasets
TBD

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