Reference

 

Trillium GTFS Documentation

November 2017

About this document

This document inventories fields used by GTFS feeds created and/or managed by Trillium.

About the fields in this document

  • Status field
    • Included
    • Included (some records): Used by some feeds and/or some records within a feed
  • GTFS Spec field
    • Required
    • Optional
    • Experimental: Not part of GTFS specifications, but included in Trillium GTFS

 

Table Name

GTFS Spec

Status

Notes

agency.txt

Required

Included

areas.txt

Experimental

Included in some feeds

Only used for GTFS-Flex feeds.

calendar_attributes.txt

Experimental

Included

Describes a calendar, e.g. “Weekdays” or “Year Round (Sunday Only)”

calendar_dates.txt

Optional

Included

calendar.txt

Required

Included

directions.txt

Experimental

Included

Defined by GTFS+. Combines route_id with named directions, e.g. “Westbound” or “Inbound”

fare_attributes.txt

Optional

Included in some feeds

fare_rider_categories.txt

Experimental

Included in some feeds

Combines fare_id, rider_category_id, and price.

fare_rules.txt

Optional

Included in some feeds

farezone_attributes.txt

Experimental

Included in some feeds

Combines a zone_id with a zone_name

feed_info.txt

Optional

Included

frequencies.txt

Optional

Included in some feeds

rider_categories.txt

Experimental

Included in some feeds

Combines description of rider types with ids.

routes.txt

Required

Included

shapes.txt

Optional

Included

stop_attributes.txt

Experimental

Included in some feeds

Provides a city for a given stop_id

stop_times.txt

Required

Included

stops.txt

Required

Included

timetable_stop_order.txt

Experimental

Included

Used by GTFS-to-HTML software, this is an optional file that can specify stop order for a particular timetable.

timetables.txt

Experimental

Included

Used byin GTFS-to-HTML software. Specifies timetables to build.

transfers.txt

Optional

Included

trips.txt

Required

Included

agency.txt

 

Field Name

GTFS Spec

Status

Notes

agency_id

Optional

Included

agency_url

Required

Included

agency_lang

Optional

Included

agency_name

Required

Included

agency_phone

Optional

Included

agency_timezone

Required

Included

agency_fare_url

Optional

Included

areas.txt

Areas.txt is only used for GTFS-Flex files, and must be turned on in GTFS Manager to export.

 

Field Name

GTFS Spec

Status

Notes

area_id

Experimental

Included (some records)

Used for GTFS-Flex 

wkt

Experimental

Included (some records)

Used for GTFS-Flex 

calendar_attributes.txt

 

Field Name

GTFS Spec

Status

Notes

service_id

Experimental

Included

service_description

Experimental

Included

Describes a calendar’s coverage, e.g. “Year Round (Weekend)”

calendar_dates.txt

 

Field Name

GTFS Spec

Status

Notes

service_id

Required

Included

date

Required

Included

holiday_name

Experimental

Included

Names a particular holiday, e.g. “Thanksgiving Day”

exception_type

Required

Included

calendar.txt

 

Field Name

GTFS Spec

Status

Notes

service_id

Required

Included

service_name

Required

Included

monday

Required

Included

tuesday

Required

Included

wednesday

Required

Included

thursday

Required

Included

friday

Required

Included

saturday

Required

Included

sunday

Required

Included

start_date

Required

Included

end_date

Required

Included

directions.txt

Defined by GTFS+

 

Field Name

GTFS Spec

Status

Notes

route_id

Experimental

Included

direction_id

Experimental

Included

Direction

Experimental

Included

Examples include “Northbound” or “Inbound”

fare_attributes.txt

 

Field Name

GTFS Spec

Status

Notes

agency_id

Optional

Included (some records)

fare_id

Required

Included (some records)

price

Required

Included (some records)

currency_type

Required

Included (some records)

payment_method

Required

Included (some records)

transfers

Required

Included (some records)

transfer_duration

Optional

Included (some records)

fare_rider_categories.txt

 

Field Name

GTFS Spec

Status

Notes

fare_id

Experimental

Included (some records)

rider_category_id

Experimental

Included (some records)

price

Experimental

Included (some records)

fare_rules.txt

 

Field Name

GTFS Spec

Status

Notes

fare_id

Required

Included (some records)

route_id

Optional

Included (some records)

origin_id

Optional

Included (some records)

destination_id

Optional

Included (some records)

contains_id

Optional

Included (some records)


farezone_attributes.txt

 

Field Name

GTFS Spec

Status

Notes

zone_id

Experimental

Included (some records)

zone_name

Experimental

Included (some records)

feed_info.txt

 

Field Name

GTFS Spec

Status

Notes

feed_publisher_url

Required

Included

feed_publisher_name

Required

Included

feed_lang

Required

Included

feed_version

Experimental

