Issues when using converter in JOSM

[prasuka4]

Hello,
This is Prashanth Kannan, I have tried to download xodr-osm converter which was pretty much helpful, but there are few error that we are facing while converting xodr file to osm..

1. When tried to open the converted osm in JOSM it is plotting an id error, that we have tried to resolve by adding id's..Is there any other method for resolving this?
2. Also when the converter sample osm file opened in JOSM, where junctions are represented in dotted lines instead off continuous line. Can this be altered?
3. The header/geo reference/lat & lon position are set with specific standard that was mentioned in xodr sample file. Is there any other projection string format that can be altered/used which might help for flexible utilization of converter for different softwares/tools.
   Kindly provide solutions that might help us in conversion process
   Thank you

[simon0628]

Hello,
This is Prashanth Kannan, I have tried to download xodr-osm converter which was pretty much helpful, but there are few error that we are facing while converting xodr file to osm..

1. When tried to open the converted osm in JOSM it is plotting an id error, that we have tried to resolve by adding id's..Is there any other method for resolving this?
2. Also when the converter sample osm file opened in JOSM, where junctions are represented in dotted lines instead off continuous line. Can this be altered?
3. The header/geo reference/lat & lon position are set with specific standard that was mentioned in xodr sample file. Is there any other projection string format that can be altered/used which might help for flexible utilization of converter for different softwares/tools.
   Kindly provide solutions that might help us in conversion process
   Thank you

Hi Kannan, sorry for my late reply.
For the first question, could you please specify which id error JOSM is plotting? I'm not sure whether it is a bugfix or a new feature. It will be helpful to provide us with more detail.
For the second one, junction in OSM is represented in dot by convention. Are you aiming to represent the bounding box of crossing? I assume it is not hard to implement, but the converting rules need to be defined.
For the last one, yes. This feature will be added soon. You may provide some of the standard you are going to use. we will give priority to support.
Glad to hear that this tool is helpful to you. Our next main feature is improving the compabiilty of the tool. Please stay tunes for update.

[simon0628]

I've downloaded JOSM and take a few simple test in it. Now I've understood what you're talking about.
OSM didn't specify the begin id of nodes, so we use 0 as default. And JOSM will throw out an error when encountering id=0. It's a bug of compability, we have fixed it. Also, the default scale of the OSM is too small, you may use view->'zoom to data' to find out where the result is.
For the second question you mentioned, it is because the OpenDRIVE stores information about connecting roads in analytic formula. We have to sample it into discrete form (because OSM use nodes to represent roads). But for junctions, we have to find their central points, and ignore the connecting roads. So the answer to 'Can this be altered?' is yes, but the overall converting logic have to be changed. FYI, we plan to add support for this this in one month.

[prasuka4]

Hi Simon,
Thank you for your response, we were able to use the updated converter to point converted osm in JOSM.

1. As suggested I'm providing a sample opendrive(.xodr) file for your reference through mail. This represents the standard Geo-header format that is being followed.

2. However, if the ".xodr" file contains entries for "paramPoly3" then the conversion fails. So, if you provide any suggestion/changes that might help in utilizing the converter with the files of "paramPoly3" entry.

Also, if you provide the help regarding junction that was mentioned earlier that would be great.
Kindly provide solutions that might be helpful in conversion process
Thank you