OpenDataWeek Marseille 2013 : Andrew Byrd -- The General Transit Feed Specification (GTFS)

4,989 views
4,836 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,989
On SlideShare
0
From Embeds
0
Number of Embeds
37
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

OpenDataWeek Marseille 2013 : Andrew Byrd -- The General Transit Feed Specification (GTFS)

  1. 1. The General Transit Feed Specification (GTFS) A success story in spontaneous standardization Andrew Byrd Project Lead, OpenTripPlanner (open source multi-modal trip planner) Co-founder and Principal, Conveyal (open data driven transportation consultancy) email: abyrd@conveyal.com
  2. 2. What is GTFS? - “The General Transit Feed Specification” - Public transport data for journey planning - Stop locations, routes, schedules, and transfers - Recently extended for real-time vehicle delay and location - An open, light-weight specification created entirely by industry
  3. 3. Where did GTFS come from? - Origins in Portland, Oregon (US) in 2005 - TriMet regional transport agency wanted journey planning - discovered a Google “20%” project with this goal and needed to exchange data - Simply exported their schedule database into structured text files - GTFS has been extended but remains essentially the same
  4. 4. How does GTFS evolve? - Collaborative review and modification process - Only backward-compatible extensions are considered - No “theoretical” improvements: only features which are actually used by GTFS consumers
  5. 5. Why GTFS? It is an alternative to heavyweight XML norms. TriMet considered: - National Transportation Communications for Intelligent Transportation System Protocol (TCIP, US FTA) - New York's Schedule Data Profile (SDP)
  6. 6. TriMet practical findings on official norms: 1. Too many layers and types. Must traverse ten layers to reach stop coordinates.
  7. 7. TriMet practical findings on official norms: 1. Too many layers and types. Must traverse ten layers to reach stop coordinates. 2. Ambiguity. Several different element types can be used to represent the same reality. Conclusion: We need “a smaller, flatter and narrowly focused set of elements.” This can be exported from more detailed operational databases or national/international data exchange norms.
  8. 8. “Agencies develop different requirements, policies and practices over time, even while performing the same basic task. A standard that encompasses such business logic is liable to fail as it attempts to normalize the elements of the task. TCIP is so broad in its definition, that we feel it’s almost unusable as a standard. The size and ambiguity alone are real show-stoppers. A more feasible approach would be to move away from … large data / process / business rules standards, and in the direction of simple, clean, compartmentalized sets of standards that define a narrow set of data elements for a specific given task.”
  9. 9. GTFS : Simple schema, CSV tables (i.e. a zip of text files) Used for almost all open public transport data in the United States and France. Data is not as rich as “heavy” XML standards like NeTEx (Europe) or TCIP (US FTA), but much preferred by many developers and agencies: - Evolved directly from a specific use case (journey planning) - Parsing / loading is straightforward - A single way to express each concept (facilitates implementation)
  10. 10. GTFS Routes:
  11. 11. GTFS Stops:
  12. 12. GTFS Stop times:
  13. 13. Open public transport data availability in GTFS format - United States: > 80% of passenger-km in PT covered - In France: Rennes, Nantes, Bordeaux, SNCF Transilien, TER, Intercités and the entire RATP (Métro, bus, tram, night buses) - Netherlands: nearly 100% coverage by OpenOV, with the position and delay of each vehicle updated 1 time per minute - Conversion from more detailed European standards straightforward (e.g. for Bouches du Rhône)
  14. 14. Growth in GTFS availability over time in US
  15. 15. Reuse of this operational data - Passenger information (journey planners, bus arrival notices) But also... - Infrastructure and service planning, impact studies - Town planning, communication, public consultations - Social and economic research
  16. 16. Publishing open transport data in common open formats allows immediate reuse with existing software.
  17. 17. Andrew Byrd email: abyrd@conveyal.com code: http://github.com/openplans/OpenTripPlanner http://openplans.org/2012/08/the-openplans-guide-to-gtfs-data/

×