Dev:changes/2.2: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(→Infrastructure subschema: adding change for trackNode geoCoord) |
|||
| Line 10: | Line 10: | ||
== Infrastructure subschema == | == Infrastructure subschema == | ||
=== {{IS:Doc|trackBegin}}/{{IS:Doc|geoCoord}} and {{IS:Doc|trackEnd}}/{{IS:Doc|geoCoord}} === | |||
{| | |||
|Fact: | |||
| The {{IS:Tag|geoCoord}} element has been added as child element of {{IS:Tag|trackBegin}} and {{IS:Tag|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 {{IS:Tag|geoCoord}} element in {{IS:Tag|trackBegin}} and {{IS:Tag|trackEnd}}. | |||
|- | |||
| Related Trac Tickets: | |||
| [http://trac.railml.org/ticket/135 #135] | |||
|- | |||
| Related SVN Commits: | |||
| [http://trac.railml.org/changeset/433 [433]] | |||
|- | |||
| geoCoord sample: | |||
| | |||
<syntaxhighlight lang="xml"> | |||
<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> | |||
</syntaxhighlight> | |||
|} | |||
=== {{IS:Doc|ocp}}/{{Attr|@abbrevation}} === | === {{IS:Doc|ocp}}/{{Attr|@abbrevation}} === | ||
Revision as of 19:41, 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>
|
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
|