Hi @daohu527, thanks for contacting. I haven't looked very closely into Apollo but i I may ask what kind of support you are looking for? What does Apollo require more than the published PointCloud to utilize our Sensors? Like a specific PointCloud format or is it a little more than that?

Many people in the community need to use Ouster lidar, so we want to integrate Ouster directly into Apollo.

What we expect is that Ouster can provide an SDK to obtain point clouds, and then Apollo will call the API and adapt to Apollo's point cloud message format.

This is very similar to ROS, but each lidar may have some special configurations, so if possible we can write a design document, then I will push forward and integrate the ouster lidar as soon as possible, of course there are better suggestions we can discuss here.

@daohu527 Thanks for your feedback. I checked out Apollo's point cloud description and the list of common point type to include it. With minor changes to the Point Cloud Customization Framework, I added the new point type "xyzit" which should work with any of the sensor udp lidar formats (except that the low data profile lacks the intensity channel).

I created a PR #290 that implements Apollo's point type: . Please give it a try and give us your thoughts if this fulfills this requirement.

@Samahu Thank you for your quick solution! I'm on vacation recently, I will give you a plan on February 19th

@Samahu I checked your pr, but the difference is that Apollo uses cyber instead of ros, so it needs to be redesigned.

I write an design doc about it. To put it simply, lidar sdk provides a callback interface for Apollo registration, and provides data format meta info for raw data. I currently use the PCD format, and then the apollo lidar driver will register the callback and convert the data into Apollo format.

Looking forward to your reply

Hi @daohu527 the framework in question is not very popular on my radar. I think for such task that the team behind Apollo's could utilize the main Ouster SDK to carry out the integration.

Thank you for your reply! Can you tell me what aspects you consider? In fact, each Lidar API only needs to provide registration callbacks.

You know we can refer to the current framework for integration, but we would like to get official support so that during the upgrade and iteration process, the quality of these drivers will be more guaranteed. We can do integrated development if possible, but I would like your support, such as reviewing the code and subsequent updates.