Closed FilippoGuarda closed 2 years ago
This is not an accidental omission. While some applications will benefit from having a static layer in the local map, typically we discourage this since it introduces dependency on the trajectory planner with localization quality to transform the map. For example, if you robot becomes poorly localized, then things that are not actual obstacles will not be navigable by the trajectory planners because they're being shown as map obstacles rather than using only current sensor data readings.
That can be appropriate for robots with relatively good / consistent localization or if your robot lacks good coverage sensors, but this is not what I want to be the default behavior, intentionally.
the omission of static layer made impossible to generate and visualize the local map on rviz. Thanks to Giacomo Fanti @FantiG for finding the error