RTM:linearLocation

Introduction

See linear location in the RailTopoModel^® Wiki.

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:linearLocation of railML® version 3.3      UML-visualization of RTM
Documentation	Path locations in RailTopoModel®
Subschema	Rtm4railml
Parents*	balise, baliseGroup, border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, genericArea, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, linesideElectronicUnitIS, loadingGauge, loop, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder, restrictionArea, roadSideBarriers, roadSideLights, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tunnelGateIS, underCrossing, weightLimit
Children	associatedNetElement (1..*)
Attributes: applicationDirection: direction in which the element is applied, related to the orientation of the <netElement> (optional; xs:string) Possible values: both: from intrinsicCoordinate=0 to intrinsicCoordinate=1 AND from intrinsicCoordinate=1 to intrinsicCoordinate=0 normal: from intrinsicCoordinate=0 to intrinsicCoordinate=1 reverse: from intrinsicCoordinate=1 to intrinsicCoordinate=0, 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 RTM:linearLocation of railML® version 3.2      UML-visualization of RTM
Documentation	Path locations in RailTopoModel®
Subschema	Rtm4railml
Parents*	balise, baliseGroup, border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, genericArea, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tunnelGateIS, underCrossing, weightLimit
Children	associatedNetElement (1..*), geometricCoordinate (0..*), linearCoordinate (0..*)
Attributes: applicationDirection: direction in which the element is applied, related to the orientation of the <netElement> (optional; xs:string) Possible values: both: from intrinsicCoordinate=0 to intrinsicCoordinate=1 AND from intrinsicCoordinate=1 to intrinsicCoordinate=0 normal: from intrinsicCoordinate=0 to intrinsicCoordinate=1 reverse: from intrinsicCoordinate=1 to intrinsicCoordinate=0, id: the identifier of the object; this can be either of type xs:ID or UUID (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.

Autoexport from the XML-Schema for element RTM:linearLocation of railML® version 3.1      UML-visualization of RTM
Documentation	This element is not documented in the schema!
Subschema	Rtm4railml
Parents*	balise, border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, underCrossing, weightLimit
Children	associatedNetElement (1..*), geometricCoordinate (0..*), linearCoordinate (0..*)
Attributes: applicationDirection: direction in which the element is applied, related to the orientation of the <netElement> (optional; xs:string) Possible values: both reverse normal, id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID; 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.

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.

The element documentation has been changed.

The parents have been changed.

The children have been changed.

The attributes have been changed.

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