| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi,
I am planning on using latitude / longitude coordinate space for my 2D navigation package. From your perspective, how easy would that be to implement or is there a different way of doing it?
I have seen quite a few projects use GPS for localisation but I am not sure what coordinate space they all operate in when in comes to TF, any advises?
The problem with lat/long space is that it's non-Euclidean, especially when you get far from the equator. For example if you develop your system in Texas and then take it to northern Europe this could completely break the system.
The recommended approach is to convert the raw lat-long from the GPS into a local North, East aligned coordinate system. Unless your project will be covering a distance of many kilometres then this flat approximation should work. The navsat_transform_node in the robot_localization package can be used to do this.
The advantage of this approach is that it uses a Cartesian frame measured in metres so it compatible with the rest of the ROS ecosystem.
The odometry message includes an absolute pose and relative twist message. In your case you can simply use the pose element and take your absolute position from that.
No, the twist is the relative movement (the first derivative). The pose message includes both the absolute position and the orientation information. However this data may not be filled in because GPS doesn't provide orientation directly only the course over ground which may well be different.
For reference REP 105 is a standard relating to this: http://www.ros.org/reps/rep-0105.html
Asked: 2019-02-07 03:58:26 -0600
Seen: 596 times
Last updated: Feb 07 '19
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.
