Adding GTFS Best Practices to the core (static) reference

30 views
Skip to first unread message

Aaron Antrim

unread,
Jun 11, 2019, 7:58:40 PM6/11/19
to gtfs-c...@googlegroups.com
Five pull requests are open that would incorporate elements of the GTFS Best Practices (gtfs.org/best-practices) into the GTFS core reference.

One of the intentions of the GTFS Best Practices process [link] was to provide a staging ground for specification improvements. Since these Best Practices have been published for ~1.5 years, MobilityData believes it is a good time to bring these to community discussion and vote. The list below represents changes to the GTFS that provide additional specificity or clarity.

- Add best practice: stop_id is not rider-facing (https://github.com/google/transit/pull/169)
- Add best practice: In-seat transfer specifics (https://github.com/google/transit/pull/168)
- Headsign best practices (https://github.com/google/transit/pull/167)
- Add best practices: Headsign and route name examples (https://github.com/google/transit/pull/166)
- Arrival and departure time best practices (https://github.com/google/transit/pull/165)

Let’s start the 7 day discussion period on the above pull requests. Please add notes on GitHub if you support the changes, have objections, or have change suggestions. I will call a vote after discussion has concluded (minimum 7 days).

Aaron Antrim (Trillium)

unread,
Jun 19, 2019, 1:04:08 AM6/19/19
to General Transit Feed Spec Changes
Voting has begun on this batch of pull requests. #168 was removed. Below are the links for fast voting. Thanks!

- Add best practice: stop_id is not rider-facing (https://github.com/google/transit/pull/169)
- Headsign best practices (https://github.com/google/transit/pull/167)
- Add best practices: Headsign and route name examples (https://github.com/google/transit/pull/166)
- Arrival and departure time best practices (https://github.com/google/transit/pull/165)

Aaron Antrim (Trillium)

unread,
Jun 28, 2019, 5:31:39 PM6/28/19
to General Transit Feed Spec Changes
The following changes passed:
- "Arrival and departure time best practices" (https://github.com/google/transit/pull/165)
- "Headsign best practices" (https://github.com/google/transit/pull/167)
- "Add best practice: stop_id is not rider facing" (https://github.com/google/transit/pull/169)

Though there was support for "Add best practices: Headsign and route name examples" (https://github.com/google/transit/pull/166) we received requests for different types of examples. The plan is to modify the change request and bring it back to vote.
Reply all
Reply to author
Forward
0 new messages