Feature Plan - NeTEx updates (2025 Q2)
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.
These small change list in our products don’t reflex all updates in the NeTEx XML Schema Definition but only required changes to provide valid NeTEx files. Please visit the NeTEx documentation for a whole changelog
In accordance with our Product Policy, all enRoute SaaS products are or will be updated to match these NeTEx changes.
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">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"/>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>