Repository navigation
navmap_tools: DEM files, Gazebo terrain, big point clouds; RViz colours - #43
Open
jmguerreroh wants to merge 1 commit into
Open
jmguerreroh wants to merge 1 commit into
jmguerreroh wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
navmap_tools: DEM files, Gazebo terrain, big point clouds; RViz colours
What the BigMap maps manager (
easynav_bigmap_maps_manager, easynav_plugins) needs to get its mapoutdoors, and the tools used to make its maps.
navmap_gis_tool
--dem-out FILE: the DEM of a place as a binary grid file (geo/dem_file.py: header with theorigin, the reference altitude, the resolution and the source), which the maps manager reads.
--dem-data-resolutionsamples the source at its own spacing and interpolates it bicubically;--dem-source ign | copernicus30 | mesh | synthetic(geo/ign.py: IGN MDT, Spain, 5 m;geo/mesh_dem.py: a DEM rasterised from a mesh, e.g. the collision mesh of a Gazebo world). A DEMmade with the same configuration is reused.
geo/terrain_export.py):--terrain-out+--world-template/--world-outwrite the terrain mesh (collision STL, textured OBJ) and a world from a template(@latitude@, @longitude@, @elevation@, @TERRAIN_DIR@).
sample_array) of the Copernicus grid, the tile mosaic and the PNOAorthophoto, which the DEM and terrain export sample over whole grids.
pointcloud_to_navmap
Streams ascii/binary PCD files block by block and reduces clouds above 5 M points by voxel
(
pcd_stream,voxel_cloud), so memory follows the extent of the map and not the number of points;several
--input;--fill-holescloses the holes a SLAM cloud leaves in its floors(
floor_holes);--min-surface-area,--max-surfaces; colour from the cloud'srgb; it sayswhich resolution the data holds. The meshing is
navmap_ros::from_points.navmap_rviz_plugin
NavMapDisplaypacked the vertex colours as ARGB whatever the render system: with OpenGL (ABGR)red and blue were swapped. It now uses the render system's own colour format.
Tests
colcon test --packages-select navmap_tools: new tests for the DEM file (round trip, a goldenfile, the headers the C++ reader of the maps manager refuses), the IGN and mesh sources, the reuse
of a DEM made with the same configuration, the terrain export and the C++ cloud tools: 562 tests,
no failures.
Independent of the navmap_core / navmap_ros PR (DistanceField, set_area, operator=, navmap_io);
neither needs the other.