Difference between revisions of "Best practices for creating GTFS"

From TransitWiki
Jump to navigation Jump to search
(Update GTFS-rt rules page)
(add link to open a GTFS Realtime feed in the browser)
 
(2 intermediate revisions by 2 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.
 
* [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]
Line 11: Line 14:
 
* [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]].
 
* [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.
 
* 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]]
{{Template:Contributors}}
 

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: