allenzhuyi

I have noticed that after converting from OpenDRIVE to a netxml file, when I first opened netedit in the default inspect mode,the shape and length of the edge at the...

I use the following command netconvert --rectangular-lane-cut false --check-lane-foes.all --ignore-errors --opendrive.curve-resolution 0.01 --log ./convert.log --opendrive-files computable-v20240207.xodr -o calc.20240216.net.xml and it still has the probem above.

> can you provide the input file (in a private message or direct attachment)? I send an email to you and upload the test opendrive file. I use the follwoing...

> @allenzhuyi beginning with tomorrow, the development version supports option **--junctions.endpoint-shape** which should have the desired effect (https://sumo.dlr.de/docs/Downloads.php#nightly_snapshots) Is is available now,I want to try to test.

After importing OpenDRIVE use opendrive.min-width option, SUMO dynamically adds some internal junctions and internal edges to handle changes in lane numbers or widths. This results in a mismatch with the...

But When I use the following commamnd "netconvert --opendrive-files nbgj-computable.xodr -o nbgj-computable1.net.xml --junctions.endpoint-shape --opendrive.curve-resolution 0.01 --opendrive.lane-shapesn --opendrive.min-width 2.5 --ignore-errors" sumo use roadId#number to name the edgeId. For example, there is...

But I alsgo want to add a opendrive lanesect index data to sumo edge,like userdata in opendrive. For example, there is a Road 37163 in opendrive file,it has 2 lane...