Difference between revisions of "Best practices for creating GTFS"

From TransitWiki
Jump to: navigation, search
(created page, linking to Transit App "Open Data Guidelines")
 
(Add Google Transit best practices)
Line 1: Line 1:
 
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 [[:Category:GTFS-consuming applications|GTFS-consuming applications]]. Various pages on the web offer advice on best practices for creating GTFS.
 
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 [[:Category:GTFS-consuming applications|GTFS-consuming applications]]. Various pages on the web offer advice on best practices for creating GTFS.
  
[[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.
+
* [[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 Transit has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html Best Practices Guide]
  
 
[[Category:General Transit Feed Specification]]
 
[[Category:General Transit Feed Specification]]

Revision as of 22:10, 26 February 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.