feat: Add Fares v2 page #89
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,71 @@ | ||
| <a class="pencil-link" href="https://github.com/MobilityData/gtfs.org/edit/main/docs/extensions/fare-extension.md" title="Edit this page" target="_blank"> | ||
| <svg class="pencil" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4v-2m10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1 2.1 2.1Z"></path></svg> | ||
| </a> | ||
|
|
||
| # GTFS-Fares v2 | ||
|
|
||
| Fares v2 is a GTFS Schedule extension project that aims to address the limitations of <a href="/schedule/examples/fares-v1">Fares v1</a>. | ||
|
|
||
| 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 payment options (e.g bank card and credit card) | ||
| - 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 <a href="/schedule/examples/fares-v2" target="_blank">examples here</a> 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. | ||
|
|
||
| <a class="button no-icon" href="https://share.mobilitydata.org/gtfs-fares-v2" target="_blank">See the full proposal</a> | ||
|
|
||
| ## In Progress Fares v2 Work | ||
|
|
||
| The GTFS community is currently working on finalizing the <a href="https://share.mobilitydata.org/fare-containers-to-fare-payment-types-proposal" target="_blank">fare_payment_options.txt (formerly fare_containers.txt)</a> proposal. | ||
|
|
||
| Items currently in discussion include: | ||
|
|
||
| - Creating a fare_payment_options_groups.txt file | ||
| - Aligning on what types should be included in the enumeration for `fare_payment_option_type` | ||
|
|
||
| <a class="button no-icon" href=https://share.mobilitydata.org/slack>Join #gtfs-fares on Slack</a><a class="button no-icon" href=https://www.eventbrite.ca/e/specifications-discussions-gtfs-fares-v2-monthly-meetings-tickets-522966225057>See the meeting schedule</a><a class="button no-icon" href=https://docs.google.com/document/d/1d3g5bMXupdElCKrdv6rhFNN11mrQgEk-ibA7wdqVLTU/edit>See meeting notes</a> | ||
|
|
||
|
|
||
| ## First Adopters | ||
|
|
||
| 🎉 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: <a href="https://www.interline.io/" target="_blank">Interline</a>, <a href="https://www.mta.maryland.gov/developer-resources" target="_blank">Maryland Department of Transportation</a>, <a href="https://dot.ca.gov/cal-itp/cal-itp-gtfs" target="_blank">Cal-ITP</a> | ||
| - Consumer: <a href="https://transitapp.com/" target="_blank">Transit</a> | ||
|
|
||
| For the fare payment options feature currently under discussion, first adopters are | ||
|
|
||
| - Producer: <a href="https://www.interline.io/" target="_blank">Interline</a> | ||
| - Consumer: <a href="https://www.apple.com/">Apple</a>, <a href="https://transitapp.com/" target="_blank">Transit</a> | ||
|
|
||
| <a class="button no-icon" href="https://share.mobilitydata.org/gtfs-fares-v2" target="_blank">See who’s using Fares v2 files and fields</a> | ||
|
|
||
| ## Proposals Currently Under Discussion | ||
|
|
||
| <iframe src="https://portal.productboard.com/rhk8dbtic1iqakfznucry448" frameborder="0" width="100%", style="min-height:600px;"></iframe> | ||
|
There was a problem hiding this comment. This is great! If so, where is the best place to see the prioritized backlog? The next item we will be working on is the Variable pricing feature. There was a problem hiding this comment. @isabelle-dr Right now that information is in our roadmap on the website. We could merge all this info into the main portal and just add a "spec proposal triage" column so everything is in 1 place. |
||
|
|
||
| ## History | ||
emmambd marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| - **2017**: Industry research and data modelling | ||
| - **October 2021**: <a href="https://github.com/google/transit/pull/286#issue-1026848880" target="_blank">Base implementation drafted and shared</a> | ||
| - **December 2021**: <a href="https://github.com/google/transit/pull/286#issuecomment-990258396" target="_blank">Open vote #1 → did not pass</a> | ||
| - **March 2022**: <a href="https://github.com/google/transit/pull/286#issuecomment-1080716109" target="_blank">Open vote #2 → did not pass</a> | ||
| - **May 2022**: <a href="https://github.com/google/transit/pull/286#issuecomment-1121392932" target="_blank">Open vote #3 → passed</a> | ||
| - **August 2022**: <a href="https://github.com/google/transit/issues/341" target="_blank">Community discussion on next phase of Fares v2 begins</a> | ||
| - **December 2022**: <a href="https://github.com/google/transit/issues/341#issuecomment-1339947915" target="_blank">Community identifies stack ranked order of features to prioritize iterations</a> | ||
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this info is a little duplicative of the table below. From a maintainability standpoint, having only one place to update what we are currently working on might be easier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hoping the "what we are currently working on" will get updated more often in 2023 🙈
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The main value of this section to me is having a few sentences that someone can skim for a general update of
(and not having to scrounge through GitHub to find that update in a specific PR or issue).
It serves a different purpose than a list of proposals people have to read through on ProductBoard, since that's more for people who really want to get into the details. I imagine us updating this section every month or two. @isabelle-dr does that make sense to you or is there an alternative approach you'd prefer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I understand better. Sounds good then.
Can you change the name to "fare container updated proposal"?
The name is back on the table 🙈