A ROS2 wrapper for OpenSlam's Gmapping, enabling mobile robots to create 2D occupancy grid maps from laser and pose data.
SLAM_GMAPPING is a ROS2 package that wraps the OpenSlam Gmapping library to perform Simultaneous Localization and Mapping (SLAM). It enables mobile robots to create 2D occupancy grid maps from laser scan and pose data, solving the core problem of mapping unknown environments while tracking the robot's location.
Robotics engineers and researchers working with ROS2-based mobile robots who need to implement SLAM for navigation, exploration, or mapping applications.
It offers a proven, open-source Gmapping algorithm integrated directly into ROS2, reducing development time and providing a reliable solution for 2D mapping without relying on proprietary software.
Slam Gmapping for ROS2
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Wraps the established OpenSlam Gmapping library, providing a reliable and tested solution for 2D SLAM, as highlighted in the README's reliance on 'openslam_gmapping'.
Designed specifically for ROS2, it subscribes to standard topics like 'scan' and uses TF, making integration straightforward for existing ROS2 setups, as per the launch instructions.
Publishes occupancy grids, metadata, and entropy on separate topics ('map', 'map_metadata', 'entropy'), offering detailed map analysis capabilities directly from the README.
Fully open-source and integrated into ROS2, it avoids vendor lock-in and allows customization, aligning with the project's philosophy of simplifying SLAM development.
Only generates 2-D occupancy grid maps, which is inadequate for environments with vertical structures or applications requiring 3D navigation, as stated in the description.
Heavily relies on laser scan data and proper TF setup, which can be complex to configure and may not suit robots with other sensor types, emphasizing the need for 'appropriate TF' in the README.
Gmapping is an older SLAM method and may not handle dynamic obstacles or large-scale maps as effectively as newer algorithms like Cartographer, given its 'well-established' nature.
Tightly coupled with ROS2, it is unusable for robotic systems based on other frameworks, limiting portability and flexibility for non-ROS projects.