| Direction in radiusChange and gradientChange [message #235] |
Mon, 19 April 2010 11:23 |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Does anyone need the 'dir' attribute inside the elements 'radiusChange'
and 'gradientChange'?
What does an import filter do in case of missing this attribute?
If I need to apply the 'dir' attribute, I have to write lots of
redundant information for both directions.
radiusChanges:
500------1200-------
km ->
0--------300-------600
<rail:radiusChange id="rc0" pos="0" radius="500" dir="up"/>
<rail:radiusChange id="rc1" pos="300" radius="1200" dir="up"/>
<rail:radiusChange id="rc2" pos="600" radius="1200" dir="down"/>
<rail:radiusChange id="rc3" pos"=300" radius="500" dir="down"/>
My favourite:
<rail:radiusChange id="rc0" pos="0" radius="500"/>
<rail:radiusChange id="rc1" pos="300" radius="1200"/>
No 'dir' attribute in 'radiusChange' and appropriate 'gradientChange'.
All '*change' definitions impact the track part with increasing 'pos'
(relative positioning = track positioning) until the next similar
'*change' element.
'speedChange' needs a different behaviour because there are often
different speed aspects subject to direction.
How about the other '*change' elements?
Any comments would be appreciated.
Kind regard,
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
