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

Chouette SaaS has been updated on May 18, 2025

Chouette

Manage a Point Of Interest Description

The user can add a Description for each Point Of Interest:

The attribute can be imported and exported in NeTEx:

<PointOfInterest version="any" id="sample">
  <Name>Point of Interest Sample</Name>
  <Description>Description Sample</Description>
  <Centroid>
    <Location>
      <Latitude>48.5331765019</Latitude>
      <Longitude>7.7064377815</Longitude>
    </Location>
  </Centroid>

  <Url>http://www.barpark.co.uk</Url>
</PointOfInterest>

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 a fixed departure/arrival Time Of Day).

The Show and Edit arrival times function is enabled (and disabled) by default.

The Flexible Stop Points are displayed with an icon and Time Of Day inputs are separated by a dedicated icon.

The user can use all advanced edit functions provided by Chouette SaaS, for example:

create a new Vehicle Journey
time shift all passing times of a Vehicle Journey
duplicate/clone a new Vehicle Journey into one or several new Vehicle Journeys

Select a Booking Arrangement in Journey Pattern editor

The user can select a Booking Arrangement associated to a Journey Pattern (which overrides the Booking Arrangement associated to the Line):

Import GTFS Flexible Stop Times

The user can import GTFS Stop Times which uses flexible attributes.

For the moment, for each GTFS Stop Time, the associated Stop Point is flexible if start_pickup_drop_off_window/end_pickup_drop_off_window are defined. This time of day range is stored in the Vehicle Journey At Stop EarliestDepartureTime/LatestArrivalTime.

In this case, if the pickup_type/drop_off_type is 2, the Chouette ForBoarding/ForAligthing is Normal. Otherwise, the ForBoarding/ForAligthing attribute is forbidden.

If the GTFS Stop Time stop_id is defined, the GTFS import looks up a Chouette Stop Area which is not a Flexible Stop Area. If the location_group_id is defined, the import looks up only a Flexible Stop Area.

References

https://gtfs.org/documentation/schedule/reference/#stop_timestxt

Export Flexible Stop Point with flexible NeTEx StopPointInJourneyPattern

When the user exports a Route where a Stop Point is flexible, the Chouette NeTEx export contains a NeTEx StopPointInJourneyPattern with FlexiblePointProperties:

<StopPointInJourneyPattern id="sample" order="2" version="any">
  <ScheduledStopPointRef ref="scheduled-stop-point-zone-tad-1" version="any"/>
  <FlexiblePointProperties>
    <PointStandingForAZone>true</PointStandingForAZone>
    <ZoneContainingStops>true</ZoneContainingStops>
  </FlexiblePointProperties>
</StopPointInJourneyPattern>

Import/Export more extended Bus GTFS Route Type

The user can import/export a GTFS Route with one of this extended Route Types: 702, 705, 711, 714 and 715.

Each route type will be converted to/from a Chouette/NeTEx Bus transport submode:

Chouette / NeTEx Bus transport submode	GTFS Route Type

Chouette / NeTEx Bus transport submode	GTFS Route Type
Bus / Express Bus	702
Bus / Night Bus	705
Bus / Shuttle Bus	711
Bus / Rail Replacement Bus	714
Bus / Demand And Response Bus	715

Reference

https://developers.google.com/transit/gtfs/reference/extended-route-types

Report invalid content on Source Retrieval

When a Source retrieves a content which doesn’t seem to be an importable file (like an HTML page, or an invalid ZIP file, etc.), the user gets the message “Invalid Content” on its retrieval:

In this case, check the content returned by the given URL.

NeTEx improvements

As previously announced, this Chouette SaaS release includes several improvements in the NeTEx file format.

These changes are only side technical changes which should not have impact on data consumers.

Order must be 1 or greater

The NeTEx resources like PassengerStopAssignment, DayTypeAssignment should use an order = 1 (instead of 0):

<!-- Invalid -->
<PassengerStopAssignment id="..." version="any" order="0">
<DayTypeAssignment id="..." version="any" order="0">
<!-- Valid -->
<PassengerStopAssignment id="..." version="any" order="1">
<DayTypeAssignment id="..." version="any" order="1">

TimetabledPassingTime must have an identifier

Each NeTEx TimetabledPassingTime embedded into ServiceJourney must have a id and a version attributes:

<!-- Invalid -->
<TimetabledPassingTime>
  <ArrivalTime>06:35:00</ArrivalTime>
  <DepartureTime>06:37:00</DepartureTime>
</TimetabledPassingTime>
<!-- Valid -->
<ServiceJourney id="vehicleJourney-1" version="any">
  <Name>Vehicle Journey Sample</Name>
  <dayTypes>
    <DayTypeRef ref="daytype-1" version="any"/>
  </dayTypes>
  <JourneyPatternRef ref="journeypattern-1" version="any"/>
  <passingTimes>
    <TimetabledPassingTime id="vehicleJourney-1-1" version="any">
      <ArrivalTime>06:30:00</ArrivalTime>
      <DepartureTime>06:30:00</DepartureTime>
    </TimetabledPassingTime>
    <TimetabledPassingTime id="vehicleJourney-1-2" version="any">
      <ArrivalTime>06:35:00</ArrivalTime>
      <DepartureTime>06:37:00</DepartureTime>
    </TimetabledPassingTime>
  </passingTimes>
</ServiceJourney>

A DataSource must be associated to each dataSourceRef

When a NeTEx resource has a dataSourceRef attribute, a DataSource with the associated identifier should exist in the NeTEx document.

<!-- Invalid -->
<Route id="sample" version="any" dataSourceRef="dummy"/>
<Quay id="sample" version="any" dataSourceRef="dummy"/>

<!-- Valid -->
<DataSource id="dummy"/>
<Route id="sample" version="any" dataSourceRef="dummy"/>
<Quay id="sample" version="any" dataSourceRef="dummy"/>

Because of a NeTEx XSD validation limitation, these DataSource resources are added in every XML documents (into a same ZIP archive, for example).

Export using the up-to-date French Profile file structure

When the user selects NeTEx French Profile, Chouette creates a NeTEx file organized according to the latest work performed by the French Workgroup Group: https://github.com/etalab/transport-profil-netex-fr/issues/121.

Data consumers, which already used files produced by Chouette SaaS, have only minor changes to perform:

the ZIP entries are now down cased (for example, stop.xml instead of STOP.xml, line_a.xml instead of LINE-A.xml)
Frames into the NETEX_LIGNE Composite Frame have been reorganized because of a profile update: https://github.com/etalab/transport-profil-netex-fr/issues/113. But the contained NeTEx resources are the same.

Technical updates

In background to our functional changelogs, the enRoute team is performing a very large technical updates on the Chouette SaaS platform. This work is close to completion and will allow us to improve performance and features during the next Quarter.

Ara

WORK IN PROGRESS