Skip navigation

Unofficial/Proposed GTFS Data Elements

TriMet's GTFS includes a few unofficial GTFS data elements. These elements are documented below:

agency.txt

Field Name Required Details
bike_policy_url Optional The bike_policy_url specifies the URL of a web page where you can read the details about the agency's bike policy.

linked_datasets.txt

Field Name Required Details
url Required The url field contains the URL of a GTFS-realtime service.
trip_updates Required The trip_updates field contains a binary value that indicates URL contains GTFS-realtime trip updates.

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 Required The vehicle_positions field contains a binary value that indicates URL contains GTFS-realtime vehicle positions.

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 Required The service_alerts field contains a binary value that indicates URL contains GTFS-realtime service alerts.

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 Required The authentication_type field defines the type of authentication required to access the URL.

Valid options are:
  • 0 - No authentication required
  • 2 - The authentication requires an API key, which should be passed as value of the parameter api_key_parameter_name in the URL. Please visit URL in authentication_info_url for more information.
authentication_info_url Optional The authentication_info_url field contains a URL to a human-readable page describing how the authentication should be performed and how credentials can be created.
api_key_parameter_name Optional The api_key_parameter_name field defines the name of the parameter to pass in the URL to provide the API key.

route_directions.txt

Field Name Required Details
route_id Required ID referencing route.route_id
direction_id Required Indicates the direction of travel for a trip. This field is not used in routing; it provides a way to separate trips by direction when publishing time tables.

Valid options are:
  • 0 - Travel in one direction (e.g. outbound travel)
  • 1 - Travel in the opposite direction (e.g. inbound travel)
direction_name Required The generalized agency direction name used to idenitify route in a specific direction of travel.

stops.txt

Field Name Required Details
tts_stop_name Optional Readable version of the stop_name. The field is aimed to be read as text-to-speech, therefore, abbreviation should be either removed ("St" should be either read as "Street" or "Saint"; "Elizabeth I" should be "Elizabeth the first") or kept to be read as it ("JFK Airport" is said abbreviated).

stop_times.txt

Field Name Required Details
continuous_pickup Optional The continuous_pickup field can be used to indicate a section of a trip where it is possible to board the transit vehicle at any point along the vehicle’s path of travel. Some terms used to describe this service feature include "hail-and-ride" (UK), "request stops" (UK) or "flag stops" (USA). In order to describe this type of service, the trip must reference a route alignment (shape_id) in shapes.txt. After a continuous_pickup type is specified that type applies for the length of the vehicle path through stop points until a different, non-empty continuous_pickup value is specified in a subsequent stop_times.txt record for the trip. continuous_pickup applies only to pickup on an alignment, and does not override any pickup_type values that are set for discrete stops.

Valid options are:
  • 0 or blank - Normal stop behaviour along route (default)
  • 3 - The rider may indicate they wish to board by "flagging" the vehicle on the street, without prior notice
continuous_dropoff Optional The continuous_dropoff field can be used to indicate a section of a trip where it is possible to alight from the transit vehicle at any point along the vehicle’s path of travel. Some terms used to describe this service feature include "hail-and-ride" (UK), "request stops" (UK) or "flag stops" (USA). In order to describe this type of service, the trip must reference a route alignment (shape_id) in shapes.txt. After a continuous_dropoff type is specified in a trip that type applies for the length of the vehicle path through subsequent stop_times.txt records until a different, non-empty continuous_dropoff value is specified in a subsequent stop_times.txt record for the trip. continuous_dropoff applies only to drop-off on an alignment, and does not override any drop_off_type values that are set for discrete stops.

Valid options are:
  • 0 or blank - Normal stop behaviour along route (default)
  • 3 - The rider may indicate they wish to alight by coordinating with the driver.