| Re: Include track length information in topology [message #2114 is a reply to message #2113] |
Mon, 21 January 2019 15:49   |
christian.rahmig
Messages: 460
Registered: January 2016
|
Senior Member |
|
|
Dear Thomas,
Am 21.01.2019 um 15:34 schrieb Thomas Nygreen:
> [...]
> There is also a possible conflict if both @intrinsicCoord
> and @pos are used and (@intrinsicCoord *
> <netElement>@length) calculates to something else than @pos.
> Should there be a rule that only one of the two attributes
> can be used on the same element, or should they be
> interpreted differently?
I suggest an order of priority:
If both attributes (@pos and @intrinsicCoord) are given, @pos is the
leading one and @intrinsicCoord shall be calculated using the ratio of
@pos and <netElement>@length.
Any comments from the user community?
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
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
