Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
February 2025 - Rider Categories, Adopted!
15 views
Skip to first unread message
GTFS Digest
Mar 6, 2025, 3:28:26āÆPMMar 6
to GTFS Digest
.png?part=0.1&view=1)
The GTFS Digest is a resource generated monthly byĀ MobilityDataĀ providing an overview of developments on GTFS.
Ā
We really value your feedback and would like to know how we did. We invite you to fill outĀ this formĀ and help us achieve the full potential of this tool.Ā
We really value your feedback and would like to know how we did. We invite you to fill outĀ this formĀ and help us achieve the full potential of this tool.Ā
š
Contributor Shoutouts
Max Buchholz
Posted his first PR fixing some typos in the proto file for GTFS Realtime. Thanks for your contribution!
Felix GĆ¼ndling & Scott Berkley
Welcome to the GTFS community and thank you for sharing your questions and insights about GTFS Fares.
Wojciech Kulesza
Thanks for taking such a big interest in Fares and joining the Working Group Meeting.
Jerome Le Lan & lolpro11
Shoutout for posting your first issues on the GTFS Github Repo. Your contributions are appreciated!Ā
Posted his first PR fixing some typos in the proto file for GTFS Realtime. Thanks for your contribution!
Felix GĆ¼ndling & Scott Berkley
Welcome to the GTFS community and thank you for sharing your questions and insights about GTFS Fares.
Wojciech Kulesza
Thanks for taking such a big interest in Fares and joining the Working Group Meeting.
Jerome Le Lan & lolpro11
Shoutout for posting your first issues on the GTFS Github Repo. Your contributions are appreciated!Ā
š³ļø Currently Voting
Clarification on continuous pickup/dropoff value and field Type in booking_rules.txt #528
This PR introduces clarifications specifically for demand-responsive transportation (DRT) services, allowing a value of 1 for continuous_pickup/continuous_drop_off when start_pickup_drop_off_window/end_pickup_drop_off_window are indicated. It also updates the data type of four fields in booking_rules.txt to a positive integer.
This PR introduces clarifications specifically for demand-responsive transportation (DRT) services, allowing a value of 1 for continuous_pickup/continuous_drop_off when start_pickup_drop_off_window/end_pickup_drop_off_window are indicated. It also updates the data type of four fields in booking_rules.txt to a positive integer.
š Recently Adopted
[GTFS Fares v2] Add rider_categories.txt #511
The rider_categories.txt file is part of the GTFS-Fares v2 proposal, aimed at modeling rider categories that are eligible for certain fares.
The rider_categories.txt file is part of the GTFS-Fares v2 proposal, aimed at modeling rider categories that are eligible for certain fares.
š Active Proposals
Fix typos in gtfs-realtime.proto #541
1Maxnet1 flagged and suggested fixes for a few typos in the Proto file for Realtime. This is a documentation maintenance change that could benefit from review by other community members before merging.
Enhancing GTFS Schedule and Realtime with original_trip_id #534
Davidr1234 suggests adopting `original_trip_id` from the Google Transit extension in both GTFS Schedule and GTFS Realtime. This would allow for seamless referencing of trips between GTFS and other standards, such as SIRI and NeTEx, which have a similar concept.
Add stops.stop_access field #515
This PR adds a stop_access field in stops.txt to indicate how the stop is accessed for a particular station. Please refer to this proposal for details. Adding this field is also the first phase of our three-phase plan to improve station modeling.
Deprecate TripUpdate.schedule_relationship = ADDED, add TripUpdate.schedule_relationship = NEW / REPLACEMENT to specify new / replaced trips which do not run on a schedule from the GTFS static. #504
The original proposal in this PR was changed after a vote failed. The updated proposal focuses on deprecating TripUpdate.schedule_relationship = ADDED in GTFS Realtime and replacing it with TripUpdate.schedule_relationship = NEW to indicate a completely new trip not found in GTFS Schedule, with the new value flagged as experimental. We invite as many people as possible to join the discussion to ensure the changes are thoroughly considered by the community before the next vote.
1Maxnet1 flagged and suggested fixes for a few typos in the Proto file for Realtime. This is a documentation maintenance change that could benefit from review by other community members before merging.
Enhancing GTFS Schedule and Realtime with original_trip_id #534
Davidr1234 suggests adopting `original_trip_id` from the Google Transit extension in both GTFS Schedule and GTFS Realtime. This would allow for seamless referencing of trips between GTFS and other standards, such as SIRI and NeTEx, which have a similar concept.
Add stops.stop_access field #515
This PR adds a stop_access field in stops.txt to indicate how the stop is accessed for a particular station. Please refer to this proposal for details. Adding this field is also the first phase of our three-phase plan to improve station modeling.
Deprecate TripUpdate.schedule_relationship = ADDED, add TripUpdate.schedule_relationship = NEW / REPLACEMENT to specify new / replaced trips which do not run on a schedule from the GTFS static. #504
The original proposal in this PR was changed after a vote failed. The updated proposal focuses on deprecating TripUpdate.schedule_relationship = ADDED in GTFS Realtime and replacing it with TripUpdate.schedule_relationship = NEW to indicate a completely new trip not found in GTFS Schedule, with the new value flagged as experimental. We invite as many people as possible to join the discussion to ensure the changes are thoroughly considered by the community before the next vote.
Other open proposals:
- Introduce boarding permissions to specify the carriage of vehicles at per-stop granularity #533
- Addition of event_based_trips.txt to specification #527
- Stop Time Events in the past should be kept #502
- [GTFS Fares v2] Add nonconsecutive_transfer_allowed field and clarify fare_transfer_type #498
- [GTFS Fares v2] Area Set matching predicates #483
- Clarification of CANCELED/SKIPPED TripUpdates VS NO_SERVICE Alerts #482
- [GTFS-Fares v2] Fare product/media transfer behavior #423Ā
š„ Most Active Conversations
Jerome seeks clarification on whether a null fare_media_id acts as a wildcard in fare_products, allowing a free transfer across all fare media, or if explicit duplication is required for each fare medium.
GTFS Realtime Stop Time Updates Timestamp type #537
lolpro11 questions whether the time field in StopTimeEvent, currently an int64, should be transitioned to uint64 for consistency with other GTFS Realtime timestamp fields.
Pluralized field names? #536
Nina questions why fields with a "Many" cardinality in GTFS are given singular rather than pluralized names. A response explains that since each row in a CSV contains only a single foreign key reference, the column name applies to the individual row rather than representing a collection.
Best Practices: Reasonable lengths in unique ids #518Ā
GTFS Realtime Stop Time Updates Timestamp type #537
lolpro11 questions whether the time field in StopTimeEvent, currently an int64, should be transitioned to uint64 for consistency with other GTFS Realtime timestamp fields.
Pluralized field names? #536
Nina questions why fields with a "Many" cardinality in GTFS are given singular rather than pluralized names. A response explains that since each row in a CSV contains only a single foreign key reference, the column name applies to the individual row rather than representing a collection.
Best Practices: Reasonable lengths in unique ids #518Ā
Stefan proposes to introduce a best practice that sets a recommended character limit for any ID used in a GTFS feed, triggering a validator warning if a value exceeds 36 bytes.
Integration of carpooling lines #430Ā
Integration of carpooling lines #430Ā
AurƩlien from the French National Access Point (NAP) has opened a GitHub Issue to discuss a potential proposal to model Carpooling lines behaving like bus lines: with precise stops and destinations, but in this case, driven by regular car drivers that can receive a money incentive from fares, or share their costs with passengers. Two different potential solutions are presented for discussion.
Slack conversations on #gtfs
Holger shared an upcoming presentation at OpenTransportMeetup
Matthew inquired about the inclusion of GTFS and GTFS-RT in the Google Maps Transit Layer
Holger shared an upcoming presentation at OpenTransportMeetup
Matthew inquired about the inclusion of GTFS and GTFS-RT in the Google Maps Transit Layer
Antoine voiced a debate regarding the association of service_id and route_id
Emma looked for software vendors producing GTFS-Pathways data
Weston asked about the impact of including frequency based services in Google Maps
Slack conversations on #gtfs-realtime
Paul asked for consumersā opinions regarding GTFS-RT matching
Usamam looked for user friendly tools to store GTFS-RT data
Paul asked for consumersā opinions regarding GTFS-RT matching
Usamam looked for user friendly tools to store GTFS-RT data
Slack conversations on #gtfs-flex
Isabelle shared a question on whether Flex can be used for carpooling
Isabelle shared a question on whether Flex can be used for carpooling
Slack conversations on #gtfs-fares
Wojciech requested further details on distance-based fares
Felix asked multiple questions regarding fare_leg_rules.txt, fare_transfer_rules.txt, fare_leg_join_rules.txt and timeframes.txt that were relevant in implementing Fares v2.
Weston followed up on a distance-based fares question from the Fares Working Group Meeting
Wojciech requested further details on distance-based fares
Felix asked multiple questions regarding fare_leg_rules.txt, fare_transfer_rules.txt, fare_leg_join_rules.txt and timeframes.txt that were relevant in implementing Fares v2.
Weston followed up on a distance-based fares question from the Fares Working Group Meeting
š
Upcoming Events
GTFS-Fares v2 ā Monthly meetings | March 25, 2025 @ 11 am EST
Topics : GTFS-Fares v2 extension Working Group Meeting
Topics : GTFS-Fares v2 extension Working Group Meeting
š¬ Join the GTFS Community
Share your ideas with the community! Join the official GTFS GitHub repository.
Get updates as soon as they happen, join the GTFS-changes google groups to get information about new pull requests and votes.
Talk everything Realtime and stay up to date. This group is discussing the GTFS Realtime, asking questions, and proposing changes.
The official GTFS documentation website. Here you will find frequently updated resources for your GTFS needs.
Have a question about GTFS or need to connect with the community? Join in on GTFS slack conversations. This is a great place to have questions answered quickly by the over 1,300 mobility enthusiasts navigating our channels.Ā And yes, it's Free!
Thank you for reading this edition of the GTFS Digest! We look forward to bringing you the latest GTFS updates in 2025 and beyond.
Reply all
Reply to author
Forward
0 new messages