Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

The normal usecase for move_base is using global_costmap (derived from a map, for global path palnning) and a local_costmap (derived from map and current sensor data, for local path planning, obstacle avoidance). You can use the projected_map as the input for the global costmap, and the laser_scans as obstacle layer in local_costmap.

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.