as everyone working with 3D LIDARs is aware of, the serialized sensor_msgs::PointCloud2 messages are very large. This affects:
the size of the rosbags.
the ability to visualize them remotely, for instance using RViz running on a different PC.
the time to load them insize a certain visualization tool.
People having this problem may start having a look here:
I am currently working (mostly for fun) on a different codec that preserves the number of points and their order (no voxelization).
Would you be interested to help me benchmarking this on a variety of rosbags?
Since these rosbag might contain sensitive information and I guess many people will not be happy sharing them, I will provide a precompiled App that you can run on your computer, and that will upload the results, such as encoding /decoding speed and compression ratio.
Just out of curiosity: is this a hand-rolled codec or one found in research? Pointcloud compression is something i started thinking about recently, but I haven’t had time to look at the literature/state-of-the-art solutions.
Hand rolled. In my preliminary result I get a 0.35 compression (1/3 the original size).
I tried some “known” algorithms, but results were generally worse.
I guess those algorithm deal with generic datasets, whilst I am leveraging some specific characteristics of data generated by LIDARs.
I’d be willing to participate. We have a lot of various sonar->point cloud data as well stereo pair data. Do you think you could provide the source for your benchmarking app?
One day you are just messing around with different compression techniques and the next day you to run a website that benchmarks different hardware and software combos against different datasets and posts the results to a publicly visible leader board.
Maybe some sort of grand “ROS Leaderboard,” like the COCO leaderboard, is something that should exist. When we were writing the RMW reports I suggested that someone should make “Consumer Reports” but for ROS packages.