Point cloud processing basics in ROS - Step-by-Step Execution

Concept Flow - Point cloud processing basics

Capture Point Cloud Data

↓

Filter Noise & Outliers

↓

Downsample Points

↓

Segment Objects or Surfaces

↓

Extract Features

↓

Use for Mapping, Recognition, or Navigation

This flow shows the main steps in processing point cloud data: capturing, cleaning, simplifying, segmenting, extracting features, and using results.

Execution Sample

ROS

sensor_msgs::PointCloud2 cloud;
pcl::PointCloud<pcl::PointXYZ> cloud_filtered;
// 1. Convert ROS cloud to PCL
pcl::fromROSMsg(cloud, cloud_filtered);
// 2. Apply voxel grid filter
pcl::VoxelGrid<pcl::PointXYZ> sor;
sor.setLeafSize(0.1f, 0.1f, 0.1f);
sor.setInputCloud(cloud_filtered.makeShared());
sor.filter(cloud_filtered);

This code converts a ROS point cloud message to PCL format and applies a voxel grid filter to downsample the points.

Execution Table

Step	Action	Input Point Count	Output Point Count	Description
1	Receive ROS PointCloud2 message	N/A	N/A	Raw point cloud data received from sensor
2	Convert ROS message to PCL format	100000	100000	Data format changed, points unchanged
3	Set voxel grid leaf size	100000	100000	Prepare filter with leaf size 0.1m
4	Apply voxel grid filter	100000	5000	Points downsampled to reduce size
5	Output filtered cloud	5000	5000	Filtered cloud ready for next steps
6	End	5000	5000	Processing stops after filtering

💡 Filtering completes when voxel grid reduces points from 100000 to 5000

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
cloud (ROS msg)	empty	received with 100000 points	unchanged	unchanged
cloud_filtered (PCL)	empty	100000 points	5000 points	5000 points
sor (filter)	uninitialized	leaf size set	filter applied	filter ready

Key Moments - 3 Insights

Why does the point count drop from 100000 to 5000 after filtering?

The voxel grid filter groups points into cubes (voxels) and replaces them with a single point, reducing total points as shown in execution_table row 4.

Is the original ROS point cloud data changed during processing?

No, the original ROS message remains unchanged; conversion creates a new PCL cloud for processing (see execution_table row 2).

What does setting the leaf size in the voxel grid filter do?

It defines the size of cubes to group points; larger leaf size means more downsampling, as set before filtering in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution table, how many points remain after applying the voxel grid filter?

A 5000

B 100000

C 0

D 10000

💡 Hint

Check the Output Point Count column at Step 4 in the execution_table.

At which step is the ROS point cloud converted to PCL format?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the Action column in execution_table for conversion details.

If the leaf size in the voxel grid filter is increased, what happens to the output point count?

A It increases

B It decreases

C It stays the same

D It becomes zero

💡 Hint

Recall from key_moments how leaf size affects downsampling.

Concept Snapshot

Point cloud processing basics in ROS:
- Capture sensor data as PointCloud2 message
- Convert to PCL format for processing
- Use filters like voxel grid to downsample
- Segment and extract features for tasks
- Larger voxel leaf size means fewer points
- Original data stays unchanged during processing

Full Transcript

Point cloud processing in ROS starts by receiving raw data as a PointCloud2 message from sensors. This data is converted into PCL format to allow processing. A common step is applying a voxel grid filter, which groups points into small cubes and replaces them with a single point to reduce data size. For example, 100000 points can be reduced to 5000 points after filtering. The leaf size parameter controls how much downsampling happens: bigger leaf size means fewer points. The original ROS message remains unchanged throughout. This process prepares the point cloud for further steps like segmentation and feature extraction used in mapping or navigation.

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