Maximilian Wulf

> For the parameter map_frame_id, I noticed that some demos used "map" for this value, whereas other demos used "odom." In the case where we do not have a ground...

Hi, yes you can define different input sources. As long as your robot configuration is correct the output should work just fine. Let me know if you have issues.

Hey, your min allowed estimation radius is defined by the resolution. If you change your map resolution the error can go away. Check here https://github.com/ANYbotics/grid_map/blob/master/grid_map_filters/src/NormalVectorsFilter.cpp#L204

Hi @LZMHIT, thank you for using elevation mapping. In which frequency did it run on your system? It depends on the hardware and the settings. This pull request #96 discusses...

> > Yeah, that just what I mean, thank you for your reply, I have another question. Yesterday, I tried to use elevation mapping with velodyne 32, however it seems...

@DLonng, no, but feel free to make a PR to this repo if you tune a new configuration file.

Hey @blablebli-robots thank you for the issue. The line you mention does not directly point to a for loop, see https://github.com/ANYbotics/elevation_mapping/blob/master/elevation_mapping/src/ElevationMapping.cpp#L424. Maybe line number changed.

But this for loop already has the check? https://github.com/ANYbotics/elevation_mapping/blob/master/elevation_mapping/src/ElevationMap.cpp#L431

True, thank you. I will probably add this check then.

Hey, to me that looks like a URDF issue, i.e. your camera with respect to the base is not correct.