GTFS Schedule Overview

ReferenceBest PracticesExamplesChangesValidatePublish

Getting Started

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.

1. Create all the required files described in the GTFS Schedule reference. Create the optional files if their functionality is desired.
2. Save all files in the .txt format. Field values should be comma delimited and each line should end with a line break. See the GTFS reference for detailed information on the file contents.
3. Zip all the text files together. The zipped file comprises a version of the feed.
4. Make the feed publicly available. See Publishing and Sharing your GTFS for more info.

Training & Resources

---

Technical details about GTFS, what it is, and how to create and maintain data:

• GTFS Introductory video
• Data examples with various features
• World Bank "Intro to GTFS" online course
• MBTA GTFS Onboarding

View example feeds:

• GTFS Mobility Database
• Transitland

See more data sources.

For free tools and instructional materials:

• MobilityData GTFS Schedule Validator
• NRTAP GTFS Builder
• Arcadis IBI Data Tools

See more free tools.

For ideas on vendors who offer GTFS services:

• Center for Urban Transportation Research, University of South Florida List of GTFS Vendors

See more online courses.

Getting Help & Community

---

Mailing Lists

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:

• GTFS Digest: generated monthly providing an overview of developments on GTFS.
• GTFS Changes: discussion of proposal for extending the GTFS specification, as outlined in the GTFS Changes document.
• GTFS Realtime: discussion of the GTFS-realtime specification.
• MobilityData Slack: Slack "organization" at with channels devoted to GTFS topics. Request an invite to mobilitydata-io.slack.com here.
• transitfeed: discussion of the open-source transitfeed project, as well of discussion of the GTFS specification and associated tools.
• transit-developers: general transit developer discussions. Many transit agencies also have their own developer mailing lists specific to the agency. For example:
  • NYC MTA
  • Portland, OR
  • BART - San Francisco, CA
  • MassDOT
  • Atlanta, GA region
  • 511 San Francisco Bay Area Developer Resources

Check with your local transit agency to see if they have a mailing list of their own.

See more community resources.