Fares v2 is a GTFS Schedule extension project that aims to address the limitations of Fares v1.
The main concepts that Fares v2 plans to represent are
- Fare products (e.g tickets and passes)
- Rider categories (e.g seniors and children)
- Fare media (e.g transit pass, paper tickets, contactless bank cards)
- Fare capping
These concepts will allow data producers to model zone-based, time-dependent, and inter-agency fares. This extension project is being adopted in iterations.
Currently, the adopted base implementation of Fares v2 works for the following use cases:
- Defining a transit fare
- Describing service locations in the same fare zone
- Creating rules for single leg journeys
- Creating rules for transfers
You can see examples here that show what can be modelled using the adopted Fares v2 base implementation.
Producers may implement Fares v2 in the same dataset with Fares v1, since there is no technical conflict between the two. Consumers can choose which version to use independent of the other. With adoption and sufficient endorsement of Fares v2, Fares v1 may be deprecated in the future.
In Progress Fares v2 Work¶
The fare media (formerly fare containers) proposal has passed and been officially adopted in the spec!
The Fares v2 working meetings will now focus on modelling and adopting time variable fares.
Join #gtfs-fares on SlackSee the meeting scheduleSee meeting notes
🎉 Shoutout to Fares v2 first adopters! At least 1 data producer and 1 consumer must commit to implementing an experimental feature before a public vote is opened to add it to the official specification. These organizations invest a large amount of time and energy into experimental changes to make sure that GTFS continues to evolve.
For the adopted base implementation, first adopters were
- Producers: Interline, Maryland Department of Transportation, Cal-ITP
- Consumer: Transit
For the fare media feature currently under discussion, first adopters are
Request a changeAdd your organization (consumers)Add your organization (producers)
Fares v2 Features Under Discussion¶
- 2017: Industry research and data modelling
- October 2021: Base implementation drafted and shared
- December 2021: Open vote #1 → did not pass
- March 2022: Open vote #2 → did not pass
- May 2022: Open vote #3 → passed
- August 2022: Community discussion on next phase of Fares v2 begins
- November 2022: Fare media draft pull request opened for feedback
- December 2022: Community identifies stack ranked order of features to prioritize iterations
- March 2023: Fare media vote passes