Sprint 144
All our SaaS products have been updated on May 10, 2026 with the releases associated with this Sprint 144.
Chouette
Search Import messages
The user can search into all Import messages of a given import (not grouped by resource as in the default display):
The user can search among the Import messages by text, criticity and filename.
Manage Journey Pattern codes
The user can view and edit codes associated with each Journey Pattern:
New style for Validate/Yes buttons
A different color is used for buttons that really perform a change:
Submit button in forms
Yes button in confirmation modals
With this UX approach, the user can ensure that its Chouette usage is harmless.
Create by default Journey Pattern with “Default” name in GTFS import
When the user imports a GTFS file, the created Journey Patterns are named with the GTFS Trip headsign or, by default, “Default”.
The user can enrich the Journey Pattern Name/Destination by using the dedicated Macro Define Journey Pattern name or destination display.
Export Timetables with new code syntax
The user can select the option “Include Chouette ID in duplicated Timetable code (experimental)” to export/publish using the GTFS format.
In this case, the GTFS export will use a new GTFS identifier format to export a Timetable with a duplicated code value. The new format uses both the duplicated code value and the Chouette model unique identifier (in its uuid form).
The oldest Timetable is exported with the code value, the other Timetables with the same code are exported with a GTFS service id suffixed with the model uuid (<code>-<uuid>).
For example, for two Timetables with the same code value, two GTFS services will be created with service_id:
A2601-_GT1LMJV-L-Ma-J-V-01-2088A2601-_GT1LMJV-L-Ma-J-V-01-2088-ae0df228-4165-4a82-b7a4-832afb5d89c7
This experimental approach could be generalized to all models and both GTFS/NeTEx formats in the future
Use GTFS Trip short name only to define Vehicle Journey name
When the user imports a GTFS file, the imported Vehicle Journeys are named by using the GTFS Trip short_name. If this GTFS attribute is not defined, the Vehicle Journey name is empty.
Ara
New Exchange Search interface
The user can search among all real-time Exchanges performed in the last 30 days by using the refactored user interface:
The search form uses the same components as the Chouette search interfaces. The loading and paginating mechanisms have been improved.
Define Code Spaces for each Referential
The user can define the Code Spaces used in each real-time Referential:
For the moment, these code spaces are indicative. They are used in the search interfaces to select a code space to search by code (see below).
Search real-time Stop Areas
The user can search among real-time Stop Areas by name and by code:
Search real-time Vehicle Journeys
The user can search among real-time Vehiche Journeys by name (when defined) and by code:
Search real-time Lines
The user can search among real-time Lines by name and by code:
Manage Vehicle Notes in SIRI Vehicle Monitoring
When Ara collects a VehicleActivity in SIRI Vehicle Monitoring, an optional VehicleActivityNote element should be stored as a raw attribute VehicleActivityNote in the Vehicle.
<siri:VehicleActivity>
<siri:MonitoredVehicleJourney>
<!-- ... -->
</siri:MonitoredVehicleJourney>
<siri:VehicleActivityNote>dummy</siri:VehicleActivityNote>
</siri:VehicleActivity>When the Vehicle is broadcasted, the associated VehicleActivity should contain the raw attribute value if exists.