| Re: Connection on TrackBegin and TrackEnd [message #1353 is a reply to message #1351] |
Fri, 08 April 2016 15:53  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Hello Torben,
Am 09.03.2016 um 14:17 schrieb Torben Brand:
> Since this is my first forum post (finally) I will give a
> short introduction to myself. My name is Torben Brand and I
> am the railML coordinator for the Norwegian national rail
> administration, Jernbaneverket. I primarily work as a
> railway capacity engineer. Here I work a lot with the railML
> programs Opentrack, Treno and Viriato. As a half German I
> also speak fluent German.
Welcome to the railML forum!
> My issue is the following:
> Sometimes you have to split a track in two graphically. For
> instance due to the display or sheet size, you have to
> continue on a new row below. I will refer to this as a
> visual connector from now on. In railML today this would
> generate two tracks. This makes the model unnecessary
> complex and less human readable.
> I propose to handle this visual connector in the
> visualization in railML, instead of splitting the track.
>
> Suggestions to solutions could be:
> 1) Allowing for two positions under <trackElementVis>. The
> programs would have to interpret this as a visual
> connector.
> [...]
The main problem we are facing with all your suggested solutions is that
the infrastructure visualization branch has been marked deprecated with
railML version 2.2. However, we have to find a solution for the use case
you described. How this solution may look like, can be discussed with
the community here and at our next railML.org meeting. I am interested
in your opinions.
Thank you very much and best regards
Christian
--
Christian Rahmig
railML.infrastructure coordinator
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
