You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lidar point clouds continue to grow and visualizing lidar point in realtime can use a lot of data. Practical amount using for example 4 spinning 128 channel lidars on a vehicle will grow above 1Gb/s.
So I would propose to support some sort of compressed point cloud (gzip:ed, quantization, mpeg-compressed) -> sensor_msgs/CompressedPointCloud.
Some compression ideas:
GZip, Usually reduces point cloud data size with approximately 50%.
I think it is a good idea in general. Before putting one in, I think it would be good to do research on the state-of-the-art for compressing point clouds. Once we have that in hand, we would probably want to design a message that can compress to any of the available compression methods, so we'd want metadata in the beginning to describe the compression scheme and other necessary things. Something like https://github.com/ros2/common_interfaces/blob/master/sensor_msgs/msg/CompressedImage.msg (but probably with more metadata fields).
Feature request
Feature description
Lidar point clouds continue to grow and visualizing lidar point in realtime can use a lot of data. Practical amount using for example 4 spinning 128 channel lidars on a vehicle will grow above 1Gb/s.
So I would propose to support some sort of compressed point cloud (gzip:ed, quantization, mpeg-compressed) -> sensor_msgs/CompressedPointCloud.
Some compression ideas:
Implementation considerations
Add a new standard sensor_msgs definition that can be used for compressed point clouds.
The text was updated successfully, but these errors were encountered: