local-costmap-config

Configure a Nav2 local costmap for reactive obstacle avoidance by setting rolling_window to true and global_frame to odom in your YAML file. This creates a rolling window around the robot that updates dynamically without relying on a global map.

The best way to tune local costmap parameters in ROS2 is to balance obstacle coverage and CPU load. You can configure width, height, and resolution in your YAML file, such as setting a 5m x 5m window at 0.05 m resolution for responsive indoor navigation.

For a rolling window in Nav2, use dynamic layers like voxel_layer, obstacle_layer, and inflation_layer for sensor data. You must avoid static layers because the rolling window operates independently of a global static map for reactive navigation.

Yes, local costmap configuration works for both indoor and outdoor navigation tasks. The Skill provides guidance on layer configuration and sensor source definitions, allowing you to enable or disable suitable costmap layers for different environmental sensor setups.

Your Nav2 local costmap configuration fails YAML validation if it violates technical requirements. Ensure rolling_window is true, global_frame is odom, and static layers are excluded to enforce safe defaults and pass validation.