Included

feed_license

Experimental

Included (some records)

feed_contact_email

Experimental

Included

feed_contact_url

Optional

Included

feed_start_date

Optional

Included

feed_end_date

Optional

Included

frequencies.txt

 

Field Name

GTFS Spec

Status

Notes

trip_id

Required

Included (some records)

start_time

Required

Included (some records)

end_time

Required

Included (some records)

headway_secs

Required

Included (some records)

exact_times

Optional

Included (some records)

rider_categories.txt

Defined by GTFS+

 

Field Name

GTFS Spec

Status

Notes

rider_category_id

Experimental

Included (some records)

rider_category_description

Experimental

Included (some records)

Some examples include “Child,” “Senior,” and “Student.”


routes.txt

 

Field Name

GTFS Spec

Status

Notes

route_id

Required

Included

agency_id

Optional

Included

route_short_name

Required

Included

route_long_name

Required

Included

route_desc

Optional

Included

route_type

Required

Included

route_url

Optional

Included (some records)

route_color

Optional

Included (some records)

route_text_color

Optional

Included (some records)

route_sort_order

Experimental

Included (some records)

Integer value that can be used for ordering routes in a way that is ideal for presentation to customers. (See change proposal.)

min_headway_minutes

Experimental

Included (some records)

For a frequency-based route, provides the highest frequency (lowest headway).

shapes.txt

 

Field Name

GTFS Spec

Status

Notes

shape_id

Required

Included

shape_pt_lat

Required

Included

shape_pt_lon

Required

Included

shape_pt_sequence

Required

Included

shape_dist_traveled

Optional

Included

stop_attributes.txt

Defined by GTFS+

 

Field Name

GTFS Spec

Status

Notes

stop_id

Experimental

Included

stop_city

Experimental

Included (some records)

stop_times.txt

 

Field Name

GTFS Spec

Status

Notes

trip_id

Required

Included

arrival_time

Required

Included

departure_time

Required

Included

stop_id

Required

Included

stop_sequence

Required

Included

stop_headsign

Optional

Included (some records)

pickup_type

Optional

Included

drop_off_type

Optional

Included

shape_dist_travelled

Optional

Included

timepoint

Optional

Included

continuous_stops

Experimental

Included

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. (See change proposal.)

area_id

Experimental

Included (some records)

Used for GTFS-Flex 

service_area_radius

Experimental

Included (some records)

Used for GTFS-Flex 

stops.txt

 

Field Name

GTFS Spec

Status

Notes

stop_id

Required

Included

stop_code

Optional

Included

platform_code

Experimental

Included (some records)

Used to distinguish between multiple platforms at rail stations. (See Google Maps extensions.)

stop_name

Required

Included

stop_desc

Optional

Included (some records)

stop_lat

Required

Included

stop_lon

Required

Included

zone_id

Optional

Included (some records)

stop_url

Optional

Included (some records)

location_type

Optional

Included

parent_station

Optional

Included (some records)

stop_timezone

Optional

Included

position

Experimental

Included (some records)

Can be used to show position of a stop on a block.

direction

Experimental

Included (some records)

Can be used to show direction of travel served by a stop.

wheelchair_boarding

Optional

Included

Timetable_stop_order.txt

Used for GTFS-to-HTML

 

Field Name

GTFS Spec

Status

Notes

timetable_id

Experimental

Included

stop_id

Experimental

Included

stop_sequence

Experimental

Included

stop_name

Experimental

Included

connected_routes

Experimental

Included

Timetables.txt

Used for GTFS-to-HTML

 

Field Name

GTFS Spec

Status

Notes

timetable_id

Experimental

Included

route_id

Experimental

Included

direction_id

Experimental

Included (some records)

start_date

Experimental

Included

end_date

Experimental

Included

monday

Experimental

Included

tuesday

Experimental

Included

wednesday

Experimental

Included

thursday

Experimental

Included

friday

Experimental

Included

saturday

Experimental

Included

sunday

Experimental

Included

route_label

Experimental

Included

service_note

Experimental

Included

direction_label

Experimental

Included

orientation

Experimental

Included

transfers.txt

 

Field Name

GTFS Spec

Status

Notes

from_stop_id

Required

Included

to_stop_id

Required

Included

transfer_type

Required

Included

min_transfer_time

Optional

Included (some records)

trips.txt

 

Field Name

GTFS Spec

Status

Notes

route_id

Required

Included

service_id

Required

Included

trip_id

Required

Included

trip_headsign

Optional

Included

trip_short_name

Optional

Included

direction_id

Optional

Included

block_id

Optional

Included

shape_id

Optional

Included

wheelchair_accessible

Optional

Included (some records)

bikes_allowed

Optional

Included (some records)

trip_type

Experimental

Included (some records)

Can be used to note Express or Limited trips.