Point cloud processing basics in ROS - Mini Project: Build & Apply

Point Cloud Processing Basics

📖 Scenario: You are working on a robot that uses a 3D sensor to see its surroundings. The sensor gives you a point cloud, which is a collection of points in space representing objects around the robot. You want to write a simple ROS node to process this point cloud data.

🎯 Goal: Build a ROS node that subscribes to a point cloud topic, filters points based on their distance from the robot, and publishes the filtered point cloud.

📋 What You'll Learn

Create a ROS subscriber to receive point cloud data from the topic /input_cloud.

Create a ROS publisher to send filtered point cloud data to the topic /filtered_cloud.

Filter out points that are farther than 2.0 meters from the origin (0,0,0).

Use the sensor_msgs/PointCloud2 message type for input and output.

💡 Why This Matters

🌍 Real World

Robots use point cloud data to understand their environment for navigation and object detection. Filtering helps remove noise and irrelevant data.

💼 Career

ROS developers and robotics engineers often process point clouds to improve robot perception and performance.

1

Create the ROS node and subscriber

Create a ROS node named point_cloud_filter and a subscriber to the topic /input_cloud with message type sensor_msgs/PointCloud2. Use the callback function named cloud_callback.

ROS

# Initialize ROS node and subscriber
# Your code here

Hint

Use rospy.init_node to create the node and rospy.Subscriber to subscribe to the topic.

2

Create a publisher for the filtered point cloud

Add a publisher named pub that publishes sensor_msgs/PointCloud2 messages to the topic /filtered_cloud.

ROS

import rospy
from sensor_msgs.msg import PointCloud2

rospy.init_node('point_cloud_filter')
sub = rospy.Subscriber('/input_cloud', PointCloud2, cloud_callback)

# Create publisher for filtered cloud
# Your code here

def cloud_callback(msg):
    pass

rospy.spin()

Hint

Use rospy.Publisher with the topic /filtered_cloud and message type PointCloud2.

3

Filter points farther than 2.0 meters

Inside the cloud_callback function, write code to filter out points that are farther than 2.0 meters from the origin (0,0,0). Use the pcl_ros or pcl library functions to convert the PointCloud2 message to a point cloud, filter it, and convert it back to PointCloud2. Store the filtered cloud in a variable named filtered_cloud.

ROS

import rospy
from sensor_msgs.msg import PointCloud2

rospy.init_node('point_cloud_filter')
sub = rospy.Subscriber('/input_cloud', PointCloud2, cloud_callback)
pub = rospy.Publisher('/filtered_cloud', PointCloud2, queue_size=10)

def cloud_callback(msg):
    # Convert PointCloud2 to pcl PointCloud
    # Filter points farther than 2.0 meters
    # Convert back to PointCloud2 and assign to filtered_cloud
    # Your code here

rospy.spin()

Hint

Use sensor_msgs.point_cloud2.read_points to read points and create_cloud to create the filtered cloud.

4

Complete the ROS node with proper spin and imports

Ensure the ROS node imports all necessary modules, defines the cloud_callback function with filtering logic, initializes the node, subscriber, and publisher, and calls rospy.spin() to keep the node running.

ROS

import rospy
from sensor_msgs.msg import PointCloud2
import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import PointField
import std_msgs.msg

# Ensure all parts are connected and node spins
# Your code here

Hint

Make sure the node runs continuously by calling rospy.spin() at the end.

Practice

1. What is the main purpose of point cloud processing in ROS?

easy

A. To control robot motors directly

B. To convert raw 3D sensor data into useful information

C. To send text messages between robots

D. To create 2D images from cameras

Solution

1. Step 1: Understand point cloud data

   Point clouds are collections of 3D points from sensors like LIDAR or depth cameras.

2. Step 2: Purpose of processing

   Processing these points helps robots understand their environment by turning raw data into meaningful info.

3. Final Answer:

   To convert raw 3D sensor data into useful information -> Option B

4. Quick Check:

   Point cloud processing = useful 3D info [OK]

Hint: Point clouds = 3D data, processing = making sense [OK]

Common Mistakes:

• Confusing point clouds with text or 2D images
• Thinking point clouds control motors directly
• Mixing point cloud data with unrelated robot functions

2. Which ROS message type is commonly used to receive point cloud data?

easy

A. sensor_msgs/PointCloud2

B. sensor_msgs/Image

C. geometry_msgs/Twist

D. std_msgs/String

Solution

1. Step 1: Identify message types for sensor data

   Images use sensor_msgs/Image, movement commands use geometry_msgs/Twist, text uses std_msgs/String.

2. Step 2: Point cloud message type

   Point clouds use sensor_msgs/PointCloud2 to send 3D point data in ROS.

3. Final Answer:

   sensor_msgs/PointCloud2 -> Option A

4. Quick Check:

   Point cloud data = PointCloud2 message [OK]

Hint: PointCloud2 is the standard for 3D points in ROS [OK]

Common Mistakes:

• Choosing Image message for point clouds
• Confusing Twist with point cloud data
• Using String message for sensor data

3. Given this ROS Python snippet, what will be printed?

import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import PointCloud2

cloud = PointCloud2()
points = [(1, 2, 3), (4, 5, 6), (7, 8, 9)]
for point in pc2.read_points(cloud, field_names=("x", "y", "z")):
    print(point)

medium

A. SyntaxError due to wrong import

B. (1, 2, 3)\n(4, 5, 6)\n(7, 8, 9)

C. No output because cloud is empty

D. RuntimeError because cloud is not initialized properly

Solution

1. Step 1: Check PointCloud2 initialization

   The cloud variable is created but not filled with points data, so it is empty.

2. Step 2: Effect on read_points

   Reading points from an empty cloud yields no points, so the loop prints nothing.

3. Final Answer:

   No output because cloud is empty -> Option C

4. Quick Check:

   Empty cloud means no points printed [OK]

Hint: Empty PointCloud2 means no points to read [OK]

Common Mistakes:

• Assuming points list fills cloud automatically
• Expecting printed points without proper cloud data
• Confusing import errors with runtime behavior

4. What is wrong with this ROS Python code snippet for filtering points by distance?

import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import PointCloud2

cloud = PointCloud2()
filtered_points = []
for point in pc2.read_points(cloud, field_names=("x", "y", "z")):
    dist = (point[0]**2 + point[1]**2 + point[2]**2)**0.5
    if dist > 5:
        filtered_points.append(point)
print(filtered_points)

medium

A. cloud is empty, so no points to filter

B. Distance calculation uses wrong formula

C. read_points does not accept field_names argument

D. filtered_points should be a set, not a list

Solution

1. Step 1: Check cloud data initialization

   The cloud variable is created but not populated with any points, so it is empty.

2. Step 2: Effect on filtering loop

   Since no points exist, the loop does not run and filtered_points remains empty.

3. Final Answer:

   cloud is empty, so no points to filter -> Option A

4. Quick Check:

   Empty cloud means no filtering possible [OK]

Hint: Empty cloud means no points to filter [OK]

Common Mistakes:

• Assuming cloud has points without initialization
• Thinking distance formula is incorrect
• Believing read_points rejects field_names argument

5. You want to filter a point cloud to keep only points within 3 meters from the robot. Which approach correctly applies this in ROS Python?

hard

A. Convert PointCloud2 to Image and filter pixels by color

B. Publish the original PointCloud2 message without changes

C. Use geometry_msgs/Twist to filter points by distance

D. Use pc2.read_points to iterate points, calculate distance, and append points with distance <= 3 to a new list

Solution

1. Step 1: Understand filtering by distance

   Filtering means selecting points based on their distance from origin (robot).

2. Step 2: Correct method in ROS Python

   Use pc2.read_points to read points, compute distance for each, and keep those within 3 meters.

3. Step 3: Why other options fail

   Publishing original data does not filter; Twist messages control movement, not points; converting to Image loses 3D info.

4. Final Answer:

   Use pc2.read_points to iterate points, calculate distance, and append points with distance <= 3 to a new list -> Option D

5. Quick Check:

   Filter points by distance using read_points [OK]

Hint: Filter points by distance using read_points and condition [OK]

Common Mistakes:

• Publishing unfiltered data expecting filtering
• Using movement messages to filter points
• Converting point clouds to images for filtering