Changes

Jump to: navigation, search

Best practices for creating GTFS

274 bytes added, 03:39, 29 September 2016
added link to RideSchedules and Kurt
* [[The Transit App]] [http://transitapp.com/developers developers page] provides "Open Data Guidelines" which includes recommendations on how to form GTFS for best results in the application.
* Google Maps has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html GTFS Best Practices Guide]
* A An [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.* [[RideSchedules]] provides GTFS Publisher Best Practices for creating and hosting GTFS.* [https://kurtraschke.com/2014/03/gtfs-download Kurt Raschke] provides recommendations for how to host GTFS data on a server to ensure update availability in consuming applications.
* 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]]

Navigation menu