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. The value must be a fully qualified URL that includes http:// or https://, and any special characters in the URL must be correctly escaped. See http://www.w3.org/Addressing/URL/4_URI_Recommentations.html for a description of how to create fully qualified URL values.

feed_info.txt

Field Name Required Details
feed_id Optional The feed_id field contains a universally unique id for the feed, found here: http://gtfs.org/feeds.txt.

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

routes.txt

Field Name Required Details
route_sort_order Optional The route_sort_order field contains the agency's preferred sort order when displaying route lists e.g. a route dropdown/combobox.

stop_times.txt

Field Name Required Details
continuous_stops Optional The continuous_stops field can be used to indicate a section of a trip where it is possible to board or alight from the transit vehicle at any point along the vehicle's path of travel.

The field can have the following non-negative integer values:
  • 0 or blank - Normal stop behaviour along route (default)
  • 1 - Continuous stopping behaviour from this stop-time to the next stop-time in the trip's sequence.