GTFS Changes

The vote for PR #561 has been initiated. Voting ends on 2025-09-15 at 23:59:59 UTC. On Thursday,

A pull request has been opened to add a stop_access field in stops.txt, which indicates how a stop is

I have updated the pull request to include similar best practices for GTFS real-time. I have called

The voting period is closed and the vote has passed. 7 votes in favor, 0 votes against. +1

The voting period ended on June 26th at 23:59:59 UTC. The result is: +1 MOTIS +1 SBB +1

The voting period ended on 2025-04-11. There were 9 votes for and 1 abstention. Therefore the vote

A new round of voting for PR#528 has been opened. Voting ends on 2025-04-07 at 23:59:59 UTC. On

I'm afraid it's even worse than that. Two GTFS feeds may contain the same agency perhaps even

The vote passed on 2025-02-13 at 23:59:59 UTC. 7 votes in favour and no votes against. Votes came

A pull request has been opened to add original_trip_id to GTFS Schedule and GTFS Realtime. Link:

The voting period has concluded. 5 votes in support, the proposition is approved! Thanks everyone! —

I've found python's gtfs-kit to be most helpful. https://mrcagney.github.io/gtfs_kit_docs/

A draft pull request has been opened to support modeling of trips for special events that depart

The vote for PR #439 has been opened. Voting ends on 2024-12-03 at 23:59:59 UTC. On Tuesday, November

A pull request has been opened to add nonconsecutive_transfer_allowed field and clarify

A pull request has been opened to add support for matching "sets" of areas in

A pull request has been opened to add fare_product_behavior, fare_media_behavior, and

The pull request to add GTFS Feed Version to the GTFS real time FeedHeader vote has passed on Nov 16,

The vote passed on 2024-09-17 at 23:59:59 UTC. 4 votes in favour and no votes against. Thank you to

The voting period has ended on Wednesday, September 11, 2024 at 23:59:59 UTC. The result is: +1

Hi, Sergio from MobilityData here. Regarding your question on the use of duplicated trip_id and

The vote passed on 2024-08-05 at 23:59:59 UTC. 4(+1) votes in favour and no votes against. Thank you

The voting period ended on 2024-08-15 at 23:59:59 UTC. With 3 votes in favor and no votes against,

The voting period ended on 2024-07-31 at 23:59:59 UTC. With 3 votes in favor and no votes against,

The voting period ended on 2024-07-17 at 23:59:59 UTC. With 5 votes in favor and no votes against,

The voting period ended on 2024-07-17 at 23:59:59 UTC. With 9 votes in favor and no votes against,

The vote passed on 2024-05-20 at 23:59:59 UTC. 5 votes in favour and no votes against. The votes came

The vote has passed on Apr 30 2024. We have 5 votes for the change, 0 votes against the change. Votes

The vote passed on 2024-03-18 at 23:59:59 UTC. 18 votes in favour and no votes against. The votes

This is solved by this proposal : https://docs.google.com/document/d/1E0RdoFTNKWEGVjRiaXM92Q1W1p-