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 |
would it be possible to use that as an input to the robot's navigation algorithm?
Yes, using global localization as a component of navigation is very common. You will either use the value directly (if it is frequent enough), or you use it to fine-tune the robot's odometry data when it becomes available. if your robot's transform tree looks like this:
map -> odom -> base_link
then you use the new data to calculate a new map->odom transform. You ask specifically about "SLAM Navigation": what I describe here is relevant only to the "Localization" portion of SLAM.
| | 2 | No.2 Revision |
would it be possible to use that as an input to the robot's navigation algorithm?
Yes, using global localization as a component of navigation is very common. You will either use the value directly (if it is frequent enough), or you use it to fine-tune the robot's odometry data when it becomes available. if your robot's transform tree looks like this:
map -> odom -> base_link
then you use the new data to calculate a new map->odom transform. You ask specifically about "SLAM Navigation": what I describe here is relevant only to the "Localization" portion of SLAM.
Update: What you describe is 99% not a "nav2" problem, it's a image processing problem. You need to find an object within an image, and estimate the location of the object relative to the camera lens. There is not a standard ros package that does this for you (because the simplifying assumptions are different for each environment.) A web search should give you a large number of hits of other people doing this, but make sure you understand what assumptions they made.
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.
