XGRIDSDocs
  • 简体中文
  • English
  • 繁體中文
  • 日本語
  • Deutsch
  • Español
  • Italiano
  • Français
  • Русский
  • Polski
  • Nederlands
  • 简体中文
  • English
  • 繁體中文
  • 日本語
  • Deutsch
  • Español
  • Italiano
  • Français
  • Русский
  • Polski
  • Nederlands
  • Lixel PortalCam Series

    • PortalCam P1

      • Product Overview
      • Basic Operation
      • Using the LCC Scan App
      • Maintenance and Care
      • FAQ
  • Lixel K Series

    • Lixel K1

      • Product Overview
      • Basic Operation
      • Device Activation and Connection
      • Scanning Workflow
      • Acquire Point Cloud Data with Absolute Coordinate
      • Map Fusion
      • Route Planning Suggestions for Typical Scenes
      • Precautions
      • FAQ
    • Lixel K2

      • Product Overview
      • Basic Operation
      • Device Activation and Connection
      • Scanning Workflow
      • Acquire Point Cloud Data with Absolute Coordinate
      • Map Fusion
      • Route Planning Suggestions for Typical Scenes
      • Precautions
      • FAQ
  • Lixel L Series

    • Lixel L2 Pro

      • Product Overview
      • Basic Operation
      • Device Activation and Connection
      • Scanning Workflow
      • Acquire Point Cloud Data with Absolute Coordinate
      • Measure Point
      • Appendix
      • FAQ
    • Lixel L3

      • Product Overview
      • Basic Device Functions
      • Device Activation and Connection
      • Data Capture
      • Capturing Absolute Coordinates
      • Appendix
      • FAQ
  • Accessories

    • Stick Light

      • Installation Guide
      • Basic Operation
      • FAQ
  • Lixel Studio

    • Version and Copyright
    • Installation and Activation
    • Software Interface
    • File Operations
    • Project Processing
    • Tools
    • 2D Drawing
    • Applications
    • Settings
    • Device Connection
    • FAQ
    • Usage Tips

      • Data Flow Overview
      • Software Licensing Guide
      • Understanding Scanner Accuracy Specifications
      • Point Cloud Registration Guide
  • Lixel CyberColor

    • LCC Studio

      • Getting Started
      • Version and Updates
      • Download and Installation
      • Interface Overview and Navigation
      • Before Reconstruction
      • Model Reconstruction
      • Single Model Reconstruction
      • Map Fusion
      • Aerial-Ground Fusion
      • Aerial Reconstruction
      • My Models
      • Other Features
      • Settings and Account
      • Converter
      • Publish to Third-Party Platforms
      • Video Reconstruction
      • FAQ
    • LCC Scene Editor

      • Version & Updates
      • Account & Login
      • Product Overview & Home
      • Editor Interface
      • Scene Navigation Modes
      • File
      • Settings
      • Edit Operations
      • Window
      • Global Toolbar
      • Assets & Properties
      • Left Toolbar
      • Viewpoints
      • Portal
      • Skybox
      • Annotations
      • Measurement
      • Flythrough
      • Scene Report
      • 3D Layout
      • Mini-Map
      • Preview Mode (Viewer)
      • Help
      • FAQ
      • Spawn Point
    • LCC Model Editor

      • Version and Updates
      • User Guide
      • Overview and Interface
      • File Operations
      • Selectors
      • Editing Operations
      • Measurement
      • Color Grading
      • Asset Management
      • Settings and Help
      • FAQ
    • Capture Guide

      • Overview
      • Capture Devices Overview
      • General Capture Principles
      • Indoor Scene Capture
      • Outdoor Scene Capture
      • Large-Scale Capture (Map Fusion)
      • Aerial-Ground Map Fusion Capture
      • Object Capture
      • People Capture
      • Video Reconstruction Capture
      • HD Enhancement
      • Control Points (Lixel P1)
      • FAQ and Troubleshooting
    • LCC Studio Linux

      • Product Overview
      • Architecture Guide
      • Installation and Deployment Guide
      • Container Startup Parameters Guide
      • CodeMeter Offline Licensing Deployment Guide
      • API Reference
      • Appendix - Developer Data Guide
      • Appendix - Error Code List
      • Single-Machine Multi-GPU Cluster Deployment QuickStart
    • Best Practices

      • Merging Multiple Large 3DGS Models
      • Aerial-Ground Map Fusion Workflow
      • Data Flow Overview
      • Software Licensing Guide
    • Version History
  • Plugin & SDK

    • Unreal

      • Introduction
      • Quick Start - Windows
      • Quick Start - Linux
      • Quick Start - Quest3
      • Editions and Licensing
      • Rendering
      • Tiled Rasterization (Experimental)
      • Visual Settings
      • Normals and Lighting
      • Scene Editing
      • Performance Parameters
      • Performance Guide
      • Third-party and Engine Plugin Integration
      • Proxy Mesh
      • Loading Animation
      • Collision
      • Navigation System Support
      • Single Layer Water Support
      • Localization
      • FAQ
      • Troubleshooting
      • Logging and Diagnostics
      • Contact Us
      • Best Practices

        • Relighting 3DGS with a LixelStudio Mesh
        • Per-camera Independent Rendering
      • API Reference

        • ALCCActorBase
        • ULCCComponentBase
        • ULCCComponent
        • ULCC2Component
        • SOG / SPZ / PLY Actors
        • ALCC2ProxyMesh
        • ALCCClippingVolume
        • ALCCSectionPlane
        • ALCCLoadVolume
        • ULCCUtilLibrary
        • Enums
        • Structs
      • Changelog

        • v3.5.0
        • v3.4.0
        • v3.3.1
        • v3.0.0
        • v2.2.1
        • v1.0.0
        • v0.9.0
        • v0.8.0
        • v0.7.1
        • v0.6.1
        • v0.5.2
        • v0.4.1
        • v0.4.0
        • v0.3.0
        • v0.0.5
        • v0.0.4
        • v0.0.3
        • v0.0.2
        • v0.0.1
    • Unity

      • Unity SDK Introduction
      • Technical Features
      • Development Environment Requirements
      • PC Quick Start Guide
      • Project Settings Optimization Guide
      • Pico 4 Ultra Development Guide
      • Pico 4 Ultra PC Streaming Guide
      • Quest 3 Development Guide
      • Quest 3 PC Streaming Guide
      • OpenXR Development Guide
      • Pico 4 Ultra Business Streaming Guide
      • Glossary
      • FAQ
      • Contact Us
      • Feature Development Guide

        • Multi-Scene Mixed Rendering Development Guide
        • Shadow Receiving Development Guide
        • Real-Time Lighting Development Guide
        • Multi-Camera Rendering Development Guide
        • High-Resolution Image Rendering Development Guide
        • LCC and LCC2 Data Format Compatibility Development Guide
        • Loading Effect Development Guide
        • Mip Rendering Mode Switching Development Guide
        • Edge and Corner Snapping Development Guide
        • Projected Decal Development Guide
        • Video Projected Decal Development Guide
        • Highlight Development Guide
        • Real-Time Clipping Development Guide
        • Color Adjustment Development Guide
        • Getting Scene Mesh Data Development Guide
        • Editor Mode Development Guide
        • Render Performance Parameter Configuration Guide
        • Application and Data Co-packaging Development Guide
        • Collision System Development Guide
        • macOS Development Permission Issue Guide
        • iOS Device Compilation and Packaging Development Guide
      • API Reference

        • LCCManager
        • Renderer
        • Data Types
      • Changelog

        • v2.3.0
        • v2.2.10
        • v2.2.0
        • v2.1.19
        • v2.0.14
    • Web

      • Introduction
      • Rendering Performance Optimization Guide
      • Graphics Configuration
      • WebGPU Development Guide
      • FAQ
      • API Reference

        • LCCObject::checkRenderNextFrame
        • LCCObject::clearRenderNextFrame
        • LCCObject::ecef2Prj
        • LCCObject::getBounds
        • LCCObject::getEnvInstancedMesh
        • LCCObject::getInstancedMesh
        • LCCObject::getLodInfos
        • LCCObject::getOriginPosition
        • LCCObject::getProjectionCoordinateSystemInfos
        • LCCObject::hasCollision
        • LCCObject::hasEnvironment
        • LCCObject::hasShcoef
        • LCCObject::intersectsCapsule
        • LCCObject::intersectsRayExt
        • LCCObject::intersectsRayFromOriginExt
        • LCCObject::intersectsSphere
        • LCCObject::lowerToBottom
        • LCCObject::prj2Ecef
        • LCCObject::raiseToTop
        • LCCObject::raycast
        • LCCObject::raycastFromOrigin
        • LCCObject::setAlpha
        • LCCObject::setClipBox
        • LCCObject::setClipPlane
        • LCCObject::setClipPrism
        • LCCObject::setEndLod
        • LCCObject::setLodAutoLevelUp
        • LCCObject::setMaxDistance
        • LCCObject::setMaxNodeSplats
        • LCCObject::setMaxSplats
        • LCCObject::setMipFilter
        • LCCObject::setOriginPosition
        • LCCObject::setPointsColor
        • LCCObject::setRenderState
        • LCCObject::setRotation
        • LCCObject::setScale
        • LCCObject::setSemantic
        • LCCObject::setSemanticColor
        • LCCObject::setSmooth
        • LCCObject::setStartLod
        • LCCObject::setTranslation
        • LCCObject::setVisible
        • LCCObject::togglePointsDisplayMode
        • LCCObject::useEnvironment
        • LCCObject::useShcoef
        • LCCRender::clearIndexDB
        • LCCRender::dispose
        • LCCRender::load
        • LCCRender::setCamera
        • LCCRender::unload
        • LCCRender::update
      • Changelog

        • v0.6.4
        • v0.6.3
        • v0.6.2
        • v0.6.1
        • v0.6.0
        • v0.5.5
        • v0.5.4
        • v0.5.3
        • v0.5.2
        • v0.5.1
        • v0.5.0
        • v0.4.1
        • v0.4.0
        • v0.3.1
        • v0.3.0
        • v0.2.0
    • Lixel OpenAPI

      • Overview
      • Connection & Authentication
      • Message Model & Codec
      • Interface Catalog
      • Real-time Data
      • Project File Access
      • Error Codes
      • Python

        • Quick Start
        • Client Wrapper & Tools
        • FAQ
      • C++

        • Quick Start
        • Client & Examples
        • FAQ
  • API

    • Structured Spatial Modeling

      • Access Guide
      • Modeling Workflow
      • API Reference
      • Temporary Upload Credentials
      • Error Codes

Point Cloud Registration Guide

Applicable software: Lixel Studio (point cloud editing module)

Intended users: surveying and modeling users for whom Map Fusion is not usable, or who need to split and process large scenes.

Overview

Point cloud registration refers to post-processing alignment in Lixel Studio of multiple point cloud results that have already been generated, so that they are unified into the same coordinate system and stitched into a complete scene.

Difference from Map Fusion:

  • Map Fusion: relies on capturing according to the specification (RTK enabled, tie points with the same name placed, 15 m of overlapping trajectory), and the software registers automatically based on coordinates or tie points. It imposes strong constraints on capture quality.
  • Point cloud registration: targets point cloud results that have already been generated and aligns them afterwards based on overlapping features. It does not require the capture stage to meet the fusion specification. It is a fallback when fusion cannot be used, and also a way to stitch large scenes after they are processed in groups.

When registration is needed

Point cloud registration is mainly used in the following situations.

Map Fusion was not captured per specification and cannot be recaptured

During capture, RTK was not enabled and no tie points with the same name were placed between adjacent data segments, and the overlapping trajectory is only a few meters, so Map Fusion cannot be used; meanwhile the site has been vacated or recapture is not possible. In this case you can only register the point cloud results that have already been generated.

A large scene exceeds the Map Fusion limit

  1. The processing limit of Map Fusion in Lixel Studio is 10 maps / 200 minutes. Large scenes exceeding this limit are not guaranteed to be processable. When a user still gets an error, the only option is to split into several groups and complete Map Fusion separately. The grouped fusion results are affected by the edge accuracy of each group and often cannot be stacked and merged directly; registration is needed to align group to group.
  2. Display limit: the software has an upper limit on the number of points it can display, currently 4.3 billion. Point clouds exceeding this will not be displayed in full.

The result needs absolute coordinates, but some maps lack correct absolute coordinates

The result requires absolute coordinates, but the following situations cause some maps to be unable to obtain correct absolute coordinates directly:

  • The App coordinate system was set incorrectly during capture, making that map's absolute coordinates wrong;
  • Some maps, limited by field conditions, could not capture RTK or place absolute control points and have only relative coordinates.

In this case you can register these maps against a reference map that has correct absolute coordinates, passing the correct absolute coordinates over through registration (see the coordinate handling section).

Choosing an approach

SituationRecommended approach
Site can be recaptured and the limit is not exceededRecapture per specification first, use Map Fusion
Cannot recapture, not captured per specificationPoint cloud registration
Exceeds the 10 maps / 200 minutes limitGrouped Map Fusion + inter-group registration
Some maps lack/have wrong absolute coordinates, result requires absolute coordinatesRegister against a reference map with correct absolute coordinates to pass coordinates over

Prerequisites and principles

Core principle

The point clouds to be registered must have an overlapping region, and within that region there must be identifiable common features. Registration is based on these common features, not on coordinates, so the amount and quality of overlapping features directly determine whether registration succeeds.

Requirements for overlap and features

  • Keep an obvious overlapping region between adjacent point clouds.
  • The overlapping region should contain clear, easily identifiable geometric features (such as wall corners, columns, steps, equipment outlines).
  • Avoid using only large flat planes, weak-texture areas, or repetitive structures as the basis for registration; such areas lack uniqueness and easily cause misalignment.

Definition and selection of registration points

A registration point is the same actual location corresponding across different maps. Registration solves the rigid transformation between maps using multiple registration points, so the quality of the selected registration points directly affects registration accuracy.

Selection principles:

  • Choose positions with obvious, easily identifiable features, such as the corner points of a landmark, or the outline points of an object with high reflectivity and a clear outline.
  • Use as many registration points as possible, distributed in different positions of the overlapping region, avoiding concentration in one place.
  • After adjustment, review the registration report, remove registration points with large errors, and reselect at other positions.

Registration points by scene type

Different scenes have different feature distributions, so the point-picking strategy differs.

Indoor scenes

  • Features are abundant (wall corners, doors and windows, columns, furniture), and common features are generally easy to find.
  • For symmetric, repetitive structures (such as identical corridors or rows of workstations), it is not recommended to pick points there unless the order can be distinguished quickly.

Outdoor scenes

  • Features are relatively sparse; prefer stable ground features such as building corners, pole-like objects, and steps.
  • Avoid using movable or unstable objects such as trees and vehicles as registration features.

Mixed indoor-outdoor scenes

  • Use the indoor-outdoor transition area (entrance, porch, connecting corridor) as the key overlap zone.
  • Make sure there are enough common features on both sides of the transition zone, to avoid seam misalignment caused by indoor and outdoor being handled separately.

Coordinate handling of registered point clouds

General principle

Registration uses the coordinate system of the reference map chosen by the user; the other maps to be registered are aligned onto the reference map and the reference map's coordinate offset is applied.

Two coordinate cases

  • A map without absolute coordinates registered with a map that has absolute coordinates: use the map with absolute coordinates as the reference map; after registration the map without absolute coordinates obtains absolute coordinates.
  • Maps in different coordinate systems registered together: choose one of the coordinate systems as the reference; after registration the other maps are unified into that reference coordinate system, bringing multiple maps into one coordinate system.

General registration steps (manual registration)

The point cloud editing tools of Lixel Studio provide manual registration, which is the general method of registration.

Example with different absolute coordinate systems

Import each group of point cloud results to be registered, then:

  1. Use Lixel Studio (version v4.1.1 or above is required) to process each one individually, to optimize the accuracy of each map and remove noise.
  2. Point cloud 1104_1 has the coordinate system CGCS2000:
Import point cloud in CGCS2000
  1. Point cloud 1104_2 has the coordinate system WGS84. When importing point clouds in different coordinate systems, choose "Input":
Import point cloud in WGS84
  1. Switch the point cloud rendering mode to "Intensity". If you use "True Color" mode, coloring errors may be introduced; decide as appropriate.
  2. Select both point clouds, click "Tools" - "Manual Registration", then click the toggle icon to select your base map. The base map's coordinate system is the coordinate system of the registration result, and the left viewport is the base map:
Select the base map
  1. Browse the point clouds in the left and right viewports, identify the area where trajectories overlap, click "Pick Point", and find the same feature point in the overlapping region. There is a magnifier above the cursor for easier observation. (If the overlapping region has no shared capture trajectory, the registration error will be larger.)
Pick corresponding points in the overlap
  1. Keep clicking "Pick Point" to enter the next selection. If you pick the wrong one, click the delete icon on the right to remove that pair. Once multiple point pairs are evenly distributed over the overlapping region, click "Register" to see the RMSE error of all points; the smaller the better. Before confirming you can repeatedly pick and delete points and watch the error value, until it can no longer be reduced, which means the current registration has reached its limit.
