The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Is this simply because ~zero_altitude only affects the Odometry messages on /odometry/gps & not the NavSatFix messages on /gps/filtered?
In my understanding, Yes, that's true!
From the package documentation and precisely the part talking about the navsat_transform node
~zero_altitudeIf this is true, the nav_msgs/Odometry message produced by this node has its pose Z value set to 0.
Regarding the ~two_d_mode parameter,
It should be set to true if your robot is moving on a planar environment or to ignore the subtle effects of variations in the ground plane that might be reported from IMUs if it's not.
/gps/filtered is an optional topic where filtered NavSatFix messages generated from the output of the gps odometry are published in case this data is needed (sort of a reverse navsat transform).
A NavSatFix message with 0 altitude does not make sense, if we don't need altitude we can simply ignore it.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
