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

Trips that exceed a specified maxHours limit #2332

demory opened this Issue Sep 1, 2016 · 2 comments


None yet
3 participants

demory commented Sep 1, 2016

TriMet has found cases where trips are being returned that exceed a specified maxHours limit. For example:,-122.59346&toPlace=SW+Boones+and+Apache::45.372875,-122.76969&time=6:30pm&date=08-31-2016

Options two and three have a total duration of 41140 sec, well over the specified 6-hour limit.

@fpurcell fpurcell added this to the 1.1.0 milestone Sep 15, 2016


This comment has been minimized.


demory commented Oct 6, 2016

We determined that this is happening because maxHours was only ever implemented to the 0.10.x branch. Needs to be implemented in the current OTP code as well.

demory added a commit that referenced this issue Oct 12, 2016


This comment has been minimized.

mg-code commented Jan 11, 2017

maxTransferTime might be useful.
Sometimes it is okay to ride a bus for 8 hours for longer distances, but not okay to ride a bus for 30 minutes, then wait for 7 hours overnight and ride for 30 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment