Best practices for creating GTFS: Difference between revisions

From TransitWiki
Jump to navigation Jump to search
Barbeau (talk | contribs)
Add link to open Google Doc
Gavinr (talk | contribs)
add link to open a GTFS Realtime feed in the browser
Tag: visualeditor-switched
 
(8 intermediate revisions by 3 users not shown)
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.


'''Official''':
* [http://gtfs.org/best-practices/ GTFS.org Industry-Standard Best Practices] - These Best Practices are agreed to and published by 17 industry partners. These are the most broadly-accepted and complete GTFS Best Practices.
'''Unofficial''':
* [[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 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.
* 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.
* [https://gtfsbook.com Quentin Zervaas's Book The Definitive Guide to GTFS] offers some discussion of GTFS best practices and style choices.
* [https://github.com/google/transitfeed/wiki/FeedValidatorErrorsAndWarnings FeedValidator's errors and warnings] reference provides an inventory of some common GTFS defects to avoid. feedvalidator.py software can automatically identify these potential issues.
* [https://trilliumtransit.zendesk.com/hc/en-us/articles/201876369-Display-of-headsign-Google-Maps- Best practices and application-behavior context for specifying headsigns] in GTFS from [[Trillium]].
* The Center for Urban Transportation Research at the University of South Florida has identified [https://github.com/CUTR-at-USF/gtfs-realtime-validator/blob/master/Rules_Implemented.md some best practices] as part of their experience with GTFS-realtime feeds.
* [https://dev.to/gavinr/how-to-open-a-gtfs-bus-feed-in-the-browser-kgo How to Open a GTFS Feed in the Browser]


[[Category:General Transit Feed Specification]]
[[Category:General Transit Feed Specification]]

Latest revision as of 22:06, 5 April 2020

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.

Official:

Unofficial: