[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [sumo-user] OpenDrive conversions to .net.xml
|
Hi Ruud,
in general importing an OpenDrive network will result in some simplifications. On top of that, only a subset of all OpenDrive elements/attributes is supported. There has been done some work on the OpenDrive import recently but I doubt it will help in your case.
The main issue here is that the importer will try to make the edges follow the reference line but has to keep the lane width constant (SUMO does not support lane width changes within a lane). Do you make use of any OpenDrive specific netconvert options like --opendrive.min-width?
Best regards
Mirko
-----Original-Nachricht-----
Betreff: [sumo-user] OpenDrive conversions to .net.xml
Datum: 2024-01-30T12:50:26+0100
Von: "Ruud van Gaal via sumo-user" <sumo-user@xxxxxxxxxxx>
An: "Sumo project User discussions" <sumo-user@xxxxxxxxxxx>
Hi,
The basis for soof our environments is in OpenDrive format. When exporting that to SUMO, it seems some of the base architectural constructs are different, making conversion difficult (OpenDrive uses roads with lanes, where SUMO uses an edge per direction it seems with lanes that are not really a direct conversion from OpenDrive). For example, in an OpenDrive (
odrviewer.io) viewer I see these lanes merging in OpenDrive:
With the export I used in SUMO 1.16.0 this ended up like this in SumoGui:
I'm wondering whether this is something structural or whether SUMO is capable of handling these types of conversions better. I'm not sure if any work has been done to the OpenDrive importer since SUMO 1.16, or that I might have missed some netconvert options which might improve the conversion on this point.
Thanks,
Ruud van Gaal
