coordinate-frames-and-tf

Clarify ROS 2 coordinate frames and TF publisher rules for navigation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns developers with ROS 2 REP 105 frames and the TF publishing rules to prevent misconfigurations in navigation stacks.

Core Features & Use Cases

  • Clearly define standard frames (map, odom, base_link, base_footprint) and their roles.
  • Enforce a single publisher per transform to avoid TF conflicts in Nav2, AMCL, and localization pipelines.
  • Troubleshoot common issues like transform discrepancies, drift corrections, and misaligned sensors.

Quick Start

Validate your robot's TF tree and ensure a correct publish chain for all essential transforms.

Frequently Asked Questions about coordinate-frames-and-tf

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

FAQPage Schema
What are the standard ROS 2 coordinate frames needed for navigation?

Standard ROS 2 coordinate frames for navigation include map, odom, base_link, and base_footprint. These frames establish the spatial relationships required to align robots with REP 105 conventions and prevent misconfigurations in navigation stacks.

How do I enforce a single publisher per transform in TF2?

To enforce a single publisher per transform in TF2, you must configure your nodes to ensure only one broadcaster publishes each frame relationship. This prevents transform conflicts and discrepancies in Nav2, AMCL, and localization pipelines.

Why does my ROS 2 TF tree have transform discrepancies during navigation?

Transform discrepancies in a ROS 2 TF tree usually occur when multiple publishers broadcast the same coordinate frame. Enforcing a single publisher per transform resolves these conflicts and corrects drift corrections and misaligned sensors.

How do I validate my robot's TF tree for Nav2?

Validate your robot's TF tree for Nav2 by checking the publish chain and verifying explicit frame relationships across map, odom, and base_link. This configuration ensures correct frame alignment for localization pipelines.

When do I need to configure base_footprint alongside base_link in ROS 2?

Configure base_footprint alongside base_link in ROS 2 when your navigation stack requires a ground-projected frame representation. This frame alignment adheres to REP 105 standards and ensures accurate robot positioning relative to the odom and map frames.