realsenseai/realsense-ros

ROS Wrapper for RealSense™ Cameras

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 20th, 2026
Created on February 23rd, 2016
Open Issues & Pull Requests: 125 (+0)
GitHub issues: Enabled
Number of forks: 2,012
Total Stargazers: 3,446 (+0)
Total Subscribers: 52 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 34
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 383 days
Stale 30+ days: 32
Stale 90+ days: 30

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • D400 (160)
  • question (34)
  • enhancement (8)
  • l500 (7)
  • ROS Wrapper 2 (1)
  • T265 (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Realsense-ros is a ROS 2 wrapper that integrates Intel RealSense cameras into ROS 2 robotics applications.

The wrapper solves the problem of connecting RealSense depth and RGB cameras to ROS 2 systems by providing a standardized interface for camera data. It publishes camera streams as ROS topics, including RGB and depth images, and exposes camera parameters through ROS services and actions. The tool handles coordinate system transformations between ROS 2 and optical camera conventions, publishes diagnostic information, and supports post-processing filters on camera data. It also provides an RViz 2 plugin for visualization and enables efficient intra-process communication for performance-critical applications.

The wrapper suits robotics projects that need depth sensing or RGB imaging from RealSense hardware within a ROS 2 ecosystem. It supports multiple cameras with configurable namespaces and names, and works on both Ubuntu and Windows. The project has moved away from ROS 1 support, with legacy ROS 1 code available on a separate branch. Developers migrating from earlier versions should note that the project has transitioned to the RealSenseAI GitHub organization from its previous location.

The project maintains active continuous integration workflows. Development activity shows regular updates and contributions from multiple developers. The codebase is written primarily in Python, making it accessible for modification and extension by ROS 2 developers.