Dev:changes/2.2: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(→Infrastructure subschema: adding change for trackNode geoCoord) |
(→Infrastructure subschema: adding change for trackBegin absDir and trackEnd absPosIn) |
||
Line 36: | Line 36: | ||
</trackBegin> | </trackBegin> | ||
<trackEnd id="tr01_te" pos="61229"> | <trackEnd id="tr01_te" pos="61229"> | ||
<geoCoord coord="49.968768 7.889734" epsgCode="urn:ogc:def:crs:EPSG::4326" /> | |||
</trackEnd> | |||
</trackTopology> | |||
</syntaxhighlight> | |||
|} | |||
=== {{IS:Doc|trackBegin}}/{{Attr|@absDir}} === | |||
{| | |||
|Fact: | |||
| The optional attribute {{Attr|absDir}} has been added to the element {{IS:Tag|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 {{IS:Tag|mileageChange}} element. | |||
|- | |||
| Recommendation: | |||
| Use the new attribute {{Attr|absDir}} in element {{IS:Tag|trackBegin}} in order to define whether the mileage (absPos) starts "raising" or "falling" into the orientation direction of the track. | |||
|- | |||
| Related Trac Tickets: | |||
| [http://trac.railml.org/ticket/159 #159] | |||
|- | |||
| Related SVN Commits: | |||
| [http://trac.railml.org/changeset/444 [444]] | |||
|- | |||
| absDir sample: | |||
| | |||
<syntaxhighlight lang="xml"> | |||
<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> | |||
</syntaxhighlight> | |||
|} | |||
=== {{IS:Doc|trackEnd}}/{{Attr|@absPosIn}} === | |||
{| | |||
|Fact: | |||
| The optional attribute {{Attr|absPosIn}} has been added to the element {{IS:Tag|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 {{IS:Tag|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 {{IS:Tag|trackEnd}}. | |||
|- | |||
| Recommendation: | |||
| Use the new attribute {{Attr|absPosIn}} in combination with the attribute {{Attr|absPos}} in element {{IS:Tag|trackEnd}} if you want to model a mileage change in the end of the track. | |||
|- | |||
| Related Trac Tickets: | |||
| [http://trac.railml.org/ticket/159 #159] | |||
|- | |||
| Related SVN Commits: | |||
| [http://trac.railml.org/changeset/453 [453]] | |||
|- | |||
| absPosIn sample: | |||
| | |||
<syntaxhighlight lang="xml"> | |||
<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" /> | <geoCoord coord="49.968768 7.889734" epsgCode="urn:ogc:def:crs:EPSG::4326" /> | ||
</trackEnd> | </trackEnd> |
Revision as of 20:07, 29 March 2017
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
|
Infrastructure subschema
trackBegin/geoCoord and trackEnd/geoCoord
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> |
trackBegin/@absDir
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> |
trackEnd/@absPosIn
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> |
|
Rollingstock subschema
|
Common subschema
|