GTFS-realtime

GTFS-realtime
Name	GTFS-realtime
Developer	Google
Introduced	2011
Format	Protocol Buffers

GTFS-realtime GTFS-realtime is a protocol for exchanging public transport live information that complements static transit schedules. It enables agencies to provide dynamic updates about vehicle positions, service alerts, and trip updates so that platforms can present timely departures and disruption notices to travelers, planners, and developers. The specification is used worldwide across many cities, transit agencies, technology companies, and research institutions.

Overview

GTFS-realtime was released by Google to augment the existing static transit feed specification used by platforms such as Apple Inc., Facebook, Microsoft, Amazon (company), and HERE Technologies. Major adopters include transit agencies like Metropolitan Transportation Authority (New York), Transport for London, RATP Group, Société de transport de Montréal, Deutsche Bahn, SNCF, Amtrak, TransLink (Metro Vancouver), Los Angeles County Metropolitan Transportation Authority, Chicago Transit Authority, MBTA, SEPTA, and Transport for NSW. The specification leverages Protocol Buffers developed by Google, and is frequently consumed by mapping services such as Google Maps, Apple Maps, OpenStreetMap, HERE WeGo, and transit apps like Moovit, Citymapper, Transit (app), and Rome2rio. Research and standards bodies including OpenStreetMap Foundation, IETF, W3C, U.S. Department of Transportation, European Commission, and academic institutions such as MIT, Stanford University, Imperial College London, and University of California, Berkeley study its impacts on urban mobility, accessibility, and planning.

Data Model and Feed Specification

The feed format uses serialized Protocol Buffers messages to convey three principal update types, and the specification defines fields, enumerations, and semantics that interoperable consumers must handle. The static GTFS dataset (stops, routes, trips) produced by agencies such as Transport for London or MTA (New York City) forms the reference dataset; GTFS-realtime ties live entities to that static structure using identifiers recognized by services like Google Maps and OpenTripPlanner. The schema supports timestamps, delay metrics, occupancy states, and optional vehicle descriptors; these concepts are modeled to integrate with scheduling systems from vendors like Siemens, Bombardier Transportation, Alstom, Thales Group, and Cubic Corporation. Governance and evolution of the spec involve contributors from Google, transit agencies, and open-source communities including Transitland, OpenTripPlanner, and MobilityData (formerly TransitFeeds).

Message Types and Entities

GTFS-realtime defines three primary message types: TripUpdate, VehiclePosition, and Alert. TripUpdate conveys schedule deviations and stop-level arrival/departure times; VehiclePosition reports instantaneous GPS-derived location, bearing, speed, and occupancy status; Alert publishes service disruption information with cause, effect, active periods, and affected entities. Entities reference identifiers present in static feeds such as route_id, trip_id, and stop_id used by agencies like New Jersey Transit, Caltrain, VTA (Santa Clara County), King County Metro, and Metrolinx. The Alert model accommodates translations and lifecycle windows enabling tools used by The New York Times, BBC News, The Guardian, and Reuters to annotate incidents and delays for public reporting and analysis.

Implementation and Adoption

Adoption spans municipal, regional, and national agencies and private mobility providers. Cities such as New York City, London, Paris, Berlin, Tokyo, Seoul, Toronto, Sydney, Melbourne, Singapore, Hong Kong, Los Angeles, Chicago, Boston, Madrid, Barcelona, Rome, Amsterdam, Copenhagen, Stockholm, Oslo, Helsinki, Zurich, Geneva, and Dubai host feeds integrated into journey planners, traveler information displays, and real-time analytics. Technology firms and startups including Uber Technologies, Lyft, Grab (company), Didi Chuxing, BlaBlaCar, Bolt (company), and Gett either consume or complement GTFS-realtime data for multimodal routing and demand prediction. Standards and procurement agencies such as European Union bodies, U.S. DOT, and Transport for Greater Manchester reference GTFS-realtime in contracts and interoperability frameworks.

Tools, Libraries, and Validation

A broad ecosystem of client libraries, server generators, and validators exists for languages and platforms including Java (programming language), Python (programming language), JavaScript, TypeScript, Go (programming language), Ruby (programming language), C#, and Rust (programming language). Notable open-source projects include OpenTripPlanner, Transitland, OneBusAway, Navitia.io, GTFS Kit, gtfs-realtime-bindings, and converters maintained by communities around GitHub and GitLab. Validation tools and testing frameworks from MobilityData and community validators check schema conformance, timestamp coherency, and referential integrity against static feeds produced by agencies like MTA (New York City), TransLink, and VTA (Santa Clara County).

Privacy, Security, and Performance Considerations

Deployers must balance operational transparency with traveler privacy and system resilience. Vehicle-level telemetry can implicate privacy regulations such as GDPR and policy frameworks referenced by authorities like European Commission and U.S. Department of Transportation. Security controls including HTTPS/TLS, authentication, rate limiting, and integrity checks are implemented by platform providers like Cloudflare, Amazon Web Services, Google Cloud Platform, Microsoft Azure, and transit vendors to mitigate interception and tampering. Performance considerations involve feed size, update frequency, delta encoding, and caching strategies utilized by content delivery systems and map platforms such as Fastly, Akamai Technologies, Mapbox, and HERE Technologies to serve high-volume metropolitan deployments.

Category:Public transport data formats