[GTFS-Fares v2] Multi-leg Transfer: Same product/media transfer behavior #420
Labels
Extension: GTFS-Fares
Issues and Pull Requests that focus on GTFS-Fares Extension
Status: Pull Request Created
Issues that have been transferred to the Pull Request stage.
Status: Stale
Issues and Pull Requests that have remained inactive for 30 calendar days or more.
Use Case
Problem to solve
The current Fares v2 spec does not have mechanism for differentiating the above use cases or provide explanation within its description, leading to potential ambiguity. This is especially relevant for certain transit systems, such as STM, that operate 100% with a ticket-based system. Transit firstly posed the question, "Should fare transfers require that the same fare product is used on both legs?" Subsequently, Google also raised the following questions in this transfer semantics document [this issue only discusses the first three questions in this document]:
fare_transfer_rules.txt
, is it required that both legs have the same fare media type?fare_transfer_rules.txt
can match a single leg-to-leg transfer?Proposed solution
On October 24th, the working group reached a consensus to clarify these questions, leaning towards a default behavior mechanism to minimize any potential breaking changes. Based on this consensus, we drafted this proposal that aims to resolve the above 3 questions.
In the November discussion, the working group is currently leaning towards option 1 proposed, which involves adding
fare_product_behavior
,fare_media_behavior
, andfilter_fare_product_id
tofare_transfer_rules
. This option is favored as this mechanism appears to be more like the attributes offare_transfer_rules
(with option 2 being an alternative).We'd love to see any feedback on this proposal or any related use cases. Please feel free to share any thoughts on this issue.
The text was updated successfully, but these errors were encountered: