Skip to content
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

netconvert OpenDrive import misses junction connection #4812

Open
m-kro opened this issue Nov 19, 2018 · 6 comments

Comments

@m-kro
Copy link
Contributor

commented Nov 19, 2018

The given OpenDrive file models a four-leg junction with turning options right/straight/left for all incoming lanes. However the netconvert import result shows no straight connection from top incoming edge to bottom outgoing edge. For other approaches, the turnings have been created successfully.
Test_Variante_3_Strassen.zip

@namdre namdre self-assigned this Nov 19, 2018
@namdre namdre added the a:NETCONVERT label Nov 19, 2018
namdre added a commit that referenced this issue Nov 19, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Nov 19, 2018

I'm not sure if the solution covers all cases. Please let me know if you find further oddities.
May the example input be used in our public test suite?

@m-kro

This comment has been minimized.

Copy link
Contributor Author

commented Nov 20, 2018

Yes, you may add the example to the tests. Currently, we have a couple of intersections to convert. If we observe again some missing connection, we will report it here. Thank you for your help!

@namdre namdre closed this in 2529f39 Nov 20, 2018
@m-kro

This comment has been minimized.

Copy link
Contributor Author

commented Nov 28, 2018

There are more issues with the OpenDrive import when using the additional options --opendrive.import-all-lanes true --opendrive.internal-shapes true. Below you see he same intersection as before, but:

  • More connections than expected (see the parallel lines right-left, bottom-top)
  • Intersection geometry does not match connection length
  • Odd connection geometry
    grafik

Then there is another intersection where the same comments apply and a connection is missing (only with the extra OpenDrive import options):
grafik
Here is the OpenDrive file for it:
Test_Testkreuzung_mitSperrflaeche.zip

@namdre: Please correct the contribution information for the test to Technische Universität Braunschweig. Thank you.

@namdre namdre added the bug label Nov 28, 2018
@namdre namdre reopened this Nov 28, 2018
namdre added a commit that referenced this issue Nov 30, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Dec 7, 2018

The connectivity is correct but the shape of the internal lane is wrong. It's on top of the reverse direction internal lane and thus hidden.

namdre added a commit that referenced this issue Dec 12, 2018
namdre added a commit that referenced this issue Dec 12, 2018
namdre added a commit that referenced this issue Dec 12, 2018
@namdre

This comment has been minimized.

Copy link
Contributor

commented Dec 12, 2018

@m-kro There are still issues with variable width lanes of type 'none' that affect the shape of the internal lanes but are currently treated as constant width.

@sapirbm

This comment has been minimized.

Copy link

commented Feb 10, 2019

hello @namdre
netconvert still misses connections. in more than one junction in the files attached.
for example, in junction 167, in opendrive we can see 16 connections while in sumo only 12. netconvert dropped all of the right-lane-straight-line from all 4 junction directions. (roads 175, 178, 194, 197)
these roads and connections are missing in the net.xml file.

maps.zip

@namdre namdre reopened this Feb 10, 2019
namdre added a commit that referenced this issue Feb 10, 2019
namdre added a commit that referenced this issue Feb 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.