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

GTFS import: Frequencies are not handled properly #728

Closed
tahini opened this issue Oct 4, 2023 · 0 comments · Fixed by #729
Closed

GTFS import: Frequencies are not handled properly #728

tahini opened this issue Oct 4, 2023 · 0 comments · Fixed by #729
Labels
bug Something isn't working data import

Comments

@tahini
Copy link
Collaborator

tahini commented Oct 4, 2023

From the GTFS specification (https://gtfs.org/schedule/best-practices/#frequenciestxt)

Actual stop times are ignored for trips referenced by frequencies.txt;  only travel time intervals between stops are significant for  frequency-based trips. For clarity/human readability, it is recommended  that the first stop time of a trip referenced in frequencies.txt should begin at 00:00:00 (first arrival_time value of 00:00:00).

It is not how we handle this, we prioritise stop times! This is why the Santiago GTFS fails to import (https://datos.gob.cl/dataset/33245)

@tahini tahini added bug Something isn't working data import labels Oct 4, 2023
tahini added a commit to tahini/transition that referenced this issue Oct 5, 2023
fixes chairemobilite#728

When frequencies are specified for a trip, the specified stop times
should be ignored and simply start/end according to frequencies
information.
tahini added a commit that referenced this issue Oct 5, 2023
fixes #728

When frequencies are specified for a trip, the specified stop times
should be ignored and simply start/end according to frequencies
information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working data import
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant