| Re: New extention element "nor:visualisationElement". [message #1733 is a reply to message #1713] |
Tue, 20 March 2018 15:35   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
the subject of screen coordinates is essential to the use case
"Schematic Track Plan" and thus will be solved with railML 3.1 for sure.
I read your proposed solution for railML 2.3 NOR several and I came to
the conclusion that for railML 2.x there could be a simpler solution:
Instead of "re-animating" the visualization scheme, I suggest to
introduce a new element <screenCoord> at the same level like <geoCoord>.
<screenCoord> shall have attributes @x, @y (mandatory) and @z (optional)
defining a pixel position. A small example may look like this:
<levelCrossing id="lcr01" pos="123.45">
<geoCoord coord="52.26125 10.58776" epsgCode="4326"/>
<screenCoord x="250" y="550"/>
</levelCrossing>
What do you think about that proposal? Any feedback is appreciated...
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
Am 28.02.2018 um 15:34 schrieb Torben Brand:
> To be able to fullfill the use case capacity planning we
> need to be able to visualise schematic track plans.
> Currently we use the depricated visualisation scheme in
> railML2.3nor. The scheme can allocate screen coordinates on
> extisting elements. But this is missing a independent
> visualisation element for elements that are not able to be
> touched "in real life". For instance to draw a "kink" aka.
> "picture element" to bend the schematic track. This usually
> after a track branches out from switch and then is bent to
> follow the mother track in parralel. The new element
> <nor:visualisationElements> with sub-element <nor:visualisationElement>
> will have no function but to
> place a screen coordinate on a defined pos on a defined
> track. The element is optional. If the element is used, the
> attribute pos is mandatory, code, name and description is
> optional. We suggest to place the new element under <track>.
>
>
> <infrastructure>
> <track>
> <nor:visualisationElements>
> <nor:visualisationElement pos="integer" code="string"
> name="string" description="string" >
> The purpose of such an element is to provide coordinates to
> layout the infrastructure at a given position (via
> absPos/relPos attributes). In some models only a few "main"
> elements like switches or crossings deliver usable layout
> coordinates. If you want to model a side track, you will
> have a problem to obtain a satisfying infrastructure layout.
> There are several discussions regarding the infrastructure
> visualization. Since 2.1 the
> <infrastructureVisualization>-container is marked as
> deprecated in the wiki, but is still usable according to the
> schema and is indeed used in the railML2.3nor extension.
> Therefor we would like to use the
> <infrastructureVisualization>-container to refer to a
> <trackElementVis>-Element which assigns layout coordinates
> to a <nor:visualisationElement>.
>
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
