IS:track

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:track of railML® version 3.2
Documentation

A Track is a railway section that can be traversed by a train in a continuous motion.

Subschema

infrastructure

Parents*
Children

areaLocation (0..*), belongsToParent (0..1), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), trackBegin (0..1), trackEnd (0..1), typeDesignator (0..*)

Attributes:

  • infrastructureManagerRef: reference to the infrastructure manager who owns the track (see <organizationalUnits> in <common>) (optional; 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}}),

  • 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,

  • type: type of the track defining the general functionality of the track.
    DEPRECATION WARNING: As of Version 3.3 this attribute will become optional. (obligatory; xs:string)
Possible values:
  • mainTrack: A main track is either an open track between operational points or the extension of an open track within an operational point. It typically connects stations and is used for planned train journeys (trains in commercial operation or trains being moved between operational points). CH: Hauptgleis (signalisiertes Gleis). CZ: Hlavní kolej. DE: durchgehendes Hauptgleis. NL: Hoofdspoorweg. NO: hovedspor.
  • secondaryTrack: A secondary track is a track used for planned train journeys running in commercial operation or trains being moved between operational points, but it is not an open track between operational points or the extension of an open track. CZ: Spojovací kolej. DE: nicht-durchgehendes Hauptgleis. NL: Lokaalspoorweg. NO: øvrige
  • sidingTrack: Siding tracks are tracks that are not used for planned train journeys, except at the start and end of a train journey if the train is shunted to or from a parking spot. CH: Nebengleis (nicht-signalisiertes Gleis). CZ: Manipulacní koleje. DE: Nebengleis. NL: Raccordement. NO: Sidespor
  • connectingTrack: Connecting tracks are typically very short and connect other tracks. Examples are short track sections connecting two tracks where switches allow to move from one track to the other. CZ: Kolejová spojka. DE: Gleisverbindung. NO: øvrige,

  • 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 IS:track of railML® version 3.1
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*
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.


Changes 3.1→3.2

The element documentation has been changed.

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Since the railway network topology in railML® 3.x is based on RailTopoModel® elements <netElement> and <netRelation>, the <track> has no topologic dimension. Considering the <track> as a pure NetEntity derived object that is placed on top of a topology, the track does not have to be defined that strictly. It is possible to allow for a weaker definition, too. This section was requested by [tickets 1].

Open Issues

Affected Tickets