Best practices for creating GTFS - Revision history

Gavinr: add link to open a GTFS Realtime feed in the browser

2020-04-05T22:06:16Z

add link to open a GTFS Realtime feed in the browser

← Older revision		Revision as of 22:06, 5 April 2020
Line 14:		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]]

Jmatute at 23:43, 21 August 2017

2017-08-21T23:43:53Z

← Older revision		Revision as of 23:43, 21 August 2017
Line 16:		Line 16:

	[[Category:General Transit Feed Specification]]		[[Category:General Transit Feed Specification]]
	~~{{Template:Contributors}}~~

Barbeau: Split out official from unofficial Best Practices

2017-03-02T19:13:43Z

Split out official from unofficial Best Practices

← Older revision		Revision as of 19:13, 2 March 2017
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]

Barbeau: Update GTFS-rt rules page

2017-03-02T19:10:46Z

Update GTFS-rt rules page

← Older revision		Revision as of 19:10, 2 March 2017
Line 10:		Line 10:
	* [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://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]].		* [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/~~wiki~~/~~Rules-and-Test-Cases~~ 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.

	[[Category:General Transit Feed Specification]]		[[Category:General Transit Feed Specification]]
	{{Template:Contributors}}		{{Template:Contributors}}

Aaronantrim: added gtfs.org/best-practices

2017-02-23T16:57:35Z

added gtfs.org/best-practices

← Older revision		Revision as of 16:57, 23 February 2017
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.

			* [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.
	* [[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]

Jmatute at 21:14, 21 October 2016

2016-10-21T21:14:09Z

← Older revision		Revision as of 21:14, 21 October 2016
Line 12:		Line 12:

	[[Category:General Transit Feed Specification]]		[[Category:General Transit Feed Specification]]
			{{Template:Contributors}}

Aaronantrim: added link to headsign practices

2016-09-29T04:13:33Z

added link to headsign practices

← Older revision		Revision as of 04:13, 29 September 2016
Line 6:		Line 6:
	* [[RideSchedules]] provides GTFS Publisher Best Practices for creating and hosting GTFS.		* [[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://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/wiki/Rules-and-Test-Cases 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/wiki/Rules-and-Test-Cases some best practices] as part of their experience with GTFS-realtime feeds.

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

Aaronantrim: added link to RideSchedules and Kurt

2016-09-29T03:39:18Z

added link to RideSchedules and Kurt

← Older revision		Revision as of 03:39, 29 September 2016
Line 3:		Line 3:
	* [[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.
	* 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.		* 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]]		[[Category:General Transit Feed Specification]]

Barbeau: Add link to CUTR test cases

2016-03-22T18:52:56Z

Add link to CUTR test cases

← Older revision		Revision as of 18:52, 22 March 2016
Line 4:		Line 4:
	* 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.		* 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.
			* 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]]		[[Category:General Transit Feed Specification]]

Barbeau: Add link to open Google Doc

2016-03-22T18:50:39Z

Add link to open Google Doc

← Older revision		Revision as of 18:50, 22 March 2016
Line 3:		Line 3:
	* [[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.

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