-
Notifications
You must be signed in to change notification settings - Fork 101
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
from_stop_id and to_stop_id not required for transfer_type 4 & 5 #1621
Comments
Thanks for opening your first issue in this project! If you haven't already, you can join our slack and join the #gtfs-validators channel to meet our awesome community. Come say hi 👋! |
Hi @brodyFlannigan, thanks for your contribution. PR #1772 addresses this issue. There is also a great discussion (google/transit#455) regarding clarifying the rule in the spec. We plan to have this fix in the next release(date TBD, sometime this summer). Please feel free to look over the PR and add your comments. |
Describe the bug
Hi!
The GTFS specification does not explicitly require that
from_stop_id
andto_stop_id
be provided for records intransfers.txt
with atransfer_type
of4
or5
. However, the validator reports amissing_required_field
error if these two fields are not provided.Steps/Code to Reproduce
Using the online GTFS validator, validate this file:
transcollines-qc-ca-fares-transfers.zip
(Ignore the other errors about translations and shape distances, those are known and being worked on)
Expected Results
Validator should not report a
missing_required_field
error iffrom_stop_id
andto_stop_id
are not provided intransfers.txt
iftransfer_type
=4
or5
Actual Results
Validator returns a
missing_required_field
error iffrom_stop_id
andto_stop_id
are not provided intransfers.txt
iftransfer_type
=4
or5
Screenshots
No response
Files used
transcollines-qc-ca-fares-transfers.zip
(Ignore other errors about translations and shape distances, those are known and are being worked on)
Validator version
4.2.1-SNAPSHOT
Operating system
(Web version of validator)
Java version
No response
Additional notes
No response
The text was updated successfully, but these errors were encountered: