ROS nodes for reading point clouds from files (PLY, VTK) and writing sensor_msgs/PointCloud2 messages to files.
Point Cloud IO is a ROS package containing two helper nodes for reading and writing point cloud data files. It enables robotics developers to load point clouds from PLY or VTK files into ROS topics and save sensor_msgs/PointCloud2 messages to disk in PLY or PCD format. This solves the problem of integrating file-based point cloud data with live ROS sensor data pipelines.
ROS developers and robotics researchers working with 3D perception, especially those using point cloud data from files alongside live sensor data in legged robotics or autonomous systems applications.
Developers choose Point Cloud IO for its simplicity and direct integration with ROS—it provides focused, reliable utilities for point cloud file I/O without the overhead of more complex point cloud processing frameworks, making it ideal for research and prototyping workflows.
ROS nodes to read and write point clouds from and to files (e.g. ply, vtk).
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Directly publishes and subscribes to standard sensor_msgs/PointCloud2 topics, enabling easy integration with ROS pipelines, as shown in the usage examples for read and write nodes.
Allows customizable output file names with parameters like counters, frame IDs, and timestamps, helping organize saved point cloud data efficiently.
Follows a single-purpose philosophy for straightforward point cloud file I/O without unnecessary complexity, ideal for prototyping and research workflows.
Includes an optional rate parameter for the read node to control publishing frequency, useful for simulating repeated data streams from files.
The README disclaims fitness for purpose and warns of frequent changes, making it unreliable for production deployments where stability is critical.
By default, only PLY format is clearly supported for writing; PCD support is mentioned but not detailed in usage, and VTK requires extra build steps.
VTK file format support is disabled by default and requires explicit CMake flags during build, adding setup complexity for users needing that feature.