Re: [sumo-user] netconvert opendrive with many lanesection

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Hello,

Option geometry.remove should serve to join the sections. If it does not this means the sections vary in some important attribute.

You can use Netedit to check which attribute that is by right-clicking on a junction and looking for the greyed out text starting with 'Replacing junction with geometry point' (after that comes the reason for being greyed out).

From looking at your screenshot I guess it might be lane width.

You could try to import your network with option --opendrive.ignore-widths

regards,

Jakob

Am Di., 22. Jan. 2019 um 14:09 Uhr schrieb <christian.damdjowabo@xxxxxx>:

Hello everyone,

i have a question relative to netconvert from sumo.

I want to import a opendrive file using netconvert. But unfortunately inside my Opendrive file the is a lot of Lanesection define.

By import of this opendrive File with these Lanesection, sumo try to put after every lanesection an junction. The Consequence of this behavior is that a become a Map with junction overall. (See picture Nr 1). Normally this Map would look like that (picture Nr 2). I try to use the Option

<geometry.remove    value ="true"/>

<junctions.join    value ="true"/>

But nothing change.

After try to remove some lanesection manually, it’s look better.

But the Problem is that, there is a lot of defined Lanesection inside the opendrive file and it’s not possible to remove all it manually.

For this reason I want to ask, if it’s possible to import an opendrive file with many lanesection in Sumo, so that we don’t have after every lanesection an new junction.

Please I hope that you can help me …

 

Best regards

 

Christian

 

 

 

 

 

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/sumo-user