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

Odom != ECEF?? Why is an ECEF Position parsed into the Odom frame? #73

Open
bjajoh opened this issue Jul 17, 2021 · 5 comments
Open

Odom != ECEF?? Why is an ECEF Position parsed into the Odom frame? #73

bjajoh opened this issue Jul 17, 2021 · 5 comments

Comments

@bjajoh
Copy link
Contributor

bjajoh commented Jul 17, 2021

Hi,

for some reason the ECEF Position is used for the odom message. However this doesn't make any sense in my opinion, because ECEF is completely different from the UTM Coordinate System which should be used.
This is not conform with the ROS Odom message or in general anyone who would use it.

Is there any reason for it?

@dawonn
Copy link
Owner

dawonn commented Jul 17, 2021

Please feel free to send a PR; using ECEF directly doesn't really make sense for the Odom frame....

@bjajoh
Copy link
Contributor Author

bjajoh commented Jul 17, 2021

Ok thank you, yes I'll think about a fix.
Otherwise if people know why this is in the code, it would be helpful to know.

@dawonn
Copy link
Owner

dawonn commented Jul 17, 2021

ECEF is probably a fine choice for a data source, but generate a transform to an ENU frame with the origin at the starting location and translate the pos into that frame.

Thank you for the help! I don't regularly use this interface obviously. ;)

@CollinNHays
Copy link

Take a look at http://wiki.ros.org/enu. Since the VectorNav cannot provide an ENU/NED position this would be a good example of how to calculate an ENU position with the data the VectorNav provides.
It may be worth implementing an LLA to ENU conversion in the odom topic of this driver.
I may even make a PR out of this if wanted.

@dawonn
Copy link
Owner

dawonn commented Nov 17, 2021 via email

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

3 participants