All our SaaS products are about to be updated with the releases associated with this Sprint 147.

Chouette

Find implicit Route stop sequence for complex NeTEx Route/Journey Patterns

The user can import NeTEx Route with Journey Patterns where the exact Stop Sequence is implicit. The Chouette import computes for each Route a stop sequence that is compatible with all Route / PointOnRoute and all Journey Patterns StopPointInJourneyPattern. For more details:

A new algorithm has been studied to cover more complex cases like:

A, B, A, B, C + A, B, C, D → A, B, A, B, C, D

The new algorithm is, for the moment, optional. It can be enabled by requesting the enRoute support team

Export to Ara parent and referent for Stop Area Group members

When the user exports a Stop Area Group, all its Stop Area members are now exported with their parent and referent Stop Areas.

Better support for “unexpected” NeTEx XML payloads

The shared component used by Chouette and Flamingo to read any NeTEx files has been massively tested, especially by using a fuzzing testing approach. Even on unexpected/invalid/strange NeTEx XML payloads, the NeTEx XML read avoids any error and is more secure.

By this work, the enRoute development team has contributed to many improvements in the underlying component:https://github.com/ohler55/ox/.

Export a NeTEx file with IDFM producer without alternate identifiers

But of the IDFM Producer specifications, when the user exports or publishes a NeTEx file using the IDFM producer, if the codes of exported models are not exported as NeTEx alternate identifiers.

New documentation about Vehicle Journeys scheduled around midnight

New documentation has been created about how Chouette handles Vehicle Journeys scheduled around midnight, in particular those that start before midnight and finish after midnight, as well as those that start after midnight: https://enroute.atlassian.net/wiki/x/AgAM3

Flamingo

New NeTEx releases and branches are provided as schema versions

Users can start a NeTEx validation by specifying new schema versions associated with NeTEx CEN releases and active branches:

v1.3.2associated with NeTEx release v.1.3.2: https://github.com/NeTEx-CEN/NeTEx/releases/tag/v1.3.2
v2.0.0associated with NeTEx release v.2.0.0: https://github.com/NeTEx-CEN/NeTEx/releases/tag/v2.0.0
v2.0, v2.1-wip associated with NeTEx branches, these schemas are periodically updated.

If the user uses the legacy schema versions:

when master is used, the v1.3.2schema version is used
when next is used, the v2.0 schema version is used

When users requests a schema validation without specifying a schema version, the v1.3.2 schema version is used by default (the v2.0.0 will be used by default in a new future).

secretary-client create validation --wait --include-schema --schema-version=v2.0.0 /path/to/netex.zip
secretary-client create validation --wait --include-schema --schema-version=v2.0 /path/to/netex.zip

Authorize resources for flexible service in IBOO Producer IBOO profile

The NeTEx resources required to describe a flexible service like BookingArrangement, FlexibleStopPlace or FlexibleStopAssignment are now authorized in the IBOO Producer Validation Ruleset.

Provide more precise line, column and filename information in Validation message

The user can retrieve the line, column and filename information for any NeTEx resource validated by a Flaming Validation Rule.

{
    "code": "service-journey-passing-times-chronology",
    "message": "Arrival time is before previous departure time",
    "resource": {
      "filename": "sample.xml",
      "line": 4850,
      "class": "TimetabledPassingTime",
      "column": 25
    },
    "criticity": "error"
  },

Better support for “unexpected” NeTEx XML payloads

The shared component used by Chouette and Flamingo to read any NeTEx files has been massively tested, especially by using a fuzzing testing approach. Even on unexpected/invalid/strange NeTEx XML payloads, the NeTEx XML read avoids any error and is more secure.

By this work, the enRoute development team has contributed to many improvements in the underlying component:https://github.com/ohler55/ox/.

Ara

Skip notes in SIRI broadcaster when associate setting is given

When a SIRI Stop Monitoring or Vehicle Monitoring connector broadcasts a Vehicle Journey or a Vehicle, the JourneyNote or VehicleActivityNote won't be included in the XML payload if the associated setting is enabled.

The user can use the following settings:

broadcast.siri.ignore_notes = true (all broadcasters will ignore notes)
broadcast.siri.stop_monitoring.ignore_notes = true (only SIRI Stop Monitoring broadcaster will ignore notes)
broadcast.siri.vehicle_monitoring.ignore_notes = true (only SIRI Vehicle Monitoring broadcaster will ignore notes)

Performance improvement in SIRI Stop Monitoring notification processing

The Ara SIRI Stop Monitoring notification processing has been improved. For a 2MB, our benchmark shows a processing time reduced from 350 ms to 20 ms.

In production, the Ara SaaS monitoring reports SIRI Stop Monitoring notifications larger than 10MB.

Performance improvement in Exchange historization

Ara SaaS logs several million exchanges daily. To improve their storage, the Exchange historization has been rewritten.

The user can see the request / request raw payload when their combined size is smaller than 9MB. Otherwise, only the smaller payload is saved (with the same limit of 9MB).

New documentation about referential reload

New documentation has been created about Ara data reload: Référentiel