A GTFS feed, which contains static transit information, is composed of a number of text (.txt) files that are contained in a single ZIP file. Each file describes a particular aspect of transit information: stops, routes, trips, fares, etc. For more information about each file, consult the GTFS reference.
In order to create a GTFS feed follow the steps below.
Datasets should be published at a public, permanent URL, including the zip file name. (e.g., www.agency.org/gtfs/gtfs.zip). Ideally, the URL should be directly downloadable without requiring login to access the file, to facilitate download by consuming software applications. While it is recommended (and the most common practice) to make a GTFS dataset openly downloadable, if a data provider does need to control access to GTFS for licensing or other reasons, it is recommended to control access to the GTFS dataset using API keys, which will facilitate automatic downloads.
The web-server hosting GTFS data should be configured to correctly report the file modification date (see HTTP/1.1 - Request for Comments 2616, under Section 14.29).
See “Best Practices: Dataset Publishing” for further recommendations.
The World Bank Open Learning Campus (OLC) offers a self-based online course called “Introduction to the General Transit Feed Specification (GTFS) and Informal Transit System Mapping”. This course includes the following sections:
There are a number of mailing lists that can be good resources when you have questions about public transit data, software, formats like GTFS and GTFS-realtime, and other issues:
Transit Developers: general transit developer discussions. Many transit agencies also have their own developer mailing lists specific to the agency. For example: