Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converted lat/lon different from original lanelet. #3

Open
mitsudome-r opened this issue May 7, 2019 · 4 comments
Open

Converted lat/lon different from original lanelet. #3

mitsudome-r opened this issue May 7, 2019 · 4 comments

Comments

@mitsudome-r
Copy link
Owner

lat/lon in converted vector map is different from original lanelet.
It is probably due to the mix use of geodesy package utm converter and lanelet UTM projector.

@liuyf5231
Copy link

lat/lon in converted vector map is different from original lanelet.
It is probably due to the mix use of geodesy package utm converter and lanelet UTM projector.

yes,
1.lanelet map data

<node id="1002" visible="true" version="1" lat="34.49234802584" lon="109.0428595787" />
<node id="1003" visible="true" version="1" lat="34.49234820025" lon="109.04287046419" />
<node id="1004" visible="true" version="1" lat="34.49234837466" lon="109.04288134969" />
<node id="1006" visible="true" version="1" lat="34.49233" lon="109.04286" />
<node id="1007" visible="true" version="1" lat="34.49233017441" lon="109.04287088549" />
<node id="1008" visible="true" version="1" lat="34.49233034882" lon="109.04288177098" />
<node id="1011" visible="true" version="1" lat="34.49234837466" lon="109.04288134969" />
<node id="1012" visible="true" version="1" lat="34.49234854907" lon="109.04289223518" />
<node id="1013" visible="true" version="1" lat="34.49234872348" lon="109.04290312067" />
<node id="1015" visible="true" version="1" lat="34.49233034882" lon="109.04288177098" />
<node id="1016" visible="true" version="1" lat="34.49233052323" lon="109.04289265647" />
<node id="1017" visible="true" version="1" lat="34.49233069764" lon="109.04290354196" />

  1. converted vector map
PID,B,L,H,Bx,Ly,ReF,MCODE1,MCODE2,MCODE3
7,34.293200,109.023400,0.000000,18486.200136,20301.105757,0,0,0,0
6,34.293200,109.023400,0.000000,18486.200136,20300.439091,0,0,0,0
5,34.293200,109.023400,0.000000,18486.200137,20299.772424,0,0,0,0
1,34.293200,109.023400,0.000000,18486.200136,20301.105757,0,0,0,0
2,34.293200,109.023400,0.000000,18486.200136,20302.105757,0,0,0,0
3,34.293200,109.023400,0.000000,18486.200136,20303.105757,0,0,0,0
4,34.293200,109.023400,0.000000,18486.200137,20299.105757,0,0,0,0
8,34.293200,109.023400,0.000000,18487.200137,20301.105758,0,0,0,0
9,34.293200,109.023400,0.000000,18487.200136,20302.105757,0,0,0,0

@mitsudome-r
Copy link
Owner Author

This was actually not a problem. Lat/lon in vector map are in dd.mmss format.

@liuyf5231
Copy link

format

This was actually not a problem. Lat/lon in vector map are in dd.mmss format.

hi mitsudome-r,

sorry again,
what's the meaing in vector map Bx,Ly? eg. 18486.200136,20301.105757

In my lanelet map,my origin point is lat="34.49233" lon="109.04286" />, other points in the lanelets near the origin point only 2 meter.

@mitsudome-r
Copy link
Owner Author

@liuyf5231
Please see this comment.
#2 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants