[GTFS Fares v2] Add rider_categories.txt#511
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 rider_category_id,rider_category_name,min_age,max_age,eligibility_url
adult,Adult (18-65),18,65,
adult-2,Adult,,,
youth,Youth (5-18),5,18,
youth-2,Youth (6-18),6,18,
child,Child (Under 5),0,4,
child-2,Child (Under 6),0,5,
smd,Senior,65,,
smd,Person with disabilities,,,
smd,Medicare recipient,,,
smdy,Senior,65,,
smdy,Person with disabilities,,,
smdy,Medicare recipient,,,
smdy,Youth,5,18,
AM:discount,Capitol Corridor (Disabled),,,https://www.capitolcorridor.org/disabled-passenger-discount/
AM:discount,Capitol Corridor (Senior),62,,https://www.capitolcorridor.org/senior-discounts/
MA:muir-youth,Marin Transit (15 and under),,15,
SR:veteran,Santa Rosa CityBus (U.S. Veteran),,,https://srcity.org/1658/Fares
ST:super-senior,SolTrans (Super Senior),80,,
AF:senior,Angel Island Tiburon Ferry (Senior),65,,
AF:child,Angel Island Tiburon Ferry (Child),6,12,
AF:small-child,Angel Island Tiburon Ferry (Small Child),3,5,
AF:toddler,Angel Island Tiburon Ferry (Toddler),,2,
AF:adult,Angel Island Tiburon Ferry (Adult),13,64, |
|
@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 |
|
Support for |
|
We have at least one producer: TriMet. Their feed could be downloaded at https://developer.trimet.org/GTFS.shtml As per the GTFS amendment process, the requirements to open a vote are met. Voting ends on 2025-02-13 at 23:59:59 UTC. |
|
+1 TriMet! |
C-TRAN is also publishing rider_categories.txt now. |
|
+1 Caltrans. 🚌 |
|
+1 from @interline-io |
|
+1 from Transit |
|
+1 from Aubin |
|
+1 from the @mbta |
|
+1 Trillium! |
|
The vote passed on 2025-02-13 at 23:59:59 UTC. 7 votes in favour and no votes against. Votes came from: Thank you to everyone who participated! |
|
As an update, validation rules for rider categories have been added to the Canonical GTFS Schedule Validator release this week: https://github.com/MobilityData/gtfs-validator/releases/tag/v7.0.0 |
![transitapp_trimet_default_rider_cat]](https://private-user-images.githubusercontent.com/20569869/407454588-60068dbf-a31a-4842-ac08-2609c3f9c19c.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzUwMjQyNDYsIm5iZiI6MTc3NTAyMzk0NiwicGF0aCI6Ii8yMDU2OTg2OS80MDc0NTQ1ODgtNjAwNjhkYmYtYTMxYS00ODQyLWFjMDgtMjYwOWMzZjljMTljLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA0MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNDAxVDA2MTIyNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM4NzZhZWNmMjIwYmU0YTE3ZjI1ZTRmNmUzMDhlZmQ1NDcxNTNkNDFjZDg3MmMxMTQ0MDc0NzFjOTg4YjlhZmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Vu5uCz7mqrK9YTbFO9NQoFTHlAiHltF74dNQXa052Ok)
The
rider_categories.txtfile 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_idwill be referenced infare_products.txtmin_ageandmax_agefields for nowChanges in this PR
rider_categories.txtfilefare_products.rider_category_idfield and update the primary key offare_products.txtfare_product_idFor 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.