Add in-seat transfers to transfers.txt #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The primary change in this pull request will be effective in the MBTA's production GTFS file on Tuesday, September 27, 2022. This follows from the recent adoption of google/transit#303 into the base GTFS specification.
Summary:
transfer_typeof4is introduced to designate pairs of trips on the same vehicle between which riders are permitted to remain aboard. At this time,block_idwill remain in use within trips.txt linking trips on the same vehicle regardless of whether riders are permitted to remain aboard.from_trip_idandto_trip_idare now officially part of the base GTFS specification, and are no longer experimental fields.