-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GTFS Fares v2] Add rider_categories.txt #511
base: master
Are you sure you want to change the base?
Conversation
Quick updates:
|
Nice. Sound Transit has a semi-complete production of Fares v2 data that we'll be making fully complete in the next couple months. We can add rider_categories.txt as well since it applies to several of our fare products. |
Hi @tzujenchanmbd, the SF Bay Area Regional Feed includes a
|
@tzujenchanmbd yes, we can add the Also in case it's useful to others, we maintain a list of the Fares-v2 tables in the SF Bay Area Regional Feed, which we can update as the remaining proposed tables are adopted: https://www.interline.io/blog/mtc-regional-gtfs-feed-fares-updates/#gtfs-fares-v2-base-implementation-and-future-additions-to-the-specification |
The
rider_categories.txt
file is part of the GTFS-Fares v2 proposal, aimed at modeling rider categories that are eligible for certain fares.In the August and September meetings, the working group reached the following consensus:
rider_category_id
will be referenced infare_products.txt
min_age
andmax_age
fields for nowChanges in this PR
rider_categories.txt
filefare_products.rider_category_id
field and update the primary key offare_products.txt
fare_product_id
For previous discussions please see the working group meeting note
Comments and questions welcome!
Side note: Currently the fares working group is primarily discussing fare use cases. However, in the future this file may be used for use cases such as service eligibility.