RTM:spotLocation/3.2

Automatic Schemaexport for Element spotLocation

Autoexport from the XML-Schema for element RTM:spotLocation of railML® version 3.2      UML-visualization of RTM
Documentation	defines the concept of punctual location on a net element of a logical topology of a network.
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	geometricCoordinate (0..1), linearCoordinate (0..1)
Attributes: applicationDirection: direction in which the element is applied, related to the orientation of the <netElement> (optional; xs:string) Possible values: both normal reverse, intrinsicCoord: location on the <netElement> in normalized form (value in range 0..1) (optional; xs:double), netElementRef: reference to a railway topology <netElement> element (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}\}), pos: a distance from the edge of a net element (optional; xs:decimal), 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.