sdk/0.2.2/pose2__d_8hpp.html

# Deprecated as of Foxy and will potentially be removed in any following release.

# Please use the full 3D pose.


# In general our recommendation is to use a full 3D representation of everything and for 2D specific applications make the appropriate projections into the plane for their calculations but optimally will preserve the 3D information during processing.


# If we have parallel copies of 2D datatypes every UI and other pipeline will end up needing to have dual interfaces to plot everything. And you will end up with not being able to use 3D tools for 2D use cases even if they're completely valid, as you'd have to reimplement it with different inputs and outputs. It's not particularly hard to plot the 2D pose or compute the yaw error for the Pose message and there are already tools and libraries that can do this for you.# This expresses a position and orientation on a 2D manifold.


float64 x

float64 y

float64 theta
Classes
class	geometry_msgs::msg::Pose2D
	ROS message class definition for Pose2D. More...
Namespaces
namespace	geometry_msgs
	The geometry_msgs package contains ROS2 interface definitions.

namespace	geometry_msgs::msg
	message definitions of the geometry_msgs package