GTFS Schedule Developer Release Notes
Introduction
The current GTFS provides the following eight files:
- agency.txt
- calendar.txt
- calendar_dates.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trip.txt
The new GTFS provides the following nine files:
- feed_info.txt
- agency.txt
- calendar.txt
- calendar_dates.txt
- routes.txt
- shapes.txt
- stops.txt
- stop_times.txt
- trips.txt
OC Transpo is creating a new GTFS schedule file to better conform to the MobilityData General Transit Feed Specification standard and prepare for publishing of a GTFS-RT feed in the near future.
The feed_info.txt file is currently configured for English only. OC Transpo is a bi-lingual transit agency and will introduce support for French soon as per the GTFS specifications using the translations.txt file.
Added file(s) in the new GTFS export
feed_info.txt
The following fields should have values:
- feed_publisher_name
- feed_publisher_url
- feed_lang
- start_date
- feed_end_date
- feed_version
- feed_contact_url
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#feed_infotxt
Existing files in the new GTFS export
Existing files in the new GTFS export:
agency.txt
Fields with new values
| Field | Value |
|---|---|
| agency_id | 1 |
| agency_phone | 613-560-5000 |
| agency_fare_url | https://www.octranspo.com/en/fares |
| agency_lang | en |
Fields with modified values
| Field | Current | New |
|---|---|---|
| agency_timezone | America/Montreal | Canada/Eastern |
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#agencytxt
calendar.txt
No changes to this file.
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#calendartxt
calendar_dates.txt
No changes to this file.
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#calendar_datestxt
routes.txt
Fields with new values
| Field | Value |
|---|---|
| agency_id | 1 |
| route_long_name | General name that describes the directions the route travels. Directions will be separated by a set of angle brackets: <>. |
| route_url | https://www.octranspo.com/en/plan-your-trip/schedules-maps?sched-lang=en |
Fields with modified values
| Field | Modification |
|---|---|
| route_id | Routes will be ordered based on the value as a string instead of an integer to accommodate alphanumeric route_ids. |
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#routestxt
shapes.txt
No changes to this file.
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#shapestxt
stops.txt
Fields with modified values
| Field | Modification |
|---|---|
| stop_id | Stop_id will be a 4-character numeric value instead of a 5 character alphanumeric value. |
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#stopstxt
stop_times.txt
Fields with new values
| Field | Value |
|---|---|
| stop_headsign | Optional value will be available only when trip head-sign or destination for the trip has an override for the stop. This occurs when the headsign changes mid-trip. |
| shape_dist_traveled | Distance travelled along the shape |
| timepoint | 0 or 1 |
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#stop_timestxt
trips.txt
Fields with new values
| Field | Value |
|---|---|
| bikes_allowed | 1 |
| wheelchair_accessible | 1 |
Field with modified values
| Field | Modification |
|---|---|
| trip_headsign | This field will reflect the trip specific destination instead of the general route direction name. The direction name will be moved to the route_long_name field within the routes.txt file |
For reference on the content of this file refer to https://gtfs.org/schedule/reference/#tripstxt