What problem does it solve? Configuring the Nav2 ObstacleLayer correctly is error-prone: mismatched raytrace and obstacle ranges leave phantom obstacles in the costmap, and misconfigured observation sources cause stale data or missing detections. This Skill provides the parameter reference and rules needed to set up reliable 2D obstacle marking and clearing. ## Core Features & Use Cases - Observation Source Setup: Define named LaserScan or PointCloud2 sources with independent marking, clearing, and range settings. - Range Validation Rules: Enforce the critical constraint that raytrace_range must exceed obstacle_range to prevent phantom obstacles. - Multi-Sensor Configuration: Combine front/rear lidars and depth cameras with per-source marking-only or clearing-only roles. - Use Case: A robot's costmap accumulates ghost obstacles after turning. Use this Skill to diagnose the raytrace_range versus obstacle_range mismatch and add a clearing-only wide-FOV source. ## Quick Start Configure the Nav2 obstacle layer with a front LaserScan source using obstacle_range 3.0 and raytrace_range 4.0, and explain why the raytrace range must be larger.