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 elements <platformEdge> and <serviceSection> have been added as new child elements of <trackElements>.
|
| Reason:
|
The elements <platformEdge> and <serviceSection> were missing and needed for more detailed (microscopic) operational modelling. Both elements derive from the same base data type and are modelled like other child elements of <trackElements>.
|
| Recommendation:
|
Use the new <platformEdge> element to model a platform edge along a track, e.g. in a station. Use the new <serviceSection> element to model a service area along a track where fueling, watering etc. is done.
|
| Related Trac Tickets:
|
#122
|
| Related SVN Commits:
|
[440], [448], [474], [475], [498], [499], [500] and [566]
|
| platformEdge sample:
|
<platformEdge id="pe263012" dir="up" pos="12197" absPos="103215" length="199" ocpRef="ocpKSPA" side="right">
<geoCoord coord="50.257208 7.646223" epsgCode="urn:ogc:def:crs:EPSG::4326"/>
</platformEdge>
|
| serviceSection sample:
|
<serviceSection id="ss263019" dir="up" pos="50852" absPos="141869" length="122" ocpRef="ocpFNDH" side="left"
cleaning="true" fueling="true" loadingFacility="true">
<geoCoord coord="50.036540 7.804770" epsgCode="urn:ogc:def:crs:EPSG::4326"/>
</serviceSection>
|
| Fact:
|
The <geoCoord> element has been (re-) introduced as child element of <mileageChange> element. Further, the optional parameter absDir with its possible values "raising" and "falling" has been added to element <mileageChange>. At the same time, the parameter dir with its values "up" and "down" has been marked DEPRECATED.
|
| Reason:
|
The <geoCoord> element disappeared from element <mileageChange> with version 2.0. Now, it has been re-introduced as it was requested. Further, the new attribute absDir shall be used to define the direction of the mileage ("raising" or "falling") starting from here into the orientation direction of the track. At the same time, the existing optional attribute dir has been marked DEPRECATED as it is not needed for the <mileageChange>, but instead leads to misinterpretations regarding the direction of the mileage.
|
| Recommendation:
|
Use the new <geoCoord> element in <mileageChange> in order to define the geographic position of a mileage change point on your track. Use the new attribute absDir in element <mileageChange> in order to define the new direction of the mileage starting from this point.
|
| Related Trac Tickets:
|
#134
|
| Related SVN Commits:
|
[430]
|
| mileageChange 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>
<mileageChanges>
<mileageChange id="tr01_mc01" pos="31186" absPosIn="122384" absPos="122385" type="missing" absDir="raising">
<geoCoord coord="50.168017 7.687182" epsgCode="urn:ogc:def:crs:EPSG::4326"/>
</mileageChange>
</mileageChanges>
</trackTopology>
|
| 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)
|
|
