| Connection on TrackBegin and TrackEnd [message #1351] |
Tue, 08 March 2016 13:26  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
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.
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.
2) Allowing for two positions under <trackElementVis> with a new child element <ConnectorVis> to indicate that it's a visual connector.
3) Having two identical references <trackElementVis> with two different <positions>. This combined with suggestion 1. or 2.
4) If double positions or double references in <trackElementVis> are not to be allowed. Then use either the <trackElement> child <geoMappings> or a new child element <trackConVis>in combination with another <trackElement> child with a length of 0 meters between them to describe the track elements of the visual connector. A new child element <ConnectorVis> under <trackElementVis> will indicate that it's a visual connector and there should not be drawn a track between them.
I am looking forward to vivid discussions on this matter... ;-)
|
|
|
|
Members
Search
Help
Login
Home
