Open zeta-mobility opened 2 months ago
Ouster Lidar: Documented as 'Autoware tested' on Autoware's LIDAR documentation page, yet no corresponding sensor integration code is available in the GitHub repository. We have developed our own integration code for the Ouster Lidar sensor and would like to discuss the possibility of contributing it to the repository.
Is you implementation anything different from https://autowarefoundation.github.io/autoware-documentation/main/reference-hw/lidars/? Also, there is a work in Sensing and Perception Working Group to develop unified lidar driver for different vendors. Do you think your implementation fits to the design? (cc. @drwnz )
Thank you for the response @mitsudome-r .
To clarify, we have not developed the driver itself; instead, we implement the code that converts the data received from the driver into the format required by Autoware's sensing pipeline. This transformation enables seamless integration of the data as an input to the sensing system.
Thus, both the LiDAR(Ouster) and GNSS(Swift Duro) data were integrated not through the development of new drivers, but by modifying the data format to ensure compatibility with the existing system.
Hello @zeta-mobility . To utilize GNSS, you'll need to adjust your message type to sensor_msgs/NavSatFix. I believe there's no need for additional additions as Autoware is presently compatible with this ROS default message type.
Checklist
Description
This issue concerns the integration and possible contribution of external sensors for Ouster Lidar and DURO GNSS, which are not currently available in the Autoware repository.
Purpose
Possible approaches
Definition of done