6.6 L2 Pro and K2 Data Transfer and Processing Preparation

Device Storage and Transfer Method

The L2 Pro and K2 store scan data differently. The L2 Pro stores scan data on a 1 TB internal SSD. The K2 stores scan data on 512 GB internal eMMC. Neither device uses a removable SD or TF card. This means you cannot do mid-session storage swaps; instead, plan storage management around end-of-day transfers.

Transfer Methods

Project Folder Structure on Device

When you open the device's internal storage in your file manager, you will see a directory structure containing one folder per scan segment. Each folder is a complete project file containing the SLAM trajectory, raw LiDAR data, camera frames (for K2), and metadata.

Workstation Folder Organization

How you organize transferred data on your workstation determines how easy or painful processing will be. A consistent structure makes it possible to find files months later, hand projects off between people, and run multiple processing jobs without confusion. An ad-hoc structure makes all of these things harder.

Recommended Project Folder Structure

Naming Conventions

The naming convention for individual scan segment folders should match the convention used during scanning, as documented in section 6.2. Use floor or zone identifier plus segment number (FL1_S01, FL1_S02, B1_S01).

Pre-Processing Verification Checklist

Before opening LixelStudio or LCC Studio for the first time on a project, verify each of the following. Most processing failures trace back to one of these problems being missed during data preparation. Catching them now saves hours of restarted processing later.

Scan Project Folder Verification

• Each project folder must be complete. A folder that was interrupted during transfer (USB unplugged early, workstation went to sleep) will be missing files. The folder size is the easiest indicator: a 5-minute scan should produce hundreds of megabytes; a 30-minute scan can produce several gigabytes. A folder that is significantly smaller than expected was not fully transferred.
• Folder names must match the scanning convention. Inconsistencies between the convention you used during scanning and the names on disk make multi-segment processing harder than necessary. Rename folders now, before processing starts.
• Folder structure inside each segment must be intact. If you accidentally extracted files out of a project folder thinking they were copies, return them. The internal structure is required by both processing pipelines.

Workstation Resource Verification

• Available RAM: LixelStudio requires approximately 2 GB of RAM per minute of scan data. A 30-minute scan requires approximately 60 GB. A 60-minute scan requires approximately 120 GB. Verify your workstation has the required RAM before processing. A scan that exceeds available RAM will fail processing or run extremely slowly.
• Available disk space: processing produces intermediate files that can be 3 to 5 times the size of the source data. Verify you have at least 5x the source data size in free disk space on the working drive before starting.
• GPU drivers and version: for LCC Studio, verify your NVIDIA drivers are up to date. AMD GPUs are not supported by LCC Studio. Older driver versions can cause processing failures with no clear error message.
• Software version: verify you are running current LixelStudio v4.0, which supports L2 Pro Drone Mode and current handheld firmware. Older versions may fail to import newer firmware project files.

Aerial-Ground Fusion Verification (when applicable)

• Coordinate system check: verify both ground scan and drone data were collected in WGS84. A coordinate system mismatch is unrecoverable in processing.
• RTK status: verify the ground scan achieved Fixed RTK throughout the fusion point areas. Float or Single Point RTK in those zones will cause fusion alignment to fail.
• Folder structure for the chosen pipeline: for LCC Studio, verify takeoff/landing image folders are named to match the fusion point names assigned during the PortalCam scan. For LixelStudio, verify the Drone/Lixel parent folder structure is in place and the XGRIDS Pose tool has been run on the drone data.
• Drone image count: verify the total drone image count is between 100 and 10,000 for LCC Studio. Below 100 images, fusion alignment will be unreliable. Above 10,000 images, processing time becomes impractical.

Backup Before Processing

Once data has been transferred and verified, back up the raw data to a secondary location before opening any processing software. Processing modifies project folders in place. A processing failure that corrupts project files cannot be undone if you do not have a clean backup.

Backup Strategy

• Keep raw data on the device until processing is complete and verified. Do not delete project folders from the L2 Pro or K2 internal storage until processing has produced a usable output and you have verified that output meets the deliverable requirements.
• Copy raw data to a secondary location before processing. Network-attached storage, an external SSD, or a cloud backup all work. The point is to have an unmodified copy available if processing damages the working copy.
• Drone images: copy from SD card to working drive, then keep an additional backup before processing. Aerial-ground fusion processing in LCC Studio can take 24 to 48 hours and represents significant client cost if it has to be repeated.