All our SaaS products have been updated with the releases associated with this Sprint 145:

Ara SaaS has been updated on May 31, 2026
Chouette SaaS has been updated on Jun 2, 2026

Chouette

Associate a Group of Line to a Network

The user can associate a Line Group with a Network:

Import/Export OccupancyLevel/OccupancyPercentage associated to NeTEx Service Journeys

As part of the Feature Plan - Planned Vehicle Journey Occupancy, the user can import and export NeTEx Service Journeys with optional occupancy attributes:

<ServiceJourney id="AAMV1" version="any">
  <Name>AAMV1</Name>
  <occupancies>
    <OccupancyView id="occ" version="any">
      <OccupancyLevel>fewSeatsAvailable</OccupancyLevel>
      <OccupancyPercentage>80</OccupancyPercentage>
    </OccupancyView>
  </occupancies>
  <dayTypes>
    <DayTypeRef ref="chouette:TimeTable:dc120ad9-090c-4358-92bd-96a7b91b34fb:LOC" version="any"/>
  </dayTypes>
  <JourneyPatternRef ref="chouette:JourneyPattern:ca809292-588a-4bf9-9df5-4d6fbaa6f1da:LOC" version="any"/>
  <passingTimes>
    <TimetabledPassingTime id="time1" version="any">
      <StopPointInJourneyPatternRef ref="chouette:StopPointInJourneyPattern:ca809292-588a-4bf9-9df5-4d6fbaa6f1da-3500a177-6395-4c14-b57e-ee5757768336:LOC" version="any"/>
      <ArrivalTime>08:00:00</ArrivalTime>
      <ArrivalDayOffset>0</ArrivalDayOffset>
      <DepartureTime>08:00:00</DepartureTime>
      <DepartureDayOffset>0</DepartureDayOffset>
      <occupancies>
        <OccupancyView id="occ1" version="any">
          <OccupancyLevel>fewSeatsAvailable</OccupancyLevel>
          <OccupancyPercentage>80</OccupancyPercentage>
        </OccupancyView>
      </occupancies>
    </TimetabledPassingTime>
    <TimetabledPassingTime id="time2" version="any">
      <StopPointInJourneyPatternRef ref="chouette:StopPointInJourneyPattern:ca809292-588a-4bf9-9df5-4d6fbaa6f1da-7d74004f-dc79-4d81-9687-affde08f5bfa:LOC" version="any"/>
      <ArrivalTime>09:00:00</ArrivalTime>
      <ArrivalDayOffset>0</ArrivalDayOffset>
      <DepartureTime>09:00:00</DepartureTime>
      <DepartureDayOffset>0</DepartureDayOffset>
    </TimetabledPassingTime>
  </passingTimes>
</ServiceJourney>

The OccupancyLevel/OccupancyPercentage attributes can be associated to:

the whole ServiceJourney
and/or each TimetabledPassingTime (to override the ServiceJourney values if they exist)

Allow several Macros/Controls in Post Import Processing Rules

The user can associate several Workbench or Workgroup Rules as Post Import. In this case, the Import will be associated with all these processings.

Define allowed Stop Area Type in Stop Area Provider

As part of the Feature Plan - Provider restrictions, the user can define which Stop Area types are allowed into a Stop Area Provider:

This Stop Area Provider can be only associated with Stop Areas of the given types.

Manage Particular-Referent link across Providers with NeTEx import

The user can manage a particular-referent link by using the NeTEx attribute derivedFromObjectRef even if the particular and the referent models are associated with the same Provider.

<Quay id="referent">
  <Name>Referent Sample</Name>
</Quay>
<Quay id="particular" derivedFromObjectRef="referent"/>

The “Ignore Particular resources” NeTEx import option is improved to manage particular-referent links (and only this information).

Ara

Search into Control messages

The user can search in Control Messages:

Manage Notes on Vehicle Journeys

When Ara collects a MonitoredVehicleJourney in SIRI StopMonitoring, an optional JourneyNote element should be stored as a raw attribute JourneyNote in the associated Vehicle Journey.

When the Vehicle Journey is broadcast (only in StopMonitoring), the associated MonitoredVehicleJourney should contain the raw attribute value if exists.

<siri:MonitoredStopVisit>
  <!-- ... -->
  <siri:MonitoredVehicleJourney>
    <siri:LineRef>11A</siri:LineRef>
    <siri:FramedVehicleJourneyRef>
      <siri:DataFrameRef>1.0</siri:DataFrameRef>
      <siri:DatedVehicleJourneyRef>10041060</siri:DatedVehicleJourneyRef>
    </siri:FramedVehicleJourneyRef>
    <!-- ... -->
    <siri:JourneyNote>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vivamus sit amet pharetra urna. Ut ornare felis non tellus gravida suscipit. Praesent condimentum mauris a erat hendrerit mollis.</siri:JourneyNote>
    <siri:Monitored>true</siri:Monitored>
    <siri:MonitoredCall>
      <!-- ... -->
      <siri:DepartureStatus>early</siri:DepartureStatus>
    </siri:MonitoredCall>
  </siri:MonitoredVehicleJourney>
</siri:MonitoredStopVisit>

Collect and broadcast notes/message using CDATA syntax

Ara should be able to collect and broadcast using the XML CDATA syntax the following 3 attributes:

SIRI VehicleMonitoring VehicleActivityNote
SIRI StopMonitoring JourneyNote
SIRI GeneralMessage MessageText

When Ara broadcasts such content, the CDATA syntax is automatically enabled when the < character is present in the attribute string.

Vehicle Monitoring sample

<siri:VehicleActivity>
  <siri:MonitoredVehicleJourney>
    <!-- ... -->
  </siri:MonitoredVehicleJourney>
  <siri:VehicleActivityNote><![CDATA[<bad/>]]></siri:VehicleActivityNote>
</siri:VehicleActivity>

Stop Monitoring sample

<siri:MonitoredStopVisit>
  <!-- ... -->
  <siri:MonitoredVehicleJourney>
    <siri:JourneyNote><![CDATA[<bad/>]]></siri:JourneyNote>
  </siri:MonitoredVehicleJourney>
</siri:MonitoredStopVisit>

General Message sample

<siri:GeneralMessage>
  <!-- ... -->
  <siri:Content xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="stif:IDFGeneralMessageStructure">
    <!-- ... -->
    <Message>
      <!-- ... -->
      <MessageText><![CDATA[<bad/>]]></MessageText>
    </Message>
  </siri:Content>
</siri:GeneralMessage>