Add Service to get depth from Image Pixel Location using the Lidar about navigator HOT 5 CLOSED

What will the service return if the pixel in the undistorted image is outside of the Velodyne's field of view (only 15 degree vertical field of view) ?

Also, if we want to get the range for a large number of pixels at a time, is the overhead of that many service calls worth the convenience?

from navigator.

Both are good things to think about. We can throw out data that doesn't have a mapping, that's easy. And as far as trying to use the service calls to get the range for a bunch of pixels and then do the smoothing and averaging on the program side, I think it should be handled on the server side. So while the client will call something like Eigen::Vector3f = server.get_depth_from_image(int x, int y) it can assume that the server has done the smoothing and the value returned is safe. So service overhead stays low.

from navigator.

I'm currently working on this for the right camera. I could probably make it more generic to work for other cameras as well. dev...ironmig:detect-deliver-dev

from navigator.

Here's my current plan:

The service request has the following fields:

• Header (for time and camera frame)
• 2d point in camera frame
• a tolerance (in pixels) of how far away a lidar point can be to be considered a corresponding point

The response includes

• an array (dynamic sized) of 3d points in camera frame found in the transformed lidar point cloud which are within tollerence pixels away from the request point

Returning an array rather then a single point allows for more use cases like finding a normal to a plane (me and @RustyBamboo will be using this in the detect-deliver mission)

NOTE: I'm not sure how this would work with stereo @DSsoto,

from navigator.

This is now available for the right camera as of #81. If it needs to be added for another camera, it can be easily configured for another.

from navigator.