Dear Christian,
if I may join the discussion.
"Instead of "re-animating" the visualization scheme, I suggest to
introduce a new element <screenCoord> at the same level like <geoCoord>. "
Would be nice to have such an element, so we do not have to use the deprecated visualization scheme in railML 2.x.
But on top we need a separate element for this use case, which also can have absolute and relative positions and is independent from another element. It is also not able to be touched "in real life". So combined:
<nor:visualisationElements>
<nor:visualisationElement pos="integer" code="string" name="string" description="string" >
<screenCoord x="250" y="550"/>
</nor:visualisationElement>
</nor:visualisationElements>
Best regards
Jonathan
[Updated on: Wed, 21 March 2018 14:25]
Report message to a moderator