Register and check the RMSE error
  1. Click "Confirm" to exit registration. The registered point cloud result is imported automatically; after loading you will see a point cloud whose name starts with manual_aligned_:
Registered result imported automatically
  1. Render the point clouds in different colors and observe the overlap between 1104_1 and the manual_aligned point cloud. Using the point measurement tool you can see that the coordinate system is already consistent with the base map. Select both point clouds, merge and export:
Merge and export the registration result

Indoor example without a coordinate system

Handle indoor corridor/passage scenes with low overlap between upper and lower floors in the same way. Because the structures are similar it is easy to pick the wrong position. Below is a registration example of adjacent floors 22F and 23F.

  1. Both imported maps have no absolute coordinates and an offset of 0, so just confirm directly. With no coordinates to compare, which one is the base map is up to the user. First find the overlapping region:
Indoor low-overlap region
  1. Double-click the point-picking position, zoom in nearby, hold the left mouse button and move to observe, avoiding picking the wrong point because other point clouds block the front:
Zoom and observe while picking points
  1. Arrange points evenly across space; indoors you can choose points such as the ceiling and stair corners:
Indoor point-picking example
  1. Click "Register" - "Confirm", and after the point cloud is loaded automatically, render it in a single color and use the 3D crop box to cut inside and observe the floor and ceiling. You will find the registration is mediocre and the positions at the arrows do not overlap ideally. However this is already as expected for point cloud registration, and further attempts cannot improve it. If the user cannot accept the current result, they can try third-party software for registration, or simply recapture according to the fusion rules:
Indoor registration result check

Optional: ICP registration

Lixel Studio also provides ICP registration as an optional method besides manual registration, to be used as needed.

Usage limitation (important): ICP registration requires the two point clouds to have as much as 70% overlap to achieve an obvious effect. Ordinary field capture rarely reaches such high overlap, so ICP registration is not a generally recommended step and is only used as a supplement when the overlap is truly sufficient.

How to use: first achieve a coarse registration with the regular manual-registration procedure, then select the coarse-registration result map and the base map, and click "ICP Registration". A dialog will appear to confirm the point clouds to be registered.

The example below only demonstrates the method. Because 22F and 23F do not overlap enough, the ICP registration does not improve and may even be worse. You can also consider trying third-party software for ICP:

ICP registration example

Quality check and common issues

Expected result and registration accuracy

Registration accuracy is referenced by the registration report value actually produced by manual processing. In theory, the smaller the value, the better the overlap at the overlapping positions.

Note that registration is a rigid transformation and cannot make the overlapping area seamlessly stitched the way fitting the same feature would, so the registration error cannot be eliminated completely and can only be reduced as much as possible. Ways to reduce the error:

  • Use as many registration points as possible;
  • After adjustment, remove registration points with large errors from the report and reselect them at other positions.

If after multiple attempts the error stays at a similar level, it means the registration accuracy of this group of maps has reached its lowest achievable level, and there is no need to keep adjusting.

Checking the registration result

After registration, focus on the following:

  • Layering: whether the same plane is split into upper and lower layers.
  • Misalignment: whether the same structure in the overlapping region is aligned and whether the seams fit.
  • Overall consistency: whether the stitched whole is distorted or offset.

Common issues and troubleshooting

SymptomPossible causeSuggested handling
Registration fails or is obviously misalignedInsufficient overlap, features too weakChoose an overlap region with richer features, or add tie feature points
Layering at the seamPoor edge accuracy, inaccurate tie pointsReselect more stable common features, avoid weak-texture areas
Coordinate result does not meet expectationsWrong reference map chosen, coordinate offset not applied correctlyCheck the reference map and coordinate system settings
ICP registration has no effectOverlap less than 70%Use manual registration, or use ICP only when overlap is sufficient

Best practices (preventive advice)

  • During capture, reserve sufficient overlap between adjacent data as much as possible, to leave room for later registration.
  • Use Map Fusion when possible; use registration as a means when fusion is unavailable or for splitting large scenes.
  • Be clear about the capability boundary between registration and fusion: fusion relies on standard capture, registration relies on overlapping features.
  • In weak-feature or repetitive-feature scenes, get into the habit of placing target papers to help later identify reflection intensity and pick points.