Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Export options

GTFS Export contains 3 options :

...

2 specific options :

...

  • 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

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:

...

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

Details

Chouette Stop Area

stop_id

GTFS Stop ID

registration_number or by default objectid

stop_name

Name

name

stop_lat

Latitude

latitude

stop_lon

Longitude

longitude

stop_desc

Comment

comment

stop_url

URL

url

location_type

0 for Quay,

1 for other Stop Area type

0 when area_type is Quay

(zdep)

or 1

parent_station

Associated Parent Stop ID

registration_number or by default objectid of the StopArea selected as parent

stop_timezone

Time Zone

time_zone if there is no parents

wheelchair_boarding

0 when not present or false

1 when true

mobility_restricted_suitability

GTFS Route

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

GTFS Route

Details

Chouette Line

route_id

GTFS Route ID

registration_number or by default objectid

agency_id

Associated GTFS Agency ID

Company registration_number or by default objectid

or chouette_default if no associated Company

route_short_name

Number

number

route_long_name

Published Name

published_nameor by default name (set if the value is different from route_short_name or blank otherwise)

route_desc

Comments

comment

route_type

Transport mode

See values below

route_url

URL

url

route_color

Line color

color

route_text_color

Text color

text_color

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

...

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

  • if there is only one Timetable Period and some Timetable for the first TimeTable Periodand 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 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

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

Each GTFS Calendar are written in calendars.txt created with the following information:

GTFS Calendar

Details

Chouette TimeTablePeriodTimeTable Period

service_id

GTFS Service ID

objectid

monday

if monday is selected

days_of_week

tuesday

if tuesday is selected

wednesday

if wednesday is selected

thursday

if thursday is selected

friday

if friday is selected

saturday

if saturday is selected

sunday

if sunday is selected

start_date

Period start date

period_start

end_date

Period end date

period_end

...

GTFS Calendar Date

Details

Chouette TimeTableDateTimeTable Date

service_id

GTFS Service ID

objectid

date

Date

date

exception_type

date is included : 1

date is excluded : 2

in_out

For example:

...

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:

GTFS Trip

Details

Chouette Vehicle Journey

trip_id

GTFS Trip ID

code or objectid. The GTFS Service id is added for additional GTFS Trips.

route_id

Associated GTFS Route ID

registration_number or by default objectid

service_id

Associated GTFS Service ID

trip_short_name

Published Name

published_journey_name

direction_id

0 for outbound Route or 1

Route wayback

shape_id

Associated GTFS Shape id

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

...

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

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

  • A CalendarDate 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 Trips

...

GTFS

...

Details

...

Chouette Vehicle Journey

...

trip_id

...

GTFS Trip ID

...

route_id

...

Associated GTFS Route ID

...

registration_number or by default objectid

...

service_id

...

Associated GTFS Service ID

...

trip_short_name

...

Published Name

...

published_journey_name

...

direction_id

...

0 for outbound Route or 1

...

Route wayback

...

shape_id

...

Associated GTFS Shape id

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 Stop Time

Details

Chouette Vehicle Journey At Stop

trip_id

Associated GTFS Trip IDcode or uuid

arrival_time

Arrival Time

arrival_timewith Timezone

departure_time

Departure Time

departure_time with Timezone

stop_id

GTFS Stop ID

the Route Stop Area by default
or the specific Stop Area

stop_sequence

Position

GTFS Transfers

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

GTFS Transfer

Details

Chouette Connection Link

from_stop_id

Associated GTFS Stop ID

departure_id

to_stop_id

Associated GTFS Stop ID

arrival_id

transfer_type

2

min_transfer_time

Minimum Transfer Time

default_duration

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

...

0 or empty - Recommended transfer point 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 :

GTFS Shape

Details

Chouette Shape

shape_id

GTFS Shape ID

code or uuid

shape_pt_lat

Shape point latitude

latitude

shape_pt_lon

Shape point longitude

longitude

shape_pt_sequence

Shape point position

position

...