IS:geoCoord: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(template:external)
(Correcting link to levelCrossing)
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{InheritGeoCoord
== GeoCoord ==
|parentLink = {{IS:Tag|axleWeightChange}}, {{IS:Tag|balise}}, {{IS:Tag|border}}, {{IS:Tag|brigde}}, {{IS:Tag|clearanceGaugeChange}}, {{IS:Tag|crossing}}, {{IS:Tag|crossSection}}, {{IS:Tag|derailer}}, {{IS:Tag|electrificationChange}}, {{IS:Tag|from}}, {{IS:Tag|gaugeChange}}, {{IS:Tag|geoMapping}}, {{IS:Tag|gradientChange}}, {{IS:Tag|levelCrossing|levelCrossings}}, {{IS:Tag|lock}}, {{IS:Tag|mileageChange}}, {{IS:Tag|ocp}}, {{IS:Tag|operationModeChange}}, {{IS:Tag|ownerChange}}, {{IS:Tag|platformEdge}}, {{IS:Tag|powerTransmissionChange}}, {{IS:Tag|radiusChange}}, {{IS:Tag|serviceSection}}, {{IS:Tag|signal}}, {{IS:Tag|speedChange}}, {{IS:Tag|stopPost}}, {{IS:Tag|switch}}, {{IS:Tag|to}}, {{IS:Tag|trackBegin}}, {{IS:Tag|trackCircuitBorder}}, {{IS:Tag|trackCondition}}, {{IS:Tag|trackEnd}}, {{IS:Tag|trainDetector}}, {{IS:Tag|trainProtectionChange}}, {{IS:Tag|trainProtectionElement}}, {{IS:Tag|trainRadioChange}}, {{IS:Tag|tunnel}}
 
|selfLink = {{IS:Tag|geoCoord}}
A GeoCoord element is a container for specifiying geographical coordinates for a railway infrastructure object. Thus, a GeoCoord element defines exactly one point on earth given by either two or three dimensional coordinates.
|semantics_en =
 
|constraints_en =
By default, the coordinates shall be given in the reference system WGS84, because it is valid worldwide.
|notes_en =
WGS84: see {{external|http://spatialreference.org/ref/epsg/wgs-84}}.
|coord =
 
|extraHeight =
== Implementation in {{rml}} ==
|epsgCode =
 
|heightEpsgCode =
{{missing information|topic=implementation in {{rml}}|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 09:40, 15 January 2018 (CET)}}
}}
 
== Discussion ==
 
There are some aspects about geographical coordinates and the current implementation in railML, which are not yet solved and require further discussion. These aspects are listed below:
 
* At the moment, only ''one <geoCoord> per element'' can be defined. It is not possible, to give one point multiple geographical coordinates, e.g. for locating a point in different reference systems.
 
* At the moment, height coordinates cannot exist without horizontal coordinates. From the timetable's perspective this is difficult since often coordinates are not know and only the vertical height/gradient profile could be modelled. Therefore, the height coordinates should be defined independent from the horizontal coordinates. Until then, please use the parameter '''extraHeight''' in combination with zero horizontal coordinates (example for German DHHN92):
 
<syntaxhighlight lang="xml">
  <geoCoord coord="0 0 0" extraHeight="123.4" epsgCode="urn:ogc:def:crs:EPSG::5783" />
</syntaxhighlight>
 
* The height coordinates may differ in various countries referencing different national peils (Amsterdam's Peil, Kronstadt Peil, ...). The peil systems are categorized in the EPSG code too. You may find the EPSG codes at the {{external|http://www.epsg-registry.org|website of EPSG Geodetic Parameter Dataset}}.
 
== Examples ==
 
This code example defines the position of Oslo Sentralstasjon in WGS84 coordinates:
 
  <geoCoord coord="59.911 10.754" epsgCode="4326" />
 
This code example defines the position of Oslo Sentralstasjon in ETRS89 / ETRS-TM32:
 
  <geoCoord coord="598059.6081 6642972.5966" epsgCode="3044" />

Revision as of 22:49, 14 September 2020