Ask Your Question

Add camera data to obstacle layer or voxel layer in costmap?

asked 2020-02-20 01:44:01 -0500

ninamwa gravatar image

Hi. I want to use navigation with multiple sensor inputs. I already have two SICK scanners on my robot, and to avoid the issue with only planar scanning, I want to add a RealSense camera as well.

I see that the obstacle/voxel layers in the costmaps in Navigation2 have support for this, and I am considering two cases:

  • Use depthimage_to_laserscan on the camera data and provide the obstacle layer with three laserscan inputs (and no voxel layer).
  • Use the pointcloud from the camera as input for the voxel layer, and two scan topics from the lasers for the obstacle layers.

Have anyone tested this and can tell me about how the different alternatives would affect the result, or maybe you can point me to some theory about this?


edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2020-02-20 09:19:31 -0500

Do the second.

If you have rich 3D information, use it. There’s no benefit except for compute savings from projecting the cloud into a scan, but you will lose a bunch of context in the environment. Unless you’re using an RPi or weaker computer, its well worth the CPU.

edit flag offensive delete link more


Thank you, I will try that out! :-)

ninamwa gravatar image ninamwa  ( 2020-02-21 02:44:29 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2020-02-20 01:44:01 -0500

Seen: 443 times

Last updated: Feb 20 '20