IS:speedSection/3.2

Automatic Schemaexport for Element speedSection

Autoexport from the XML-Schema for element IS:speedSection of railML® version 3.2 UML-visualization of IS
Documentation	locates part of a track where given permanent speed restriction is applicable
Subschema	infrastructure
Parents*	speeds
Children	areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*), validForSpeedProfile (0..*)
Attributes: isSignalized: indicates whether the speed aspect is shown next to the track by a signal or panel (true) or only in the "driver's timetable" (false) (optional; xs:boolean), isTemporary: boolean value to indicate whether the speed section is temporary (optional; xs:boolean), maxSpeed: maximum permitted speed in the speed section, in [km/h] (optional; xs:decimal) Possible values: end, refersToTrain: Reference to the part of the train from where on the speed aspect is valid. Normally, a limiting speed signal aspect relates to the head of the train while a speed release refers to the end of the train. In ETCS this is usually refered to as Q_FRONT (optional; xs:string) Possible values: endOfTrain: The tail of the train should be located at the stopping place when the train has stopped. headOfTrain: The headof the train should be located at the stopping place when the train has stopped. This is the default setting. midOfTrain: The center of the train should be located at the stopping place when the train has stopped., 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.