Map Fusion

When valid control points and RTK data are available, the point clouds of multiple projects can be seamlessly merged automatically. When absolute coordinate information is available, the point cloud can also be converted to absolute coordinates. This avoids the layering of overlap areas caused by accuracy issues of the RTK or control points themselves when using global optimization alone.

Field Work

For field work specifications, refer to "Acquire Point Cloud Data with Absolute Coordinate".

1. For multi-map fusion, regardless of the fusion mode, to achieve better fusion, try to have a certain length of overlapping path between two adjacent maps. The recommended overlap length is > 15 m, with 15–30 m suggested. Keep the adjacent overlap area in feature-rich scenes as much as possible, and avoid degraded environments such as open areas, long corridors, and smooth tunnels.
2. When using control points, if the control points carry absolute coordinates, keep a scan overlap of > 15 m between adjacent projects. If the control points do not carry absolute coordinates, in addition to keeping a scan overlap of > 15 m between adjacent projects, you must effectively record control points within the overlap area and ensure that the device position and control point name are consistent when the two projects mark the same control point.
3. Minimum requirements for coordinate conversion: all maps have connections (relative control points or continued scanning), and there are at least 3 absolute control points across all maps (and the control points are not on the same line).
4. If the requirements are not met, data fusion cannot be performed properly.

Office Work: Data Processing

See the LixelStudio user manual.