How are Vehicle Journeys managed in Chouette?
At various stages of building your transport offer, Chouette may in some cases create or merge vehicle journeys. Below, we explain some of the most common situations that lead to these changes.
Vehicle Journey Merge
You can import data in multiple formats: NeTEx, Neptune et GTFS.
Each import will create a dataset, and several datasets can be merged. Depending on the data, the merge process may decide to merge vehicle journeys if they follow the same route and, more specifically, have the same:
stop areas,
timetables.
In the example below, Chouette will merge two vehicle journeys into one, as they contain the same stops and timetables.
Creation of new vehicle journeys during GTFS export/publication
A vehicle journey defines the schedules for passing through the various stops on the journey pattern and is contained in the trips.txt file.
Let's start from the following premise: Chouette contains a vehicle journey linked to two calendars for the same period, but with different application days.
The GTFS format allows a vehicle journey to be linked to only one timetable. When you export your data, Chouette will therefore need to split journeys into two in order to comply. The data remains consistent: a journey has simply been created with a new identifier generated by Chouette due to the limitations of the GTFS format.
Managing vehicle journeys that don’t have the code selected in the GTFS publication
An automatic publication may have the option to define the code space for exported data:
In this case, Chouette will export the vehicle journey IDs (and other model IDs) with the value of the selected code space.
However, when a vehicle journey does not have the code requested by the publication, it will be exported with an ID generated by Chouette.
Managing duplicate vehicle journeys in GTFS export