What Are 5 Common SHARE SLAM Scanning Mistakes and How Can You Avoid Them?
On this page
Avoid Five Common Capture and Processing Errors
Five recurring capture risks are remaining stationary too long, stopping or turning abruptly, failing to close the route, interrupting the save process, and forcing an excessively long scan into one session. Preventing them can reduce rework, but it does not replace on-site coverage checks, trajectory and photo review, or verification with separate independent check points.
The effect of each risk depends on site conditions, route, model configuration, and processing settings. The workflow below applies to renovation measurement, building inspection, as-built surveying, underground or tunnel projects, historic buildings, and steel structures.

Figure 1: The five common operating mistakes correspond respectively to monitoring while moving, turning at a steady pace, overlapping a closed loop, confirming that saving is complete, and capturing by zone.
Mistake 1: Remaining Stationary for Too Long
What it looks like: Standing still in a room to inspect the point cloud or wait for the preview, or lingering in one place for an extended period. Why it is a problem: Simultaneous localization and mapping (SLAM) relies on continuous movement to acquire new features. Remaining stationary for too long can degrade positioning, and the trajectory may jump when movement resumes. Correct approach: Monitor the preview while walking, and do not stop longer than necessary.
If you need to inspect something, make a quick loop or return to the closed-loop route.
Mistake 2: Stopping or Turning Abruptly, or Walking Too Fast
What it looks like: Spinning around at a corner, walking quickly to save time, or stopping suddenly. Why it is a problem: Sudden speed changes can cause motion blur and trajectory jumps. Turning too quickly can produce an immediate loss of features, and the affected section will usually need to be rescanned. Correct approach: Walk at a steady pace. Slow down at corners and return to normal speed after turning. Keep the front of the device stable.
Mistake 3: Failing to Close the Loop
What it looks like: Ending a scan after walking a U-shaped or L-shaped route through a room, without returning to the starting point. Why it is a problem: Without loop closure, the workflow has fewer opportunities to constrain accumulated SLAM drift, so alignment errors may become more visible over longer distances. Correct approach: Complete at least one closed loop in every room, returning near the starting point and overlapping part of the initial route.
Mistake 4: Powering Off or Removing the Card Before Saving Is Complete
What it looks like: Powering off or removing the TF card immediately after finishing the route, or leaving before the files have finished saving. Why it is a problem: Data may still be writing. Powering off or removing the card too early can cause incomplete data, corrupt files, or files that cannot be processed. Correct approach: Wait until the app confirms that saving was successful before powering off or removing the card.
If saving fails, first create a backup, check the card-slot contact, and confirm that the TF card is a high-speed card rated U3/V30 or above and formatted as NTFS.
Mistake 5: Forcing a Single Scan Over an Excessively Long Distance or Duration
What it looks like: Trying to scan an entire building or factory in one pass, resulting in an excessively long scanning session or route. Why it is a problem:
The longer the scan and the more complex the route, the greater the risks of accumulated drift, feature degradation, and post-processing failure. Correct approach: Scan by zone, with a separate closed loop for each floor or large area. Afterward, in SHARE PointClouds Studio V2.6, choose the reference point cloud and the point cloud to be registered. Manually pick at least three evenly distributed pairs of clear corresponding fixed feature points, review the overlap/error preview, and generate the registered result before merging if needed. This workflow is manual corresponding-point registration and does not align scans on its own.
Scan-Quality Self-Check Checklist
After scanning and before leaving the site, check each item:
Frequently Asked Questions
Q1: I have already scanned and found drift. What should I do? First retain the raw data and use the SHARE Capture app’s field trajectory preview, live point-cloud coverage, and save status to determine whether the field data is complete. If the site was captured as separate scan tasks, process the tasks separately and then use manual corresponding-point registration in reliable overlap areas before merging. If a single complete scan was already captured, post-processing cannot split it into separate reconstruction tasks; it can only crop or delete unwanted point-cloud data. If critical areas are missing or the trajectory is clearly abnormal, recapture the area using an adjusted route rather than treating post-processing as a way to restore missing field data.
Q2: If I notice a mistake halfway through a scan, do I have to start over? Not necessarily. If the issue is local, you can supplement the affected area. If the route is fundamentally flawed—for example, it does not close—rescanning that space is recommended.
Q3: Are these mistakes caused by the device? These issues may result from site features, materials, the route, storage, or device status and cannot be attributed to the device based on the result alone. Review the checklist first and preserve the logs. If an issue recurs or cannot be reproduced, submit the device model, software version, and a de-identified sample to technical support.
Q4: What should I do if real-time positioning becomes weak during continuous indoor-outdoor capture? During capture, monitor the real-time kinematic (RTK) status indicators in the SHARE Capture app and record the transition location. Back at the computer, when the required observations are available, generate an RTKLIB POS trajectory file in an external post-processed kinematic (PPK) tool and select it in SHARE PointClouds Studio only as the Trajectory Source in the global navigation satellite system (GNSS) workflow, GNSS Fusion. You can also use control points or apply coordinate transformation to an existing point cloud. Whichever method you choose, verify the result with separate independent check points rather than reusing control points.
Q5: What drawing and model files are available after scanning and drafting? SHARE PointClouds Studio supports computer-aided design (CAD)-assisted drafting. CAD drawing export simultaneously generates drawing exchange format (DXF) and DWG files and includes them in the exported ZIP package. Those drawings still require manual review. RVT, IFC, complete building information modeling (BIM) models, and SketchUp deliverables remain downstream professional workflows. 3D Gaussian splatting (3DGS) is intended only for photorealistic viewing.
PROJECT SUPPORT

