-
Notifications
You must be signed in to change notification settings - Fork 213
Comments
[GTFS Fares v2] Add nonconsecutive_transfer_allowed field and clarify fare_transfer_type#498
Open
tzujenchanmbd wants to merge 4 commits intogoogle:master from
Open
[GTFS Fares v2] Add nonconsecutive_transfer_allowed field and clarify fare_transfer_type #498tzujenchanmbd wants to merge 4 commits intogoogle:master from
tzujenchanmbd wants to merge 4 commits intogoogle:master from
Conversation
@tzujenchanmbd
tzujenchanmbd
added
GTFS-Fares
Issues and Pull Requests that focus on GTFS-Fares Extension
Change type: Functional
Refers to modifications that significantly affect specification functionalities.
Support: Needs Review
labels
Sep 18, 2024
This pull request has been automatically marked as stale because of lack of recent activity. It may be closed manually after one month of inactivity. Thank you for your contributions.
@github-actions
github-actions
bot
added
the
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
label
Feb 4, 2025
Contributor
jfabi
commented
Feb 5, 2025
Keep open (we may have some new interest on this at the @mbta).
@eliasmbd
eliasmbd
added
Discussion Period
The community engages in conversations to help refine and develop the proposal.
and removed
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
labels
Feb 5, 2025
This pull request has been automatically marked as stale because of lack of recent activity. It may be closed manually after one month of inactivity. Thank you for your contributions.
@github-actions
github-actions
bot
added
the
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
label
May 7, 2025
@Sergiodero
Sergiodero
added
the
Former Governance Applies
This proposal is subject to the former governance process which predates July 7, 2025.
label
Jul 7, 2025
@github-actions
github-actions
bot
removed
the
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
label
Jul 8, 2025
This pull request has been automatically marked as stale because of lack of recent activity. It may be closed manually after one month of inactivity. Thank you for your contributions.
@github-actions
github-actions
bot
added
the
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
label
Oct 8, 2025
Collaborator
Author
tzujenchanmbd
commented
Nov 14, 2025
not stale
@github-actions
github-actions
bot
removed
the
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
label
Nov 15, 2025
This file contains hidden or 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.
Uh oh!
There was an error while loading. Please reload this page.
Changes in this PR:
nonconsecutive-transfer-allowedfield infare_transfer_rules.txtto indicate whether the transfer rule is allowed to apply to non-consecutive transfers.fare_transfer_typein a journey with multiple transfers, when the consumer calculates the total processed cost of the preceding leg(s) and transfer(s), thefare_transfer_typeof the preceding legs must be considered. Additionally, include an explanation regarding non-consecutive transfers.For more details please refer to this proposal
For previous discussions in the working group please see the working group meeting note (Jul, Aug)
Please help review this PR. Comments/questions welcome!