1 Chouette
2 Ara
3 Chouette Valid
- 3.1 Technical upgrade / Performance improvement
- 3.2 Documentation

All our SaaS products are about to be updated with the releases associated to this Sprint 126:

Chouette SaaS has been updated on Apr 28, 2025
Ara SaaS, Chouette Valid are going to be updated on Apr 30, 2025

Chouette

Define a subgroup in Chart

The user can create a chart by subgrouping the models.

For example, the user can see Daily Service Counts by Date and Lines:

Service Counts by Date and Lines

Or the user can see Stop Areas by Created date and Area type:

Edit Route to include flexible stops

The user can add a Flexible Stop Point into a Route:

When a Flexible Stop Point is used, it can be associated to a Flexible Stop Area (and any other Stop Area). In contrast, standard (non-Flexible Stop) Points can’t be associated with Flexible Stop Areas, but any other type of Stop Areas (Quay, etc.).

Edit passing time range in Vehicle Journeys flexible stops

When a user visits or edits the Vehicle Journeys associated to a Flexible Route, the Flexible Stop Points are associated to a Time Of Day range (instead of an arrival/departure time):

Chouette-Vehicle-journeys-on-route-Inbound-04-29-2025_02_51_PM.png

The user can use advanced editing tools on flexible Vehicle Journeys:

create a new Vehicle Journey
clone a Vehicle Journey into several new Vehicle Journeys
shift the schedules in time
copy/paste schedules

Import GTFS location groups as Stop Area Flexible Area

For each GTFS Location Group, the Chouette import updates or creates a Stop Area with:

the type Flexible Stop Area
a Flexible Area with the associated Stop Areas

See https://gtfs.org/documentation/schedule/reference/#location_groupstxt

Import Stop Area Flexible Area in NeTEx

When the user imports a FlexibleStopPlace NeTEx resource, a Flexible Stop Area is updated or created:

<FlexibleStopPlace id='zone-tad-1' version="any">
  <Name>FTS Zone 1</Name>
  <Centroid>
    <Location>
      <Longitude>7.7064377815</Longitude>
      <Latitude>48.5331765019</Latitude>
    </Location>
  </Centroid>
  <areas>
    <FlexibleArea version="any" id="zone-tad-1-area">
      <members>
        <QuayRef ref="quay-1" version="any"/>
        <QuayRef ref="quay-2" version="any"/>
      </members>
    </FlexibleArea>
  </areas>
</FlexibleStopPlace>

Only the first FlexibleArea is read, other FlexibleArea resources are ignored. Only FlexibleArea with QuayRef members are supported.

Export Stop Area with a NeTEx TarifZoneRef for each Fare Zone

When the user exports in NeTEx a Stop Area associated with one or more Fare Zones, the associated NeTEx StopPlace/Quay should include a FareZoneRef for each associated Fare Zone:

<Quay>
  <!-- ... -->
  <tariffZones>
	<FareZoneRef ref="first" version="any"/>
	<FareZoneRef ref="second" version="any"/>
  </tariffZones>
</Quay>

New Home Page layout

The Chouette SaaS home layout has been refactored to match the new enroute website: Take control of your mobility data! - enRoute. Some improvements are also present in the global design.

Documentation

The Chouette SaaS documentation has been improved, especially these topics:

NeTEx improvements in next Release

As previously announced, the next Chouette SaaS release will include several improvements in the NeTEx file format:

Several changes are required in the NeTEx payload created by our SaaS tools to match fixes in the NeTEx current XML Schema Definition or to anticipate changes its next version. See Feature Plan - NeTEx updates (2025 Q2) for details
The French NeTEx profile will be updated to match the latest structure defined by the French Workgroup Group: https://github.com/etalab/transport-profil-netex-fr/issues/121

Ara

Broadcast Situation according broadcast period for SIRI SX subscriptions

When a SIRI Situation Exchange subscription is active, a Situation should be broadcasted if the SIRI subscription period matches the subscription Time Scope (same logic than Sprint 123 | Improve Situations & General Messages broadcast period).

Create code from another with a Macro

The user can create a code into a Target Code Space by using the code value from a Source Code Space and a specified Target Pattern. The macro is only executed when the model is created.

For example, the user can create Stop Areas “external” code from “internal” code used by CAD/AVL system.

Ara Macros are in beta access. Contact our support team to use macros

Control model is expected in static data

The user can define a “Model is present in Static Data” by selecting a target model (Stop Area, Line, Vehicle Journey or Operator).

If a such model is created (outside the referential/database loading), the control creates a message:

The StopArea/Line/vehicle Journey/Operator ‘<name>’ was not expected into static data
L’arrêt/La ligne/La course/L’opérateur ‘<name>’ n'était prévu(e) dans les données théoriques

Ara Controls are in alpha access. Contact our support team to know details

New Home Page layout

The Ara SaaS home layout has been refactored to match the new enroute website: Take control of your mobility data! - enRoute.

Manage SIRI Vehicle Monitoring notifications with new SIRI Go library

Ara SaaS is now parsing millions of Vehicle Monitoring notifications received per day using the new enRoute open source library SIRI Go.

Chouette Valid

Technical upgrade / Performance improvement

The Chouette Valid SaaS platform has been updated to use the Rails Framework 7.2 and benefits from the latest performance improvements.

Documentation

The Ara SaaS documentation has been improved, especially these topics: