Skip to main content

GTFS Extensions

Metro Transit’s GTFS includes a few extensions to the GTFS standard. These elements are documented below. Please note this is intended to supplement documentation on GTFS itself.

linked_datasets.txt

Field Definition
url URL of a GTFS-realtime feed
trip_updates A binary value that indicates URL contains a GTFS-realtime TripUpdate feed. Valid options are:
  • 0 - The dataset at this URL doesn't contain TripUpdate entities.
  • 1 - The dataset at this URL may contain TripUpdate entities.
vehicle_positions A binary value that indicates URL contains a GTFS-realtime VehiclePositions feed. Valid options are:
  • 0 - The dataset at this URL doesn't contain VehiclePosition entities.
  • 1 - The dataset at this URL may contain VehiclePosition entities.
service_alerts A binary value that indicates URL contains a GTFS-realtime ServiceAlerts feed. Valid options are:
  • 0 - The dataset at this URL doesn't contain Alert entities.
  • 1 - The dataset at this URL may contain Alert entities.
authentication_type The authentication_type field defines the type of authentication required to access the URL. Valid options are:
  • 0 - No authentication required
  • 1 - The authentication requires an API key

trips.txt

Field Definition
direction

Indicates the cardinal direction of travel for a trip.
NB = northbound
SB = southbound
EB = eastbound
WB = westbound

branch_letter

Indicates the trip’s branch or variant.
Metro Transit’s service includes many branches. Trips with the same route_id serve meaningfully different stops and destinations based on their branch_letter. When referring to a specific trip, the branch_letter should always be included along with the route_id.