IS:track/3.1

Automatic Schemaexport for Element track

Autoexport from the XML-Schema for element IS:track of railML® version 3.1 UML-visualization of IS
Documentation	A Track is defined by a railway section between two switches/crossings or between a switch/crossing and a buffer stop.
Subschema	infrastructure
Parents*	tracks
Children	any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), length (1..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), trackBegin (0..1), trackEnd (0..1)
Attributes: type: type of the track defining the general functionality of the track (obligatory; xs:string) Possible values: mainTrack: CH: Hauptgleis (signalisiertes Gleis) CZ: Hlavní kolej DE: durchgehendes Hauptgleis NL: Hoofdspoorweg NO: hovedspor secondaryTrack: CZ: Spojovací kolej DE: nicht-durchgehendes Hauptgleis NL: Lokaalspoorweg NO: øvrige sidingTrack: CH: Nebengleis (nicht-signalisiertes Gleis) CZ: Manipulacní koleje DE: Nebengleis NL: Raccordement NO: Sidespor connectingTrack: CZ: Kolejová spojka DE: Gleisverbindung NO: øvrige, infrastructureManagerRef: reference to the infrastructure manager who owns the track (see <organizationalUnits> in <common>) (optional; xs:IDREF; 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}\}), mainDirection: predominant direction of operation on this track; use this attribute to define the default direction of train operations, especially on double track lines (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.