-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to set bidi-edges with netedit #11397
Comments
The file problem2.net.xml.zip is redundant. This issue is also reported in the ticket #10445 |
A extracted network is generated and attached. A reverse edge (-403054383#8) of 403054383#8 is generated. When clicking one of these two edge the attribute "isBidi" of the Mode Inspect is still grayed out. No Bidi-edges can be generated accordingly. Where exactly should a respective test be generated under sumo\tests? |
such tests would go in tests/netedit but you do not need to add it right now. |
The geometries of both edges differs with regard to the endpoints. This is visible to the naked when looking at junction 5912628377 To enable bidi, select both edges and chose 'reset endpoints' from the context menu. |
The reversed edge is automatically generated by netedit. Don't they supposely have the same geometries regarding the end points? Just tried the method with 'reset endpoints' the endpoints are set back to the original ones once pressing F5/saving the network. And they can still not be set to bidi-edges. |
I also attached another case here: Edges c and -c should be set to bid-edges.
|
Add your issue description here.
Some edges cannot be set to bidi-edges with the spread-type-setting "center", since the check-box "isBidi" is either grayed out or has not action after clicking (see the attached example files problem2 and problem).
SUMO-version:
v1_14_1+0350-48d7f2812e8
operating system:
Windows
problem2.net.xml.zip
problem_edges.zip
The text was updated successfully, but these errors were encountered: