global-costmap-config

Configure Nav2 global costmap YAML parameters for map-based planning.

18|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill global-costmap-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-costmap-config
Source: https://github.com/wimblerobotics/ros2-copilot-skills/tree/main/global-costmap-config
Command: npx skills add https://github.com/wimblerobotics/ros2-copilot-skills --skill global-costmap-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure Nav2 global costmap to manage the map-based planning space, including resolution, footprint handling, and obstacle layer integration.

Core Features & Use Cases

  • Configure global_costmap parameters (global_frame, robot_base_frame, resolution, footprint, track_unknown_space, always_send_full_costmap)
  • Manage inclusion of obstacle/voxel layers based on sensor range and SLAM mode
  • Use static maps with dynamic obstacles and validate with common mistakes and debugging tips
  • Use case: tune costmap settings for accurate global planning on large maps

Quick Start

Edit your Nav2 YAML to set global_costmap parameters and load your map, then launch the costmap to verify behavior.

Frequently Asked Questions about global-costmap-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the Nav2 global costmap to use a static map with dynamic obstacles?

To configure the Nav2 global costmap with static maps and dynamic obstacles, you enable the obstacle layer integration in your YAML parameters while loading a valid static map. This allows the global costmap to manage the map-based planning space by overlaying dynamic sensor data onto the static map.

What does track_unknown_space do in a ROS2 global costmap?

The track_unknown_space parameter in a ROS2 global costmap dictates how unmapped areas are treated during path planning. Configuring this behavior in your YAML settings ensures the Nav2 planner either avoids or allows traversal through unknown spatial regions.

How do I tune Nav2 global costmap update and publish frequencies for large maps?

To tune Nav2 global costmap update and publish frequencies for large maps, you adjust the rate parameters in your YAML configuration. Setting appropriate frequencies prevents performance bottlenecks while ensuring the map-based planning space remains current with sensor updates.

Why does my Nav2 global costmap footprint handling cause planning failures?

Nav2 global costmap footprint handling causes planning failures when the robot_base_frame and footprint parameters in your YAML are not properly defined or scaled. Verifying these settings against your robot's physical dimensions ensures accurate global planning space management.

Do I need SLAM mode enabled to use voxel layers in a Nav2 costmap?

You do not always need SLAM mode enabled to use voxel layers in a Nav2 costmap, but inclusion of obstacle and voxel layers depends on your specific sensor range and whether you are operating in SLAM mode. Configure the YAML parameters to match your sensor setup.