diff --git a/.gitignore b/.gitignore index 3ce15e17c..744889bcc 100644 --- a/.gitignore +++ b/.gitignore @@ -88,3 +88,4 @@ fabric.properties # Editor-based Rest Client .idea/httpRequests +/.idea diff --git a/examples/functions/timetable/Netex_01.2_Bus_SimpleTimetable_WithTimings.xml b/examples/functions/timetable/Netex_01.2_Bus_SimpleTimetable_WithTimings.xml index 5aca118bd..fd73a4314 100644 --- a/examples/functions/timetable/Netex_01.2_Bus_SimpleTimetable_WithTimings.xml +++ b/examples/functions/timetable/Netex_01.2_Bus_SimpleTimetable_WithTimings.xml @@ -420,6 +420,12 @@ The Calendar is shown coded as true + + + + noWaiting + + diff --git a/xsd/netex_part_1/part1_tacticalPlanning/netex_servicePattern_version.xsd b/xsd/netex_part_1/part1_tacticalPlanning/netex_servicePattern_version.xsd index 05f21f6d0..8f1c212f2 100644 --- a/xsd/netex_part_1/part1_tacticalPlanning/netex_servicePattern_version.xsd +++ b/xsd/netex_part_1/part1_tacticalPlanning/netex_servicePattern_version.xsd @@ -3,11 +3,13 @@ + + @@ -63,8 +65,7 @@ http://www.netex.org.uk/schemas/1.0/PATH/netex_prereqfile.xsd Unclassified - CEN, Crown Copyright 2009-2023 - + CEN, Crown Copyright 2009-2023
  • Derived from the Transmodel, VDV, TransXChange, NEPTUNE, BISON and Trident standards.
  • @@ -901,6 +902,13 @@ Rail transport, Roads and Road transport Nature of use of stop, e.g. access, interchange only, or pass through. Default is Access. + + + + + Impediments to navigation from processes or barriers. For example security, check in etc., +v2.1 + + diff --git a/xsd/netex_part_2/part2_journeyTimes/netex_passingTimes_version.xsd b/xsd/netex_part_2/part2_journeyTimes/netex_passingTimes_version.xsd index 1faa2c962..eda482bd2 100644 --- a/xsd/netex_part_2/part2_journeyTimes/netex_passingTimes_version.xsd +++ b/xsd/netex_part_2/part2_journeyTimes/netex_passingTimes_version.xsd @@ -3,6 +3,7 @@ + @@ -204,6 +205,11 @@ Rail transport, Roads and Road transport Number of days after the starting time of the journey if not same calendar day. Default is 0 for same day. + + + CHECK CONSTRAINTs can be used on StopPointInJourneyPattern as well. It should be used there, if it affects every SERVICE JOURNEY with that SERVICE JOURNEY PATTERN. If the CONSTRAINT only affects one single SERVICE JOURNEY and PASSING TIME is used, then it is better to use this CHECK CONSTRAINT here in PASSING TIME. +v2.1 + + OCCUPANCYs associated with this journey. +v2.0