Open gladysmcgan opened 7 months ago
The entrance point for this problem is:
Any OSM node which has a railway tag with a value containing the keyword "crossing" will be treated as a railway crossing. This leads to special railway-oriented signalling.
I see, thanks!
I think a potential fix for the high cycle times might be for a way distinguish the green times given to trams and cars. For instance, to reduce the green time for a tram to something like 3-5 seconds, since it isn't realistic that trams have a similar green time to cars. Perhaps implementing this on this intersection is more complicated since here trams share a green phase with a turning for cars.
I have another intersection example here (folder) where a 31 second green phase serves only trams (see TLS cluster_2209519449_3447105008_41151781044115178105#4more in BAS_sumo_raw1.net.xml)
It seems that SUMO creates a signalised intersection on this node https://www.openstreetmap.org/node/1460427225, even though it does not have a traffic light signal tag in OSM. I noticed that the signals is removed when the tram_level_crossing tag is removed, but it is not always the case that tram_level_crossing intersections get signals.
May I know how and in which cases does SUMO create these signals in such intersections?
This is also an issue because of the resulting high cycle time, 180 (default 48).
OSM file, netccfg and net here
Thanks!
SUMO-version: 19
operating system: MacOS