Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element TT:baseItinerary of railML ® version 3.3 |
| Documentation
|
Basic building blocks of a railML 3 timetable. Each BaseItinerary represents a path through the network along with the necessary run and stop times.
|
| Subschema
|
timetable
|
| Parents*
|
baseItineraries
|
| Children
|
baseItineraryPoint (1..*)
|
Attributes:
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID); 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.
|
Autoexport from the XML-Schema for element TT:baseItinerary of railML ® version 3.2 |
| Documentation
|
Basic building blocks of a railML 3 timetable. Each BaseItinerary represents a path through the network along with the necessary run and stop times.
|
| Subschema
|
timetable
|
| Parents*
|
baseItineraries
|
| Children
|
baseItineraryPoint (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, 3.3. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The children have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
This is an example of a base itinerary that is based on the Advanced example infrastructure (link to the railML® website). It shows how to specify a path through the railway network, while using many of the available options for describing special situations.
For easier understanding, here a schematic track plan of the base itineraries area:
The base itinerary consists of 3 stops:
- first is in Cranz (OC: op-3) on track 3 (the one between platform 1 and platform 11 in the above visualization)
- One platform is used for boarding the other for onboarding
- second is in Dunja (ODUN: op-4), its a onRequest stop
- third one is in Eimber (op-5) - not included in the drawing
Example below is valid only for railML 3.2. As of 2024-11-08 it was not adapted to railML 3.3!
<!-- From Cranz to Eimber -->
<baseItinerary id="bi-3">
<baseItineraryPoint id="bp-5" locationRef="op-3">
<times scope="commercial">
<departure time="12:01:00"/>
</times>
<times scope="operational">
<departure time="12:01:30"/>
</times>
<followupSections>
<followupSection>
<minimalTime runTime="PT2M15S"/>
<reserves>
<reserve reserve="PT45S" type="qualityByRailwayUndertaking">
<rule>
<timeBasedRule supplementInPercent="25"/>
</rule>
</reserve>
</reserves>
</followupSection>
</followupSections>
<trackRef ref="tk-3"/>
<stop>
<platformEdgeRefs>
<platformEdgeRef ref="pe-5" onOff="on"/>
<platformEdgeRef ref="pe-4" onOff="off"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-6"/>
<isCommercial onOff="both"/>
</stop>
</baseItineraryPoint>
<baseItineraryPoint id="bp-6" locationRef="op-4">
<times scope="commercial">
<arrival time="12:05:00"/>
<departure time="12:05:00"/>
</times>
<times scope="operational">
<arrival time="12:04:30"/>
<departure time="12:05:30"/>
</times>
<followupSections>
<followupSection>
<minimalTime runTime="PT7M30S"/>
<reserves>
<reserve reserve="PT2M30S" type="qualityByRailwayUndertaking">
<rule>
<timeBasedRule supplementInPercent="25"/>
</rule>
</reserve>
</reserves>
</followupSection>
</followupSections>
<stop minDwellTime="PT1M30S">
<platformEdgeRefs>
<platformEdgeRef ref="pe-8"/>
</platformEdgeRefs>
<stoppingPlaceRef ref="sp-13"/>
<isCommercial onRequest="true"/>
</stop>
</baseItineraryPoint>
<baseItineraryPoint id="bp-7" locationRef="op-5">
<times scope="commercial">
<arrival time="12:16:00"/>
</times>
<times scope="operational">
<arrival time="12:15:30"/>
</times>
<stop>
<isCommercial/>
</stop>
</baseItineraryPoint>
</baseItinerary>
Additional Information
Notes
Open Issues
