In the course of the upcoming migration, the logic for generating the SLOID (stop_id) adjusted.
The aim is a more consistent and unambiguous representation of step and track information in the affected formats – GTFS, NeTEx* and OJP 1.0 and 2.0 – to be created.
*NeTEx is not affected by the subsequent generation of the SLOID. In NeTEx, the original SLOID continues to be output as a key (SLOID) / value (ch:1:sloid:y:z) pair for Steps.
The migration to SLOID will only change in NeTEx that for stops additionally the SLOID is output as a key (SLOID) / value (ch:1:sloid) pair. The structure of the StopPlace ID is retained, e.g. <StopPlace id="ch:2:StopPlace:8503000" version="any"> The newly generated SLOID will be structured as follows:
– Is the SLOID for ascending not unique, it shall be carried out in accordance with the scheme: {StopPlace SLOID}_gen:{Quay SLOID}_pf:{Platform Code*} educated.
– If no Steps SLIID is available, will be used instead {StopPlace SLOID} gen:missingSLOID_pf:{Platform Code*} used.
– Note: Special characters in the track identifier are replaced by a period (‘.‘), for example 21/22 → 21.22.
Planned implementation timetable:
– Thursday, 7th May 2026: Migration of DEV, TEST and INT systems (EFA, EMS)
– Thursday, 4th June 2026: Go-live of the PROD systems (EFA, EMS)
👉 We also have Test files prepared for you so that you can try out the new logic in advance: