<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.transitwiki.org/TransitWiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gavinr</id>
	<title>TransitWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.transitwiki.org/TransitWiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gavinr"/>
	<link rel="alternate" type="text/html" href="https://www.transitwiki.org/TransitWiki/index.php/Special:Contributions/Gavinr"/>
	<updated>2026-04-24T08:05:31Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.1</generator>
	<entry>
		<id>https://www.transitwiki.org/TransitWiki/index.php?title=Best_practices_for_creating_GTFS&amp;diff=5483</id>
		<title>Best practices for creating GTFS</title>
		<link rel="alternate" type="text/html" href="https://www.transitwiki.org/TransitWiki/index.php?title=Best_practices_for_creating_GTFS&amp;diff=5483"/>
		<updated>2020-04-05T22:06:16Z</updated>

		<summary type="html">&lt;p&gt;Gavinr: add link to open a GTFS Realtime feed in the browser&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
'''Official''':&lt;br /&gt;
* [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.&lt;br /&gt;
&lt;br /&gt;
'''Unofficial''':&lt;br /&gt;
* [[The Transit App]] [http://transitapp.com/developers developers page] provides &amp;quot;Open Data Guidelines&amp;quot; which includes recommendations on how to form GTFS for best results in the application.&lt;br /&gt;
* Google Maps has a [https://maps.google.com/help/maps/mapcontent/transit/bestpractices.html GTFS Best Practices Guide]&lt;br /&gt;
* 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.&lt;br /&gt;
* [[RideSchedules]] provides GTFS Publisher Best Practices for creating and hosting GTFS.&lt;br /&gt;
* [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.&lt;br /&gt;
* [https://gtfsbook.com Quentin Zervaas's Book The Definitive Guide to GTFS] offers some discussion of GTFS best practices and style choices.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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]].&lt;br /&gt;
* 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.&lt;br /&gt;
* [https://dev.to/gavinr/how-to-open-a-gtfs-bus-feed-in-the-browser-kgo How to Open a GTFS Feed in the Browser]&lt;br /&gt;
&lt;br /&gt;
[[Category:General Transit Feed Specification]]&lt;/div&gt;</summary>
		<author><name>Gavinr</name></author>
	</entry>
</feed>