Difference between revisions of "Best practices for creating GTFS"

From TransitWiki
Jump to: navigation, search
(Add link to open Google Doc)
(Add link to CUTR test cases)
Line 4: Line 4:
 
* Google Maps has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html GTFS Best Practices Guide]
 
* Google Maps has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html GTFS Best Practices Guide]
 
* A [https://docs.google.com/document/d/1FeAJNDs-1EdzcQq_daq8_uR0KIug6tzKDxdPxSdi8L4/edit?usp=sharing open Google Doc] has captured some best practices from members of the GTFS community.
 
* A [https://docs.google.com/document/d/1FeAJNDs-1EdzcQq_daq8_uR0KIug6tzKDxdPxSdi8L4/edit?usp=sharing open Google Doc] has captured some best practices from members of the GTFS community.
 +
* The Center for Urban Transportation Research at the University of South Florida has identified [https://github.com/CUTR-at-USF/gtfs-realtime-validator/wiki/Rules-and-Test-Cases some best practices] as part of their experience with GTFS-realtime feeds.
  
 
[[Category:General Transit Feed Specification]]
 
[[Category:General Transit Feed Specification]]

Revision as of 18:52, 22 March 2016

The General Transit Feed Specification allows for transit features to be described using a variety of approaches. In some cases, particular approaches will result in better results in GTFS-consuming applications. Various pages on the web offer advice on best practices for creating GTFS.

  • The Transit App developers page provides "Open Data Guidelines" which includes recommendations on how to form GTFS for best results in the application.
  • Google Maps has a GTFS Best Practices Guide
  • A open Google Doc has captured some best practices from members of the GTFS community.
  • The Center for Urban Transportation Research at the University of South Florida has identified some best practices as part of their experience with GTFS-realtime feeds.