The following ticket discusses mitigation and those might be applied manually already: https://github.com/eclipse-sumo/sumo/issues/9045
Am Do., 1. Feb. 2024 um 17:27 Uhr schrieb Ruud van Gaal via sumo-user < [email protected]>: > Hi Mirko, > > SUMO only supporting a constant lane width is indeed a difference with > respect to OpenDrive and would explain what I've been seeing. Good to know, > thanks! > I did not use *--opendrive.min-width, *no, so the resulting edges were > mostly coming straight out of netconvert. I used something like: > > > *netconvert --opendrive-files myfile.xodr -o > myfile.net.xml --sidewalks.guess true --crossings.guess true* > > Kind regards, > Ruud > > > On Tue, Jan 30, 2024 at 3:56 PM Mirko Barthauer <[email protected]> > wrote: > >> 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" <[email protected]> >> >> An: "Sumo project User discussions" <[email protected]> >> >> >> >> >> >> >> 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: >> >> [image: image.png] >> With the export I used in SUMO 1.16.0 this ended up like this in SumoGui: >> >> [image: image.png] >> >> 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 >> >> >> >> > _______________________________________________ > sumo-user mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user >
_______________________________________________ sumo-user mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
