IS:mileageChange

Documentation

Syntax

Autoexport from the XML-Schema for element IS:mileageChange of railML® version 3.3 UML-visualization of IS
Documentation	A MileageChange marks the point where the railway kilometer system does a jump resulting in a kilometer gap or overlap. A MileageChange needs to have two spot locations: one for the incoming and one for the outgoing kilometer value.
Subschema	infrastructure
Parents*	mileageChanges
Children	areaLocation (0..*), designator (0..*), elementState (0..*), gmlLocation (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes: type: describes whether kilometers were added (mileage gap) or removed (mileage overlap) (obligatory; xs:string) Possible values: gap: a mileage anomaly which happens when the value of algebraic difference between adjacent kilometre posts is lower than actual distance between them. This occurs when re-alignment made new track longer. overlap: a mileage anomaly which happens when the value of algebraic difference between adjacent kilometre posts is higher than actual distance between them. This occurs when re-alignment made new track shorter., 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:mileageChange of railML® version 3.2 UML-visualization of IS
Documentation	A MileageChange marks the point where the railway kilometer system does a jump resulting in a kilometer gap or overlap. A MileageChange needs to have two spot locations: one for the incoming and one for the outgoing kilometer value.
Subschema	infrastructure
Parents*	mileageChanges
Children	areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes: from: Referencing a spotLocation (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}}), to: Referencing a spotLocation (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}}), type: describes whether kilometers were added (mileage gap) or removed (mileage overlap) (obligatory; xs:string) Possible values: gap: a mileage anomaly which happens when the value of algebraic difference between adjacent kilometre posts is lower than actual distance between them. This occurs when re-alignment made new track longer. overlap: a mileage anomaly which happens when the value of algebraic difference between adjacent kilometre posts is higher than actual distance between them. This occurs when re-alignment made new track shorter., 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.

This element does not appear in railML^® 3.1 within the IS subschema. It is available only in railML^® 3.2. Do not hesitate to contact railML.org for further questions.

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.

Introduced with version 3.2.

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

Due to historical reasons, the mileage (or "metering") of the tracks of a line often is not continuous. It can have any points of discontinuity (jumping with missing parts or overlength of tracks) for instance by geographical corrections / repositioning of a line.

The <RTM:anchor> and <IS:mileageChange> elements both can be used to define the position of a track where metering of mileage changes. The approach with <IS:mileageChange> provides a less semantically rich way because anchors allow for stretched and compressed kilometers.

Below you can see the source code of a representation of mileage change (overlap) through <IS:mileageChange>s.

<mileageChange id="mch01"
               type="overlap"
               from="mch01_sloc02"
               to="mch01_sloc01">
  <spotLocation id="mch01_sloc01"
                neElementRef="ne_x01"
                applicationDirrection="both"
                intrinsicCoord="0.42">
    <linearCoordinate positioningSystemRef="lps01"
                      measure="990.0"/>
  </spotLocation>
  <spotLocation id="mch01_sloc02"
                neElementRef="ne_x01"
                applicationDirrection="both"
                intrinsicCoord="0.42">
    <linearCoordinate positioningSystemRef="lps01"
                      measure="1000.0"/>
  </spotLocation>
</mileageChange>