|Re: [sumo-dev] Netedit lane lengths and shapes
Is it the "customShape" attribute? If so, and I specify the lane shape using "customStape", would that also mean that if I move the intersection a bit, or the starting/ending node of an outgoing/incoming edge, the position of the internal lanes would not move?
I played a bit more with the original network and while I might have an example where moving an incoming endpoint of edge at a neighbouring intersection generates a network file with many internal lanes recomputed (the original network has an awful lot of short edges for no apparent reason, and also quite complicated system of pedestrian and bicycle crossings; it has, though, been generated via netconvert with just minimum complaints about sharp turns). I cannot reproduce it for a network that has been manually simplified and, at least from the perspective of the updated UI for netedit in 1.x, looks visually okay. So my guess is that it is a some kind of geometry issue, probably triggered by too small edge segments and too close placement of auxiliary intersections in the file.
It seems to me that the only reasonable approach now would be to edit the network manually, hopefully only once, to clean it up, and to do all the editing of additionals afterwards...
Back to the top