Good afternoon guys,
yesterday I encountered a minor tagging problem. It is about a siding or yard track becoming part of the main network, using a crossover. The situation is sketched at http://puu.sh/hB2j5/44aceed8c0.png. Currently the tagging system demands us to tag according to [2]. This however looks like the main track on the left suddenly stops/starts. Perhaps tagging this single crossover as main [1], or allowing the tagging of both crossover and main [3] would be more elegant. Allowing [3] would also come in handy at tagging inbound and outbound station tracks; there it is very hard to distinguish main tracks from crossovers. Example: http://www.openrailwaymap.org/?lang=nl&lat=52.09244570234097&lon=5.1...
Kind regards, Jeroen
Hi,
I think about: What would the situation be like if the yard were abandoned?
-> +1 for solution [1.].
regards, Christian
Am 04.05.2015 um 14:51 schrieb JJJ Wegdam:
Good afternoon guys,
yesterday I encountered a minor tagging problem. It is about a siding or yard track becoming part of the main network, using a crossover. The situation is sketched at http://puu.sh/hB2j5/44aceed8c0.png. Currently the tagging system demands us to tag according to [2]. This however looks like the main track on the left suddenly stops/starts. Perhaps tagging this single crossover as main [1], or allowing the tagging of both crossover and main [3] would be more elegant. Allowing [3] would also come in handy at tagging inbound and outbound station tracks; there it is very hard to distinguish main tracks from crossovers. Example: http://www.openrailwaymap.org/?lang=nl&lat=52.09244570234097&lon=5.1...
Kind regards, Jeroen
Openrailwaymap mailing list Openrailwaymap@openrailwaymap.org http://lists.openrailwaymap.org/lists/listinfo/openrailwaymap
openrailwaymap@openrailwaymap.org