| Re: [railML3] Positioning approach [message #3156 is a reply to message #3125] |
Thu, 02 November 2023 17:09   |
Karl-Friedemann Jerosch
Messages: 11
Registered: May 2020
|
Junior Member |
|
|
Dear Christian,
concerning your general questions:
- Yes, we understand the approach.
- We cannot fully agree with the suggestion. Details see attached file.
Summary:
- We agree to have intrinsic coordinates for netElements to define their orientation (0.0 and 1.0).
Additionally, each end of a netElement should have a linearCoordinate with absolute kilometer value
(using linearCoordinate with @positioningSystemRef and @measure).
- The location of other infrastructure and interlocking elements positioned on netElements should be given by using @pos (for spotLocations) or @posBegin and @posEnd (for linearLocation or areaLoction).
Additionally, as lower priority, the location can be provided by linearCoordinate (using linearCoordinate with @positioningSystemRef and @measure) to provide different kilometer systems (e.g. a linearPositioningSystem from infrastructure manager and/or another linearPositioningSystem from ETCS measurement).
- We would avoid to use intrinsic coordinates for infrastructure and interlocking elements (except netElements), because to get the absolute kilometer value of a location, conversion calculations are necessary which will result in rounding problems.
Means: To calculate the location, the intrinsic coordinates must be multiply with the netElement's length and this will result in rounding problems.
- After an expectable discussion, the documentation of railML.org should be updated accordingly including minor corrections (see attached file).
Martin Zien & Karl-F. Jerosch
[Updated on: Mon, 04 December 2023 11:00] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
