yes of course, I will check it out. Thanks for the updates.
With kind regards,
Od: sumo-user <sumo-user-bounces@xxxxxxxxxxx> v imenu Jakob Erdmann <namdre.sumo@xxxxxxxxx>
Poslano: torek, 08. marec 2022 19:10
Za: Sumo project User discussions
Zadeva: [EXTERNAL] Re: [sumo-user] SUMO OpenDrive unable to load in VTD
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
This message is from an external sender
This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you are not sure, you can use the ReportPhish Button to submit the message for analysis.
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?
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 ?
sumo-user mailing list
To unsubscribe from this list, visit