Costmap's free-space depending on gmapping?
Hey all,
I realized that /costmap topic only publishes OBSTACLE, INFLATED and UNKNOWN space. All the rest is assumed to be FREE space. Now I need to get all available freespace blocks within my local costmap. As soon as the robot moves, the costmap steadily changes with direct impact on obstacle and inflated space. Now I wonder if this is different to free space. As I discovered, SLAM gmapping requires some time to create the map. During this time the amount of free space blocks do not change, which results in the fact that free space is not available in the instantiated costmap until the underlying map is created.
Which approach can be used to mitigate this behaviour?
- Faster updates of the SLAM map
- Somehow update freespace blocks, whenever the costmap changes
I really appreciate every hint. Thanks
Daniel