| Re: [railML2] Adding a new element informationArea to ocp [message #2759 is a reply to message #2743] |
Fri, 11 June 2021 16:25  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Christian,
Christian Rößiger wrote on Tue, 01 June 2021 16:25...
In our view, it would be a clearer modelling if we used geo-coordinates that do not contain height information. Since
we do not necessarily want to introduce a new element for this, our
question is whether such an element already exists. Alternatively, we
would use the existing <tGeoCoord> element and point out in the
documentation that in this context the height should not be specified.
I suggest to define this rule of having only 2-dimensional coordinates for information areas as a semantic constraint for two reasons:
* we don't need to define a new datatype for a spatial coordinate, but can make use of the existing one
* we remain open for future changes, e.g. when railways conquer also the vertical dimension of space ;-)
I created a new Trac ticket #473 [1] for the topic to be included in railML 2.5.
[1] https://trac.railml.org/ticket/473
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
