GTFS

GTFS
Name	General Transit Feed Specification
Abbreviation	GTFS
Type	data specification
Initial release	2006
Developer	Google Transit Partnership
License	public domain / various

GTFS

The General Transit Feed Specification (GTFS) is a standardized data format for public transportation schedules and associated geographic information. It enables interoperability between transit agencies, mapping platforms, trip planners, and research tools by defining a set of text files and fields that describe routes, stops, trips, and timetables. GTFS has become a foundation for transit data exchange among agencies such as Metropolitan Transportation Authority (New York) , Transport for London, SNCF, Deutsche Bahn, and platforms like Google Maps, OpenTripPlanner, and HERE Technologies.

Overview

GTFS specifies a collection of comma-separated values (CSV) files that represent transit network elements including stops, routes, trips, stop times, calendars, and fare information. Major adopters include Federal Transit Administration, European Commission, Transport for Edinburgh, Los Angeles County Metropolitan Transportation Authority, and international operators such as Japan Railways Group and Agence métropolitaine de transport. The format enables integration with routing engines like GraphHopper, Valhalla (software), and journey planners used by Apple Maps and Citymapper. GTFS feeds are commonly published by agencies on portals inspired by initiatives from OpenStreetMap community and civic data projects like Transitland.

History and Development

GTFS originated from collaboration between engineers at Google and transit agencies including TriMet and New York City Transit to support the launch of transit directions in Google Maps in 2005–2006. Early specification development involved contributors from Portland State University and open-data advocates such as Sunlight Foundation. The format evolved through community discussion hosted on mailing lists and code repositories influenced by projects funded by Knight Foundation and technical work from organizations like Mapzen and MobilityData. Over time, extensions and related efforts—such as models developed by OpenStreetMap Foundation contributors and standards comparisons with NeTEx—shaped GTFS usage in Europe, North America, and Asia.

Specification and File Structure

The core GTFS model consists of required files like agency.txt, stops.txt, routes.txt, trips.txt, stop_times.txt, and calendar.txt, plus optional files such as frequencies.txt, shapes.txt, and transfers.txt. Implementations often reference schema discussions involving ISO 8601 conventions and coordinate systems used by projects like EPSG:4326 in mapping stacks from Esri or Mapbox. Advanced features interact with fare models inspired by National Transit Database practices and schedule exceptions similar to patterns used by Amtrak and Deutsche Bahn. Extensions and rival schemas discussed by organizations including MobilityData and European Union standards bodies address multilingual fields, accessibility attributes, and real-time updates.

Uses and Applications

GTFS is used for static schedule distribution, route planning, accessibility analysis, ridership modeling, and realtime augmentation via GTFS-realtime feeds. Transit agencies such as Chicago Transit Authority, MBTA, RATP Group, Sydney Trains, and Toronto Transit Commission publish GTFS data to power apps like Transit (app), Moovit, and municipal trip planners. Researchers at institutions like Massachusetts Institute of Technology, University College London, and University of California, Berkeley use GTFS for urban mobility studies, GIS analyses with QGIS, and integration into transport simulation tools such as MATSim and SUMO. Third-party services aggregate feeds for compliance checks influenced by regulators like California State Transportation Agency and initiatives from World Bank urban mobility programs.

Implementation and Tools

A broad ecosystem supports GTFS creation, validation, conversion, and visualization. Notable tools include validators from TransitFeeds, parsers in programming environments promoted by Apache Software Foundation projects, converters developed by Mapzen alumni, and hosting platforms like TransitLand and GTFS Data Exchange. Developers use libraries for languages such as Python, JavaScript, and Java maintained by communities around GitHub repositories and continuous-integration workflows influenced by practices at Google Open Source Programs Office. Visualization and editing tools integrate with GIS products from Esri and open-source stacks like Leaflet and OpenLayers.

Limitations and Criticism

Critics cite GTFS’s focus on static schedules as insufficient for on-demand and microtransit services offered by providers like Uber and Lyft or for multimodal journeys involving Bicycle Sharing System operators and Scooter-sharing companies. Comparisons with standards such as NeTEx highlight GTFS’s limited modeling of complex fare rules, real-time operational exceptions, and hierarchical network relationships used by large operators like Deutsche Bahn and SNCF Réseau. Data quality issues—stemming from inconsistent agency practices at organizations like smaller municipal transit authorities—affect reliability for researchers at institutions such as Stanford University and policy bodies like European Cyclists' Federation. Privacy and licensing debates have involved stakeholders including Creative Commons advocates and national open-data programs.

Governance and Maintenance

GTFS lacks a single formal standards body; stewardship has been informal, with contribution and stewardship by companies like Google and nonprofit coalitions such as MobilityData and community-maintained repositories on GitHub. Regional initiatives from entities like Transport for New South Wales and advocacy groups including Open Knowledge Foundation participate in evolving best practices. Coordination with international standards organizations such as CEN and alignment efforts with projects sponsored by European Commission and USDOT shape the future of the specification and interoperability with complementary schemas.

Category:Transportation data formats