All our SaaS products have been be updated with the releases associated to this Sprint 129.

Chouette

Prioritize Publications

The user can define the priority associated to each Publication. When publications are started automatically (after an Aggregate, for example), the Publications are performed in this order.

Edit publication priority

A Publication with the priority 1 has the higher processing priority.

Publish to IDFM ICAR API

The user can select the ICAR API Destination to send the published file.

Publish to ICAR API

The user needs to define the attributes required by the ICAR API:

a Site ID
a Site Name
a ICAR API token

The user can change the file type (Total/T, Partial/P, Deletion/S) used to create the file name.

Export BookingArrangments/FlexibleStopPlaces in IBOO NeTEx profiles

BookingArrangements and FlexibleStopPlaces were included in IDFM Profiles, and avaliable on NeTEx export now. A new /commun.xml file is used to store BookingArrangement and FlexibleStopPlace resources.

<?xml version="1.0" encoding="UTF-8"?>
<PublicationDelivery xmlns="http://www.netex.org.uk/netex" version="1.04:FR1-NETEX-1.6-1.8">
  <PublicationTimestamp>2025-03-20T06:59:36Z</PublicationTimestamp>
  <ParticipantRef>FR1_OFFRE</ParticipantRef>
  <dataObjects>
    <GeneralFrame id="FR1:GeneralFrame:NETEX_COMMUN-20250320T065936Z:LOC" version="1.8" dataSourceRef="FR1-OFFRE_AUTO">
      <TypeOfFrameRef ref="FR1:TypeOfFrame:NETEX_COMMUN:"/>
      <members>
        <BookingArrangement version="any" id="standard">
          <keyList>
            <KeyValue typeOfKey="ALTERNATE_IDENTIFIER">
              <Key>regional</Key>
              <Value>booking-arrangement-1</Value>
            </KeyValue>
          </keyList>
          <BookingContact>
            <Phone>+33 1 23 45 67 89</Phone>
            <Url>https://example.com/info</Url>
          </BookingContact>
          <BookingMethods>callOffice</BookingMethods>
          <BookingAccess>public</BookingAccess>
          <BookWhen>untilPreviousDay</BookWhen>
          <BuyWhen>beforeBoarding</BuyWhen>
          <LatestBookingTime>16:30:00</LatestBookingTime>
          <MinimumBookingPeriod>PT30M</MinimumBookingPeriod>
          <BookingUrl>https://example.com/booking</BookingUrl>
          <BookingNote>
            Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed ac elit
            suscipit, volutpat ipsum at, dignissim velit. Nullam feugiat, orci
            nec egestas placerat, ligula dolor tempus velit
          </BookingNote>
        </BookingArrangement>

        <FlexibleStopPlace id='zone-tad-1' version="any">
          <Name>FTS Zone 1</Name>
          <areas>
            <FlexibleArea version="any" id="zone-tad-1-area">
              <members>
                <QuayRef ref="FR::Quay:24383:FR1" version="any"/>
                <QuayRef ref="FR::Quay:39542:FR1" version="any"/>
              </members>
            </FlexibleArea>
          </areas>
        </FlexibleStopPlace>
      </members>
    </GeneralFrame>
  </dataObjects>
</PublicationDelivery>

Add Line model for macro "Define Referent attribute from Particulars value"

Macro “Define Referent attribute from Particulars value” can be used on target model Stop area and Company. Now, Chouette manages a new target model Line on these attributes :

active_from
active_until
color
number
published_name
text_color
transport_mode
transport_submode
url

Use Line model for macro "Define Referent attribute from Particulars value"

Display Public GraphQL URL on a Publication API page

Display Public GraphQL URL

A Public GraphQL URL is displayed on Publication API page to clearly separate Public URL and Public GraphQL URL.

Import NeTEx StopPointInJourneyPattern ForAlighting/Boarding as StopPoint attributes

The user can import NeTEx StopPointInJourneyPattern with ForAlighting/ForBoarding attributes. In this case, the created Chouette StopPoint will have the associated For Boarding For Alighting attributes (Normal / Forbidden).

Ara

Improve all SIRI Payload used by Ara

SIRI payloads created by Ara have been improved to make all of them valide according to the latest SIRI XML Schema.

Hundreds of automatic scenarios in our QA process ensure that any SIRI XML payload respects the SIRI XSD (or fail). Both SOAP and “raw” SIRI payloads are tested.