octomap_mapping: octomap | octomap_server
Package Summary
The OctoMap library implements a 3D occupancy grid mapping approach, providing data structures and mapping algorithms. The map implementation is based on an octree.
Deprecated. This package now forwards octomap pkgconfig flags through the manifest, do not depend on this feature. Instead use cmake's find_package infrastructure for the octomap package.
More details are available at http://octomap.sourceforge.net/.
- Author: Kai M. Wurm and Armin Hornung
- License: BSD
- Repository: alufr-ros-pkg
- Source: svn http://alufr-ros-pkg.googlecode.com/svn/trunk/octomap_stacks/octomap_mapping/octomap
The octomap ROS package will be deprecated (starting with ROS Fuerte, see below).
Documentation
General information about OctoMap is available at http://octomap.sourceforge.net/. Doxygen documentation based on the latest OctoMap release is available at Code API.
Up to ROS electric, this octomap package provides the OctoMap by downloading a released tarball. If you want to use OctoMap in ROS, octomap_ros and octomap_msgs provide messages, wrappers and conversion methods. A visualization tool is available at octovis.
OctoMap in ROS Fuerte
Starting with ROS Fuerte, OctoMap will be replaced with a rosdep system dependency provided in the ros-fuerte-octomap debian package. This means that you compile against OctoMap without requiring any ROS-specific build tools. For convenience, the system install includes CMake config files for easily finding and configuring OctoMap in your CMakeLists.txt using the normal find_package() macro:
find_package(octomap REQUIRED)
include_directories(${OCTOMAP_INCLUDE_DIRS})
link_directories(${OCTOMAP_LIBRARY_DIRS})
link_libraries(${OCTOMAP_LIBRARIES})Finally, add
<rosdep name="octomap" />
to your stack.xml.
Report a Bug
Use trac to report bugs or request features. For questions (and FAQ), check answers.ros.org.