Changes

Jump to: navigation, search

Best practices for creating GTFS

7 bytes added, 19:10, 2 March 2017
Update GTFS-rt rules page
* [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/wikiblob/Rules-and-Test-Cases master/Rules_Implemented.md some best practices] as part of their experience with GTFS-realtime feeds.
[[Category:General Transit Feed Specification]]
{{Template:Contributors}}
Bureaucrats, engaged
55
edits

Navigation menu