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

AP_DDS: Add support for PoseStamped #23278

Closed
Ryanf55 opened this issue Mar 22, 2023 · 2 comments · Fixed by #23480
Closed

AP_DDS: Add support for PoseStamped #23278

Ryanf55 opened this issue Mar 22, 2023 · 2 comments · Fixed by #23480
Assignees
Labels

Comments

@Ryanf55
Copy link
Collaborator

Ryanf55 commented Mar 22, 2023

While #23277 adds support for WGS-84 position reporting, the PoseStamped message is used to report position+orientation in a local coordinate system following ENU convention for ROS2 consumers.

This is commonly used as the position+orientation component an Odometry message in ROS2, when combined with the appropriate velocity message.

@pedro-fuoco
Copy link
Contributor

pedro-fuoco commented Apr 13, 2023

I'd like to look into it. Can you assign me ? @Ryanf55

@Ryanf55
Copy link
Collaborator Author

Ryanf55 commented Apr 24, 2023

Just talked to @tridge. We are good to continue with only ENU support. Since the conversion is usually trivial, and most ROS community is already in ENU, ArduPilot will expose ENU.

If we need NED, ArduPilot should follow ROS REP 103/105/147 by adding the _ned suffix to the frame ID. Perhaps enabled with a parameter so there isn't duplicate data. Not a priority for now unless someone makes a strong case for it.

@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in DDS/ROS2 Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants