Chouette can export a dataset into the GTFS format by following the below rules.

Export options

The Chouette GTFS Export contains 2 specific options :

• Prefer Referent Stop Areas : with this option, the GTFS export exports the referent stops areas when exists instead of the particular stop areas. See GTFS Stops section for details.

• Ignore Monomodal Stop Places with a single Quay : with this option, the GTFS export doesn’t export a GTFS parent station with only a single quay. See GTFS Stops section for details.

Export content

File 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.

GTFS identifiers

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

By default, the GTFS export uses the codespace “external” (used by default by the Chouette imports). For Stop Areas, Lines and Companies, the registration number is used as code (to be changed).

Duplicated codes

The export prevents automatically two GTFS resources to use the same code value. In this case, the Chouette unique identifier will be used in place. For example, a GTFS Trip can be identified by chouette:VehiculeJourney:868007fe-07f8-4e02-8615-2341ba5a82c4:LOC when the associated code can be used as unique value.

Selected Vehicle Journeys

According to the options, the export selects the Vehicle Journeys which must included into the exported data. These exported Vehicle Journeys guide Chouette to select all other kind of models which must be included in the export (time tables, journey pattern, route, stop areas, etc).

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 or each specific Stop Area 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 parents that has just one Stop Area child if the option “Ignore Monomodal Stop Places with a single Quay” is activated).

If the exported Stop Area as a referent Stop Place and the option “Prefer Referent Stop Areas” is activated, the Referent Stop Area will be exported at the place of the particular Stop Area.

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 :

• for the first TimeTable Period and included/excluded Dates, Chouette creates a GTFS Calendar and GTFS Calendar Dates with the same GTFS Service ID.

• if there is more than one Timetable Period, Chouette creates additional GTFS Calendars for each Timetable Period with a new GTFS Service ID.

Each GTFS Calendar are created with the following information:

Each GTFS Calendar Date are written in calendar_dates.txt :

When several GTFS Calendars / Services are required, the GTFS export will need to create several GTFS Trips. See GTFS Trips section.

GTFS Trips

For each exported Vehicle Journey and each GTFS Service require to export the associated TimeTables, 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.

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 Calendar Date for the excluded date

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

• A Calendar Date 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 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:

When the user exports Vehicle Journeys associated to a Line with the flag "On demand transportation", all associated GTFS Stop Times use the pickup type 2.

GTFS Transfers

For each Connection Link with both departure and arrival associated to the exported Stop Areas, Chouette creates a dedicated GTFS Transfer with the following information:

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 :