Hello, 1) due to some unusual geometry (possibly related to the footpath), the connection is incorrectly classified as a partly-left turn rather than a turn-around and so get created despite the no-turnaround options. You could try importing with option '--keep-edges.by-vclass passenger' to get rid of the footpath. 2) Yes. It's common for the lane numbers in OSM to be incomplete. See 'remark for data consumers' at https://wiki.openstreetmap.org/wiki/Key:lanes#Description Obviously, this can be a major source of jamming in the simulation.
regards, Jakob Am Di., 14. Apr. 2020 um 18:47 Uhr schrieb Tetris < [email protected]>: > Thank you, I will try this. > > Furthermore I got data for the traffic lights to set the tls programs more > accurate. I used tls_csv2SUMO.py and got warnings like that: > "Warning: No link definition for connection (24654535#0_1, -24678549#1_1)!. > Using 'g' by default." > But this connection really shouldn't have any traffic on it. This would be > a > turnaround on an intersection. I already used --no-turnarounds and > --no-turnarounds.tls. > <http://sumo-user-mailing-list.90755.n8.nabble.com/file/t300/uturn.png> > > > I also noticed that there was one lane missing in the network. The road has > 3 lanes in google maps. But somehow openstreetmap exported only 2 lanes. Is > that a common bug? > > > > -- > Sent from: http://sumo-user-mailing-list.90755.n8.nabble.com/ > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
