Hello, polyconvert is mainly intended to parse native formats. (I.e. it contains its own OSM parser to extract polygons). The xml reading facility is only intended to re-parse its own output xml for post processing and thus not helpful for parsing xodr. I think you could add an opendrive parsing module to polyconvert with moderate effort by copying liberally from the existing polyconvert parsers and the netbuild xodr road network importer.
best regards, Jakob 2017-08-03 17:40 GMT+02:00 Richter Gerald via sumo-user < [email protected]>: > Hi. > > What is the best approach to > use openDrive signal records > to generate some information that polyconvert can process. > > I saw a possibility to give an XML file to polyconvert. > * is there an example on how to use this option? > * how to specify what is to be expected by polyconvert in such a file? > > Or: is it easier to write my own extractor, generating a polys and pois? > > an educated guess would help. > > thanks & regards > Gerald. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > sumo-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sumo-user > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sumo-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sumo-user
