8.6 LixelStudio Tools
Reference for every Project Processing setting, coloring option, processing mode, advanced processing option, and coordinate transformation parameter in LixelStudio. For point cloud editing tools and export formats, see 8.7 LixelStudio Editing and Export.
Project Processing Settings
The Project Processing dialog is the primary interface for converting raw scan data into a processed point cloud. It opens after importing raw data into a new project. All configuration decisions below must be set before clicking Start. They cannot be changed after processing begins.
Coordinate system defaults to CGCS2000. Confirm the coordinate system before clicking Start. Processing with the wrong coordinate system produces output that cannot be accurately transformed after the fact, requiring a full reprocessing run.
Device support in LixelStudio. L3, L2 Pro, and K2 are all fully supported for Single Scan, Map Fusion, and all reconstruction options. PortalCam data does not process in LixelStudio; PortalCam scans require LCC Studio.
For the L3, XGRIDS lists map fusion constrained by control points or matched by region selection without them, multi-session fusion and adjustment, PPK post-processing, stable mapping in low-feature environments, local point cloud enhancement, mesh reconstruction, stockpile volumes, and automatic privacy blurring.
Core Settings
RTK Setting Panel
When the GNSS checkbox is enabled and the RTK module is selected, clicking RTK Setting opens a panel showing the validity chart for the RTK data collected during the scan. This chart plots the RTK fix quality against the scan timeline, showing which portions of the scan had Fixed status and which had Float, Single, or no fix.
The RTK valid data count must be greater than 100 to achieve successful coordinate transformation in LixelStudio. If the valid count is below this threshold, process without RTK (uncheck GNSS) or provide GCPs to anchor absolute coordinates. Do not attempt to process with poor RTK data; the result will be a point cloud with incorrect or inconsistent absolute coordinates.
Coloring Options
LixelStudio supports two coloring sources. The correct choice depends on whether an external panoramic camera was used during the scan. Selecting the wrong option results in either no color or misaligned color on the point cloud.
External Camera Requirements
When using external camera coloring, the camera video files must be placed in the external_data subfolder of the project before processing. The external camera must have been started within 5 seconds of the scan start to maintain time synchronization.
Recommended external camera settings for LixelStudio compatibility: timelapse mode (not normal video), 6K resolution, 24 Hz frame rate, automatic exposure, standard color profile. Confirm the recording mode in the field before starting the scan; mode mismatches produce coloring failure during processing.
Processing Modes
The Mode dropdown on the Project Settings panel offers Standard, Robust, Narrow Space, Vehicle, UAV, and Standard is the default. The correct mode depends on the scanning environment and how the device was mounted. Using the wrong mode either reduces quality or causes the processing to fail outright.
Standard
General scenes. The first choice for the initial processing attempt in typical interiors and exteriors. Where conditions were less than ideal, expect to reprocess in Robust.
Robust
Scenes requiring higher processing stability. Switch to it after a Standard failure, particularly when the processing report shows "LIO Too Few, Please Try Robust Mode" or trajectory drift, and reprocess the same raw data. It raises the mapping success rate, though accuracy may be compromised.
Narrow Space
Tight, structurally constrained environments such as tunnels, mine shafts, and extended corridors. It raises reconstruction success within 1,640 ft (500 m); split a longer run into shorter scans and fuse them. It risks failure in regular open-plan environments. For the L3, XGRIDS lists stable mapping in low-feature environments such as tunnels and utility corridors as a LixelStudio feature.
Vehicle
Configured for scans captured from a moving vehicle where the scanner is fixed in place and the motion profile is continuous and smooth. Not for handheld use. Requires the matching Vehicle mount method. Applicable to the L2 Pro (the L3 vehicle mount is in development); K2 is a handheld-only device and does not support a vehicle-mount configuration.
UAV
Configured for L2 Pro aerial scans on compatible DJI drone platforms (M350 RTK, M300 RTK). The RTK module must be removed for drone use. Requires the matching UAV mount method. K2 is a handheld-only device and does not support drone mode. A drone mount for the L3 is in development for the DJI Matrice 400.
Aerial datasets typically show larger absolute errors than handheld projects. Field results suggest several centimeters RMSE compared to 3 cm handheld, but no published XGRIDS specification exists for aerial accuracy. Always validate aerial results against independent check points before using them for design work.
Advanced Processing Options
These settings appear in the Advanced Setting section of the Project Processing dialog. Most are disabled by default. Enable them only when the specific scenario described applies.
Coordinate Transformation
The coordinate transformation panel is accessed via the RTK Setting dialog when GNSS is enabled. It configures the source coordinate system (the system used by the RTK receiver during capture) and the target coordinate system (the delivered output coordinate system).
Default System
LixelStudio defaults to CGCS2000 (China Geodetic Coordinate System 2000) as both the source and target ellipsoid. For projects outside China or projects requiring delivery in a different coordinate system, the source and target must be reconfigured before processing.
US projects. For most US deliverables, set the target coordinate system and ellipsoid to the delivery system itself, with its projection parameters taken from the EPSG record, rather than leaving the target on WGS84. Most US zones are a UTM zone or a Transverse Mercator state plane zone; Lambert Conformal Conic zones are not supported by the projection engine, and US survey feet output is not native and needs a conversion from metric after processing. The method is on 4.6 Coordinate Systems. The source coordinate system depends on the RTK receiver configuration during capture; confirm with the field crew before processing. The L3's real-time coordinate conversion supports WGS84 and CGCS2000 only, so any other delivery system is configured here.
Key Configuration Parameters
Coordinate system mismatch is not recoverable without reprocessing. If the wrong target system is selected at processing time, the resulting point cloud has incorrect real-world coordinates. There is no post-processing fix. Reprocess from raw with the correct target configuration.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer

