railML schema changes between railML® 2.1 and railML® 2.2
This site is intended to collect the schema changes between railML® 2.1 and railML® 2.2 by topics, that influence the XML output. As it starts as a stub please refer to railML forum and railML's ticket system too.
For changes with other version upgrades see CO:changes.
Timetable subschema
|
In this article there is information missing with respect to the all the TT's changes in railML's version 2.2. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Vasco Paul Kolmorgen (Diskussion) 18:29, 11. Feb. 2016 (CET)
|
|
Infrastructure subschema
Fact:
|
The <geoCoord> element has been added as child element of <trackBegin> and <trackEnd> element.
|
Reason:
|
So far it was not possible to define the begin or the end of a track by their geographic coordinates.
|
Recommendation:
|
Use the new <geoCoord> element in <trackBegin> and <trackEnd>.
|
Related Trac Tickets:
|
#135
|
Related SVN Commits:
|
[433]
|
geoCoord sample:
|
<trackTopology>
<trackBegin id="tr01_tb" pos="0">
<geoCoord coord="50.350834 7.589025" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackBegin>
<trackEnd id="tr01_te" pos="61229">
<geoCoord coord="49.968768 7.889734" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackEnd>
</trackTopology>
|
Fact:
|
The optional attribute absDir has been added to the element <trackBegin>. Its possible values are "raising" and "falling".
|
Reason:
|
So far, it was not possible to determine the direction of the mileage ("raising" or "falling") at the beginning of a track without setting a separate <mileageChange> element.
|
Recommendation:
|
Use the new attribute absDir in element <trackBegin> in order to define whether the mileage (absPos) starts "raising" or "falling" into the orientation direction of the track.
|
Related Trac Tickets:
|
#159
|
Related SVN Commits:
|
[444]
|
absDir sample:
|
<trackTopology>
<trackBegin id="tr01_tb" pos="0" absPos="91199" absDir="raising">
<geoCoord coord="50.350834 7.589025" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackBegin>
<trackEnd id="tr01_te" pos="61229" absPos="152428">
<geoCoord coord="49.968768 7.889734" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackEnd>
</trackTopology>
|
Fact:
|
The optional attribute absPosIn has been added to the element <trackEnd>. Its possible values are of type tLengthM (meters).
|
Reason:
|
If the mileage (absPos) changes in the end of the track, it was not possible to model this change without an additional <mileageChange> element. This problem has been solved with the new attribute, which allows it to define two mileages (an "incoming" one and an "outgoing" one) for the <trackEnd>.
|
Recommendation:
|
Use the new attribute absPosIn in combination with the attribute absPos in element <trackEnd> if you want to model a mileage change in the end of the track.
|
Related Trac Tickets:
|
#159
|
Related SVN Commits:
|
[453]
|
absPosIn sample:
|
<trackTopology>
<trackBegin id="tr01_tb" pos="0" absPos="91199" absDir="raising">
<geoCoord coord="50.350834 7.589025" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackBegin>
<trackEnd id="tr01_te" pos="61229" absPosIn="152428" absPos="152455">
<geoCoord coord="49.968768 7.889734" epsgCode="urn:ogc:def:crs:EPSG::4326" />
</trackEnd>
</trackTopology>
|
ocp/@abbrevation
Fact:
|
The abbrevation attribute in the <ocp> element is declared deprecated.
|
Reason:
|
There are multiple different abbreviations for single operation or control points. They can't be defined with one attribute.
|
Recommendation:
|
Use the new <tsi> and/or <designator> elements instead.
|
Related Trac Tickets:
|
#112
|
Related SVN Commits:
|
[335], [439]
|
Old sample (railML 2.1):
|
<ocp ... name="Passau Hbf." abbrevation="NPA"/>
|
New sample (railML 2.2):
|
<ocp ... name='Passau Hbf.' ...>
<tsi country="80"/>
<designator register='RL100' entry='NPA'/>
<designator register='ENEE' entry='80-26506-6'/>
<designator register='PLC' entry='DE18274'/>
<designator register='IBNR' entry='8000298'/>
<designator register='DB640' entry='Pa'/>
</ocp>
|
|
In this article there is information missing with respect to all the additonal IS's changes in railML's version 2.2. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Vasco Paul Kolmorgen (Diskussion) 18:29, 11. Feb. 2016 (CET)
|
|
Rollingstock subschema
|
In this article there is information missing with respect to the RS's changes in railML's version 2.2. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Vasco Paul Kolmorgen (Diskussion) 18:29, 11. Feb. 2016 (CET)
|
|
Common subschema
|
In this article there is information missing with respect to the CO's changes in railML's version 2.2. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Vasco Paul Kolmorgen (Diskussion) 18:29, 11. Feb. 2016 (CET)
|
|