Require from_stop_id and to_stop_id in recommended transfer point transfers (empty or 0) #591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In
transfers.txt, requirefrom_stop_idandto_stop_idwhentransfer_type = 0or is empty (recommended transfer point).This affected requirement rules, therefore it's a non-functional change. It requires a discussion period, a review period and a vote.
Describe the Problem
In
transfers.txt, whentransfer_type = 0or is empty, it means that it is a recommended transfer point between routes, which should include afrom_stop_idandto_stop_id.However, the spec currently only requires
from_stop_idandto_stop_idwhentransfer_type =1, 2 or 3The issue was raised by a community member in the #gtfs Slack channel (thread): "from_stop_id and to_stop_id are "Required if transfer_type is 1, 2, or 3", but aren't they also required if transfer_type=0 or empty?"
Type of change
GTFS Schedule
GTFS Realtime
Proposed Discussion Period
We want to leave the discussion period open until after the holidays to accommodate holiday schedules and to make sure the community has an eye on this. We intend to start a one-week review period and the vote mid-January.
Therefore, we propose a discussion period of 6 weeks (too accommodate the holidays), the discussion period ends on 9 January 2026 at 23:59:59 UTC.
Proposal Update Tracker
Checklist