From 9af4472ec7fb5a90de94b973c0d2a785dd1fe8c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Wed, 17 Jun 2026 14:32:09 +0200 Subject: [PATCH 1/9] Addint StopPointInServiceJourneyPatternRef to JourneyWaitTime --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index cfcd99378..0fd73e186 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -158,6 +158,11 @@ Rail transport, Roads and Road transport + + + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Many systems don't support this feature in providing the data. So this element should be used with care. +v2.1 + + Wait time as interval. @@ -441,4 +446,4 @@ Rail transport, Roads and Road transport - + \ No newline at end of file From 03b744ded6ea62865b1e26900b74202d06e489c9 Mon Sep 17 00:00:00 2001 From: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 17 Jun 2026 12:34:54 +0000 Subject: [PATCH 2/9] Lint and update documentation tables --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 0fd73e186..525eaec0c 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -446,4 +446,4 @@ Rail transport, Roads and Road transport - \ No newline at end of file + From e7bda5f13a7f2087273173591e08d4ac4c990483 Mon Sep 17 00:00:00 2001 From: duex Date: Fri, 26 Jun 2026 20:13:45 +0200 Subject: [PATCH 3/9] made JourneyWaitTimeGroup/StopPointInJourneyPatternRef reference the correct element type --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 525eaec0c..627aeb85b 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -2,6 +2,7 @@ + @@ -158,7 +159,7 @@ Rail transport, Roads and Road transport - + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Many systems don't support this feature in providing the data. So this element should be used with care. +v2.1 From 9ea9fe2b13a64dc1a51f6754864310c27b16ffd9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Tue, 7 Jul 2026 17:27:37 +0200 Subject: [PATCH 4/9] Update netex_journeyTiming_version.xsd --- .../netex_journeyTiming_version.xsd | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 627aeb85b..28d1d0219 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -159,11 +159,14 @@ Rail transport, Roads and Road transport - + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Many systems don't support this feature in providing the data. So this element should be used with care. +v2.1 - + + + + Wait time as interval. @@ -447,4 +450,4 @@ Rail transport, Roads and Road transport - + \ No newline at end of file From 6cca3bb8a38a8645bbdbe3124cbcfca63c361ec0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Tue, 7 Jul 2026 23:57:14 +0200 Subject: [PATCH 5/9] add example and fix error and make it all one choice --- NeTEx.spp | 1 + ...eTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml | 787 ++++++++++++++++++ .../netex_journeyTiming_version.xsd | 23 +- 3 files changed, 805 insertions(+), 6 deletions(-) create mode 100644 examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml diff --git a/NeTEx.spp b/NeTEx.spp index 11d91fa2d..b5a8a143e 100644 --- a/NeTEx.spp +++ b/NeTEx.spp @@ -734,6 +734,7 @@ + diff --git a/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml b/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml new file mode 100644 index 000000000..17d61e213 --- /dev/null +++ b/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml @@ -0,0 +1,787 @@ + + + + + 2025-06-26T14:16:54+02:00 + TUXALP + NeTEx Zweisimmen Example edited by Urs + + + + + 2025-12-15T00:00:00 + 2026-12-12T23:59:59 + + + + + + Fahrplanjahr 2025/26 + + + + + BLS + BLS AG + + + entityLegalOwnership + + + + operation + + + + + + + + ProductCategories + + + Regio Express + RE + + + Regionalzug + R + + + + + + + + + SBOID + ch:1:sboid:100015 + + + ch:1:sboid:101105 + BLS AG + BLS + + + + + + + + + DIDOK + 7000 + + + SLOID + ch:1:sloid:7000 + + + Bern + 7000 + + + 7.43913088992 + 46.94883228914 + 540.2 + + + + + Berna + + + railStation + + + + + SLOID + ch:1:sloid:7000:5:9 + + + + + 7.43913088992 + 46.94883228914 + 540.2 + + + + + + + + + DIDOK + 7100 + + + SLOID + ch:1:sloid:7100 + + + Thun + 7100 + + + 7.62960582867 + 46.75485272921 + 559.75 + + + railStation + + + + + SLOID + ch:1:sloid:7100:1:1 + + + + + 7.62960582867 + 46.75485272921 + 559.75 + + + + + + + + + DIDOK + 8507483 + + + SLOID + ch:1:sloid:7483 + + + Spiez + 8507483 + + + 7.68010305780 + 46.68639566696 + 627.82 + + + railStation + + + + + SLOID + ch:1:sloid:7483:0:3AB + + + + + 7.68010305780 + 46.68639566696 + 627.82 + + + + + + + + + DIDOK + 8507290 + + + SLOID + ch:1:sloid:7290 + + + Zweisimmen + 8507290 + + + 7.37486190719 + 46.55348254993 + 941.6 + + + railStation + + + + + SLOID + ch:1:sloid:7290:0:930269 + + + + + 7.37486190719 + 46.55348254993 + 941.6 + + + + + + + + + DIDOK + 8507478 + + + SLOID + ch:1:sloid:7478 + + + Frutigen + 8507478 + + + 7.65158908644 + 46.58857680502 + 779.8 + + + railStation + + + + + SLOID + ch:1:sloid:7478:0:852180 + + + + + 7.65158908644 + 46.58857680502 + 779.8 + + + + + + + + + DIDOK + 8501609 + + + SLOID + ch:1:sloid:1609 + + + Brig + 8507290 + + + 7.99057910188 + 46.32002223690 + 677.9 + + + railStation + + + + + SLOID + ch:1:sloid:1609:4:9 + + + + + 7.99057910188 + 46.32002223690 + 677.9 + + + + + + + + + + + + + + + + SLNID + ch:1:slnid:1024437 + + + Bern - Spiez - Kandersteg - Brig (- Domodossola) + RE1 + rail + RE1 + + + + + + + + SLNID + ch:1:slnid:1024426 + + + Spiez - Zweisimmen + R11 + rail + R11 + + + + + Brig / Zweisimmen + + + + + + + DIDOK + 8507000 + + + SLOID + ch:1:sloid:7000:5:9 + + + Bern + 9 + railStation + + + + + DIDOK + 8507100 + + + SLOID + ch:1:sloid:7100:1:1 + + + Thun + 1 + railStation + + + + + DIDOK + 8507483 + + + SLOID + ch:1:sloid:7483:0:954324 + + + Spiez + 3 + railStation + + + + + DIDOK + 8507290 + + + SLOID + ch:1:sloid:7290:0:930269 + + + Zweisimmen + 6 + railStation + + + + + DIDOK + 8507478 + + + SLOID + ch:1:sloid:7478:0:852180 + + + Frutigen + 3 + railStation + + + + + DIDOK + 8501609 + + + SLOID + ch:1:sloid:1609:4:9 + + + Brig + 9 + railStation + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Bern-Spiez + + + + outbound + + + + + false + true + + + + + + + + true + true + + + + true + false + + + passenger + + + Spiez-Zweisimmen + + + + outbound + + + + + false + true + + + + true + false + + + passenger + + + + + + Spiez-Brig + + + + outbound + + + + + false + true + + + + + true + true + + + + true + false + + + passenger + + + + + + + + PT21M + + + + PT10M10S + + + + + + + + PT1M + + + + + + + + PT47M + + + + + + + + PT12M + + + + PT57M + + + + + + + PT1M + + + + + + + + + + 2025-12-14T00:00:00 + 2026-12-13T23:59:59 + 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000 + + + + + + + + + + + + + SJYID + ch:1:sjyid:100015:4175-001 + + + ch:1:ServiceJourney:1 + rail + + + planned + 14:39:00 + 0 + + + + + outbound + + + + + + + + + + + SJYID + ch:1:sjyid:100015:6829-001 + + + ch:1:VehicleJourney:2 + rail + + + planned + 08:30:00 + 0 + + + + + outbound + + + + + + + + + + + SJYID + ch:1:sjyid:100015:4179-001 + + + ch:1:ServiceJourney:1 + rail + + + planned + 15:12:00 + 0 + + + + + outbound + + + + + + + + RE1 4175 Bern - Spiez + 4175 + + + R11 6829 Spiez - Zweisimmen + 6829 + + + RE1 4179 Spiez - Brig + 4179 + + + + + + + + + + + + true + false + true + true + + + + + + + + + + + false + false + + + true + true + + + + + + + + + + + diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 28d1d0219..121cf8560 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -158,14 +158,25 @@ Rail transport, Roads and Road transport Elements of a JOURNEY WAIT TIME. - - + - In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Many systems don't support this feature in providing the data. So this element should be used with care. +v2.1 + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. Otherwise a TimingPointRef is the way to use. +v2.1 - - - + + + The standard way to use JourneyWaitTime is with a TimingPointRef. + + + + + +v2.1 + + + + + +v2.1 + + From 18b317293a4125154f34903b9ba4945afe7b605a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Wed, 8 Jul 2026 00:10:41 +0200 Subject: [PATCH 6/9] Update netex_journeyTiming_version.xsd --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 121cf8560..5cdf653e1 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -158,9 +158,9 @@ Rail transport, Roads and Road transport Elements of a JOURNEY WAIT TIME. - + - In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. Otherwise a TimingPointRef is the way to use. +v2.1 + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. >Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 @@ -176,7 +176,7 @@ Rail transport, Roads and Road transport +v2.1 - + From 0036375e2d33d20c13317df5d1452a9234387d70 Mon Sep 17 00:00:00 2001 From: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 22:13:16 +0000 Subject: [PATCH 7/9] Lint and update documentation tables --- .../timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml | 3 +-- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml b/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml index 17d61e213..918106381 100644 --- a/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml +++ b/examples/functions/timetable/NeTEx_CH_Bern_Spiez_Zweisimmen_ValidRef.xml @@ -1,7 +1,6 @@ - - + 2025-06-26T14:16:54+02:00 TUXALP NeTEx Zweisimmen Example edited by Urs diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 5cdf653e1..c9eb3c563 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -160,7 +160,7 @@ Rail transport, Roads and Road transport - In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. >Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. >Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 @@ -461,4 +461,4 @@ Rail transport, Roads and Road transport - \ No newline at end of file + From 5e20300005b70e6e0d3d90ca2b0e1a7984caba57 Mon Sep 17 00:00:00 2001 From: Stefan de Konink Date: Wed, 15 Jul 2026 23:15:13 +0200 Subject: [PATCH 8/9] Apply suggestion from @skinkie --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index c9eb3c563..26e16209e 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -160,7 +160,7 @@ Rail transport, Roads and Road transport - In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. >Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 From 04aa75e87367967a89e736ecfca7bc7423fb6eb7 Mon Sep 17 00:00:00 2001 From: Stefan de Konink Date: Wed, 15 Jul 2026 23:16:29 +0200 Subject: [PATCH 9/9] Apply suggestion from @skinkie --- .../part1_tacticalPlanning/netex_journeyTiming_version.xsd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd index 26e16209e..f9fb75681 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_journeyTiming_version.xsd @@ -160,7 +160,7 @@ Rail transport, Roads and Road transport - In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver. Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1 + In some cases there are multiple visits to the same stop with a different WaitTime (e.g. on the second there is a change in the driver). Then one of the PointInJourneyPatternRef is needed instead of the TimingPoint. Must be optional, because in the JourneyPatternWaittime other element make the reference to the pattern. Otherwise a TimingPointRef is the way to use. +v2.1