Re: [sumo-user] opendrive conversion to net.xml leads to projection erro

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Add option netconvert '--offset.disable-normalization' when importing the network.

(By default sumo networks are shifted towards 0,0 and this command disables the shift).

regards,

Jakob

Am Di., 12. Mai 2020 um 14:22 Uhr schrieb zipfl <zipfl@xxxxxx>:

Hi,

I want to convert a .xodr file to a .net.xml file.
The conversion from geodetic in metric coordinates results in wrong results:
I have a map which has a center point that is about 3km away from the area
of interest.
To check this I have chosen a characteristic point (geodetic), which can be
recognized in the net as well as in the odr file.
Additionally I have used the proj library to convert the same point. (with
the given transformation rule)
Both the xodr and the proj result in the same metric coordinates, but the
.net.xml differs in ca. 10, 6 m in x,y
In this picture both net and xodr are overlayed, the black and the grey road
should be in the same place.
<http://sumo-user-mailing-list.90755.n8.nabble.com/file/t387/sumo_x.png>

my geoReference in the xodr file
geoReference></geoReference>

my convertion command:
netconvert --opendrive FILE1.xodr -o FILE2.net.xml

----
Are there any commands that can fix that problem?






--
Sent from: http://sumo-user-mailing-list.90755.n8.nabble.com/
_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user