Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:itinerary of railML ® version 3.2 |
| Documentation
|
An Itinerary is created based upon one or several base itineraries. The base itineraries can be cut into parts and recombined for that. Additionally they can be transposed in time.
|
| Subschema
|
timetable
|
| Parents*
|
itineraries
|
| Children
|
range (1..*)
|
Attributes:
- id: unique identifier (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
Introduced with version 3.2.
Semantics
Best Practice / Examples
Combining base itineraries
Interpreting path
Below itinerary "it-11" combines base itineraries "bi-1" and "bi-7". This allows to go from Arnau to Kudowa.
The following conditions are true:
- <range> children of "it-11" so to say "intersect": both "bp-2" and "bp-22" refer with @locationRef to Cranz.
<range> children of "it-11" should be interpreted as follows: Train arrives at "bp-2" and departs from "bp-22". Arrival fact is indicated by attribute range/@end="bp-2". Departure fact is indicated by attribute range/@start="bp-22".
Definition of "bp-2" and "bp-22" differs on itself, thus microscopic description of a path should be interpreted as follows: Train arrives at "tk-5" and departs from "tk-6". From the definition of tracks it can be seen that "tk-5" and "tk-6" are parts of "tk-4". This is indicated with @belongsToParent attribute.
Interpreting times
As soon as "bi-1" has @offset="-PT5M" at "it-11", it means that arrival time="11:59:00" (e.g. for commercial trains) is moved 59 - 5 = 54 minutes i.e. new arrival time is "11:55:00". "bi-7" has no offset, therefore departure time is "11:59:00". Together this constitutes stop time of 5 minutes for "combined" itinerary "it-11".
More specific connections between parts of a track can be defined in the IS:topology part of the infrastructure subschema.
Operational points source code is below.
<operationalPoint id="op-1">
<name language="de" name="Arnau"/>
<designator entry="OAR" register="_RML"/>
<opEquipment>
<ownsInfrastructureElement ref="pf-1"/>
<ownsInfrastructureElement ref="sp-1"/>
<ownsInfrastructureElement ref="sp-2"/>
<ownsInfrastructureElement ref="sp-3"/>
<ownsInfrastructureElement ref="sp-4"/>
<ownsInfrastructureElement ref="tk-1"/>
<ownsInfrastructureElement ref="tk-2"/>
</opEquipment>
</operationalPoint>
<operationalPoint id="op-3">
<name language="de" name="Cranz"/>
<designator entry="OC" register="_RML"/>
<opEquipment>
<ownsInfrastructureElement ref="pf-2"/>
<ownsInfrastructureElement ref="pf-3"/>
<ownsInfrastructureElement ref="pf-4"/>
<ownsInfrastructureElement ref="sp-5"/>
<ownsInfrastructureElement ref="sp-6"/>
<ownsInfrastructureElement ref="sp-7"/>
<ownsInfrastructureElement ref="sp-8"/>
<ownsInfrastructureElement ref="sp-9"/>
<ownsInfrastructureElement ref="sp-10"/>
<ownsInfrastructureElement ref="sp-11"/>
<ownsInfrastructureElement ref="sp-12"/>
<ownsInfrastructureElement ref="tk-3"/>
<ownsInfrastructureElement ref="tk-4"/>
<ownsInfrastructureElement ref="tk-5"/>
<ownsInfrastructureElement ref="tk-6"/>
<ownsInfrastructureElement ref="tk-7"/>
</opEquipment>
</operationalPoint>
<operationalPoint id="op-5">
<name language="de" name="Eimber"/>
<designator entry="OEI" register="_RML"/>
</operationalPoint>
<operationalPoint id="op-6">
<name language="de" name="Funera"/>
<designator entry="OFN" register="_RML"/>
<opEquipment>
<ownsInfrastructureElement ref="pf-7"/>
<ownsInfrastructureElement ref="sp-15"/>
<ownsInfrastructureElement ref="sp-16"/>
</opEquipment>
</operationalPoint>
<operationalPoint id="op-11">
<name language="de" name="Kudowa"/>
<designator entry="OXK" register="_RML"/>
<opEquipment>
<ownsInfrastructureElement ref="pf-10"/>
<ownsInfrastructureElement ref="sp-19"/>
<ownsInfrastructureElement ref="sp-20"/>
<ownsInfrastructureElement ref="sp-21"/>
<ownsInfrastructureElement ref="sp-22"/>
<ownsInfrastructureElement ref="tk-10"/>
<ownsInfrastructureElement ref="tk-11"/>
</opEquipment>
</operationalPoint>
Tracks source code is below.
<track type="sidingTrack" id="tk-4">
<name language="de" name="1"/>
<designator entry="OC1" register="_RML"/>
</track>
<track type="sidingTrack" id="tk-5">
<name language="de" name="1a"/>
<designator entry="OC1A" register="_RML"/>
<belongsToParent ref="tk-4"/>
</track>
<track type="sidingTrack" id="tk-6">
<name language="de" name="1b"/>
<designator entry="OC1B" register="_RML"/>
<belongsToParent ref="tk-4"/>
</track>
Base itineraries source code is below.
<!-- From Arnau to Cranz -->
<baseItinerary id="bi-1">
<baseItineraryPoint id="bp-1" locationRef="op-1">
<times scope="commercial">
<departure time="11:52:00"/>
</times>
<times scope="operational">
<departure time="11:52:30"/>
</times>
<followupSections>
<followupSection>
<minimalTime runTime="PT4M"/>
<reserves>
<reserve reserve="PT1M" type="qualityByRailwayUndertaking">
<rule>
<timeBasedRule supplementInPercent="25"/>
</rule>
</reserve>
<reserve reserve="PT1M" type="trackworkByInfrastructureManager"/>
</reserves>
</followupSection>
</followupSections>
<trackRef ref="tk-2"/>
<stop>
<platformEdgeRefs>
<platformEdgeRef ref="pe-3"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-3"/>
<isCommercial/>
</stop>
</baseItineraryPoint>
<baseItineraryPoint id="bp-2" locationRef="op-3">
<times scope="commercial">
<arrival time="11:59:00"/>
</times>
<times scope="operational">
<arrival time="11:58:30"/>
</times>
<trackRef ref="tk-5"/>
<stop>
<platformEdgeRefs>
<platformEdgeRef ref="pe-15"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-7"/>
<isCommercial/>
</stop>
</baseItineraryPoint>
</baseItinerary>
<!-- From Eimber to Kudowa (Express) -->
<baseItinerary id="bi-7">
<baseItineraryPoint id="bp-21" locationRef="op-5">
<times scope="commercial">
<departure time="11:48:00"/>
</times>
<times scope="operational">
<departure time="11:48:30"/>
</times>
<followupSections>
<followupSection>
<minimalTime runTime="PT7M30S"/>
<reserves>
<reserve reserve="PT2M30S" type="qualityByRailwayUndertaking">
<rule>
<timeBasedRule supplementInPercent="25"/>
</rule>
</reserve>
</reserves>
</followupSection>
</followupSections>
<stop>
<passengerTextInfos>
<passengerTextInfoRef ref="pt-01"/>
</passengerTextInfos>
<announcements>
<announcementRef ref="an-01"/>
</announcements>
<isCommercial/>
</stop>
</baseItineraryPoint>
<baseItineraryPoint id="bp-22" locationRef="op-3">
<times scope="commercial">
<arrival time="11:59:00"/>
<departure time="12:01:00"/>
</times>
<times scope="operational">
<arrival time="11:58:30"/>
<departure time="12:01:30"/>
</times>
<trackRef ref="tk-6"/>
<stop>
<activities>
<activityLoad id="al01" minDuration="PT2M"/>
</activities>
<platformEdgeRefs>
<platformEdgeRef ref="pe-16"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-10"/>
<isCommercial/>
</stop>
</baseItineraryPoint>
<baseItineraryPoint id="bp-23" locationRef="op-11">
<times scope="commercial">
<arrival time="12:10:00"/>
</times>
<times scope="operational">
<arrival time="12:09:30"/>
</times>
<followupSections>
<followupSection>
<minimalTime runTime="PT6M"/>
<reserves>
<reserve reserve="PT2M" type="qualityByRailwayUndertaking">
<rule>
<timeBasedRule supplementInPercent="25"/>
</rule>
</reserve>
</reserves>
</followupSection>
</followupSections>
<trackRef ref="tk-10"/>
<stop>
<platformEdgeRefs>
<platformEdgeRef ref="pe-14"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-22"/>
<isCommercial/>
</stop>
</baseItineraryPoint>
</baseItinerary>
Itinerary source code is below.
<itinerary id="it-11">
<range baseItineraryRef="bi-1" start="bp-1" end="bp-2" offset="-PT5M"/>
<range baseItineraryRef="bi-7" start="bp-22" end="bp-23"/>
</itinerary>
Additional Information
Notes
Open Issues
