Hello Gregor, the latest git version contains several fixes with regard to misspelled attributes and element ordering. Can you re-export some xodr (either with a fresh build of netconvert or tomorrows nightly-build) and check whether VTD can load it?
regards, Jakob Am Mo., 7. März 2022 um 10:49 Uhr schrieb Ovsenjak, Gregor AVL/SI via sumo-user <[email protected]>: > Hello, > > since Carla is unable to load OpenDrive files created by SUMO and support > from their developers is bad I tried to load an OpenDrive file into VTD. > However when parsing even a simple 6 KB OpenDrive file of a straight > highway road VTD is unable to load it. It gets stuck in a loop. I compared > it with another XODR file which was not created by SUMO, and VTD was able > to load it. But when comparing the XML structure I could not find any > concerning difference, except at the start where SUMO uses > encoding="UTF-8", whereas WorkingVTD file uses standalone="yes". I can load > the odr in ESMINI. I am using a development version of SUMO loaded on 14th > of February. However even when trying with a stable version of SUMO, VTD > cannot load an xodr file. I don't know where is the issue, could You > perhaps help me locate the issue ? > > > > Best regards, > > Gregor Ovsenjak > > > _______________________________________________ > 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
