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

Rejection of continuous stopping in flex trips is overly strict #6230

Open
leonardehrenfried opened this issue Nov 5, 2024 · 0 comments · May be fixed by #6231
Open

Rejection of continuous stopping in flex trips is overly strict #6230

leonardehrenfried opened this issue Nov 5, 2024 · 0 comments · May be fixed by #6231
Labels
GTFS Related to import of GTFS data TriMet

Comments

@leonardehrenfried
Copy link
Member

OTP currently rejects any flex trips have one or more stop times that contain continuous stopping values. This was originally added because the combination of flex and continuous was deemed to be invalid: MobilityData/gtfs-flex#70

However, a closer reading of the specification shows that it's not invalid to mix them in a single trip - it's only invalid to mix them in the very same stop_time:

continuous_drop_off [is] forbidden if start_pickup_drop_off_window or end_pickup_drop_off_window are defined.

https://github.com/google/transit/blob/master/gtfs/spec/en/reference.md#stop_timestxt

Reported by @m-mcqueen. cc @fpurcell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GTFS Related to import of GTFS data TriMet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant