There was a new feature with regard to OpenDRIVE signal output in 1.13.0 ( https://github.com/eclipse/sumo/issues/2367) but apparently nobody noticed this bug until now. It's fixed (https://github.com/eclipse/sumo/issues/11980) but you need to do a fresh build or wait until the nightly version of tomorrow to get the fix. Thanks for reporting,
Jakob Am Di., 8. Nov. 2022 um 10:12 Uhr schrieb Sasan Amini <[email protected]>: > Dear all, > I am using the netconvert to convert a sumo network to opendrive > format. The generated output has some issues that I cannot further > process it with my toolchain e.g. I see the XML file often contains: > <signals> > <signal id="LSA029_2" s="38.25" t="-8.00" orientation="+" > dynamic="yes" zOffset="5" country="OpenDRIVE" type="1000001" > subtype="-1" height="0.78" width="0.26"> > <validity fromLane="0" toLane="0" fromLane="1" > toLane="1" fromLane="2" toLane="2"/> > </signal> > </signals> > which is an invalid structure for an XML to have the same attribute > fromLane toLane multiple times in one element. > This happens n both version 1.14 and 1.15 which was just released. The > last time I successfully converted the network without errors was on > 2021-12-02 by Version v1_10_0+2435-f922cc64a22. > Any suggestions on what has changed? > > Thanks, > Sasan > _______________________________________________ > 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
