IS:trackGauge

Introduction

In rail transport, <trackGauge> is the distance between the two rails of a railway <track>. All <vehicles> on a rail <network> must have wheelsets that are compatible with the <trackGauge>. Since many different <trackGauges> exist worldwide, gauge differences often present a barrier to wider operation on railway <networks>. Not to be confused with <loadingGauge>.
	<trackGauge>

Documentation

Syntax

Autoexport from the XML-Schema for element IS:trackGauge of railML® version 3.3      UML-visualization of IS
Documentation	Allows describing the distance between the rails
Subschema	infrastructure
Parents*	trackGauges
Children	areaLocation (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes: value: value of gauge in metres (obligatory; xs:decimal), 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 IS:trackGauge of railML® version 3.2      UML-visualization of IS
Documentation	Allows describing the distance between the rails
Subschema	infrastructure
Parents*	trackGauges
Children	areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes: value: value of gauge in metres (obligatory; 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.

Autoexport from the XML-Schema for element IS:trackGauge of railML® version 3.1      UML-visualization of IS
Documentation	This element is not documented in the schema!
Subschema	infrastructure
Parents*	trackGauges
Children	any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
Attributes: value: the track gauge is the distance between the rails, in metres (obligatory; xs:decimal), 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 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 children have been changed.

The attributes have been changed.

Best Practice / Examples

In Chop_railway_station () some tracks have Dual_gauge ()

Below an example of modeling of Dual_gauge () is given.

        <trackGauge id="trg01" value="1435">
          <linearLocation id="trg01_lloc01" applicationDirection="both">
            <associatedNetElement netElementRef="ne_a11">
              <geometricCoordinateBegin positioningSystemRef="gps01" x="48.43370" y="22.21180"/> 
              <geometricCoordinateEnd positioningSystemRef="gps01" x="48.43369" y="22.21368"/> 
            </associatedNetElement>
          </linearLocation>
        </trackGauge>
        <trackGauge id="trg01" value="1520">
          <linearLocation id="trg01_lloc01" applicationDirection="both">
            <associatedNetElement netElementRef="ne_a11">
              <geometricCoordinateBegin positioningSystemRef="gps01" x="48.43370" y="22.21180"/> 
              <geometricCoordinateEnd positioningSystemRef="gps01" x="48.43369" y="22.21368"/> 
            </associatedNetElement>
          </linearLocation>
        </trackGauge>

Additional Information

Notes

Example was reviewed by the coordinator (link to the railML^® website) of the Infrastructure subschema on 2025-10-24.