Difference between revisions of "Best practices for creating GTFS"
Jump to navigation
Jump to search
(Add Google Transit best practices) |
|||
| Line 2: | Line 2: | ||
* [[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 | + | * Google Maps has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html GTFS Best Practices Guide] |
[[Category:General Transit Feed Specification]] | [[Category:General Transit Feed Specification]] | ||
Revision as of 22:11, 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.
- 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