| Re: [railML2] Adding a new element informationArea to ocp [message #2738 is a reply to message #2733] |
Fri, 28 May 2021 13:37   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Milan,
thank you for sharing these ideas from the TT developers group with the IS community.
The approach of modelling "infomation areas" around OCPs sounds reasonable although it is not "touchable" infrastructure in a straight definition. So, I am curious to hear/read from the community about their needs for having information areas modelled within railML 2.5.
Some specific questions:
* Will information areas also needed for other infrastructure elements, e.g. level crossings or bridges or tunnels?
* naming: To make it more precise, how about <passengerInformationArea>?
* Is there any linking with other types of areas, e.g. track-related areas?
Finally, let's come to the rectangle challenge:
Generally, any kind of area will use <geoCoord> elements to define certain points describing the area boundaries. Every <geoCoord> element contains the attribute @epsgCode to define the coordinate reference system of the coordinate. For instance, EPSG::4326 specifies a WGS84 coordinate in 2D with latitude and longitude axes. Therefore, although not explicitly modelled in railML, the axes of the coordinates are given. Consequently, it is absolutely possible to model a rectangle using two coordinate positions: the rectangle is defined by lower left and upper right point with sides being parallel to the axes defined by the coordinate reference system (EPSG code). But you have to make sure, that all coordinate positions of the rectangle (as well as for any other geoemtry) are linked with the same coordinate reference system.
Any comments from the community are highly appreciated...
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
