Export structure

The export creates a zip containing the following csv files:

• agencies.txt

• stops.txt

• routes.txt

• trips.txt

• stop_times.txt

• calendars.txt

• shapes.txt

• transfers.txt

These files are compliant with the GTFS standard as defined in the Google’s official documentation.

Export options

GTFS Export contains 3 options :

• Duration in days : When user selects a duration, only the Vehicle Journeys with a TimeTable including the export period are selected.

• Prefer Referent Stop Areas : This option permits to export Stop Places (Stop Area referent) and not Quays

• Ignore Monomodal Stop Places with a single Quay : This option is used in GTFS Stops and permits to export only Stop Places that have at least 2 Quays ​

Export content

Each export is associated with a codespace. This codespace is used to find code value into Chouette models to identify the GTFS resources.

GTFS Agencies

For each Company associated to an exported Vehicle Journey (or the Line of this Vehicle Journey), Chouette create a GTFS Agency in agencies.txt with the following information:

If the Chouette Company registration number is empty, the Company ID is used as agency_id value.

A default GTFS Agency can be exported by Chouette, if one of the exported Vehicle Journeys isn’t associated to a Company or a Line associated to a Company. This default GTFS Agency uses these values:

A warning message is added to the Export when the default GTFS Agency is used.

GTFS Stops

For each Stop Area associated to a Route of an exported Vehicle Journey, Chouette creates a GTFS Stop in stops.txt. Non commercial Stop Areas (borders, etc) are ignored by the GTFS export.

Parents of exported Stop Areas are exported (except parent that has just one Stop Area if Ignore Monomodal Stop Places with a single Quay option is activated).

Each GTFS Stop uses the following information:

GTFS Route

For each Line associated to an exported Vehicle Journey, Chouette creates a GTFS Route in routes.txtwith the following information:

The GTFS route type value is selected according to the Chouette Line transport mode according to this mapping:

GTFS Calendar and GTFS Calendar Date (Service)

For each Timetable including in the exported period associated to exported Vehicle Journeys :

• if there is only one Timetable Period and some Timetable Dates, Chouette creates a GTFS Calendar and GTFS Calendar Dates with the same GTFS Service ID

• if there is more than one Timetable Period and some Timetable Dates, Chouette creates

  • a GTFS Calendar for the first Timetable Period and all GTFS Calendar Dates with the same GTFS Service ID

  • GTFS Calendars for each Timetable Period with a new GTFS Service ID

Each GTFS Calendar are written in calendars.txt :

Each GTFS Calendar Date are written in calendar_dates.txt :

For example:

• A Timetable A on week days with two periods and an excluded date (on the first period)

• A Timetable B with only included dates

• A Vehicle Journey 1 which uses the two timetables A & B

• A Vehicle Journey 2 which uses only the Timetable B

These models should be exported as:

• A Calendar (service_id A1) for the first period of Timetable A and an associated CalendarDate for the excluded date

• A Calendar (service_id A2) for the second period of Timetable A

• A CalendarDate for each included dates of Timetable B (with the same service_id B)

• A Trip for Vehicle Journey 1 associated to the service_id A1

• A Trip for Vehicle Journey 1 associated to the service_id A2

• A Trip for Vehicle Journey 1 associated to the service_id B

• A Trip for Vehicle Journey 2 associated to the service_id B

GTFS Trips

For each exported Vehicle Journey, Chouette creates a dedicated GTFS Trip in trips.txt with the following information:

A single Chouette Vehicle Journey can be exported into several GTFS Trip because of GTFS format limitations on service/calendar description.

If the “gtfs” code is unique in the GTFS export scope, it will be used as value for the GTFS Trip ID. Otherwise, the GTFS Trip ID uses the objectid.

GTFS Stop Times

For each Vehicle Journey At Stop associated to exported Vehicle Journey, Chouette creates a dedicated GTFS Stop Time in stop_times.txt with the following information:

GTFS Transfers

For each Connection Link with both departure and arrival associated to exported Routes, Chouette creates a dedicated GTFS Transfer in transfers.txt with the following information:

transfer_type is always set to 2 as defined in GTFS specification :

• 0 or empty - Recommended transfer point between routes.

• 1 - Timed transfer point between two routes. The departing vehicle is expected to wait for the arriving one and leave sufficient time for a rider to transfer between routes.

• 2 - Transfer requires a minimum amount of time between arrival and departure to ensure a connection. The time required to transfer is specified by min_transfer_time.

• 3 - Transfers are not possible between routes at the location.

GTFS Shapes

For each Shape associated to a Journey Pattern and linked to exported Vehicle Journeys, Chouette creates a dedicated GTFS Shape. For each geometry point of the Shape it creates an element in shapes.txt with the following information :

If the “gtfs” code is unique in the GTFS export scope, it will be used as value for the GTFS Shape ID. Otherwise, the GTFS Shape ID uses the uuid.