.png)
.png)
.png)
Define “Deliverables” as a File Checklist Before Delivery
After capture with a SHARE3DCAM handheld simultaneous localization and mapping (SLAM) scanner such as the SHARE SLAM S20, SHARE SLAM S20 SE, SHARE SLAM S100, or the SHARE3DCAM C10 Series, delivery should follow the project agreement and include the agreed point clouds, coordinate and quality records, initial computer-aided design (CAD) deliverables, and project archives—not merely “a 3D model.” Different models do not change the responsibility principles; specific deliverables still depend on site conditions, processing workflows, and acceptance criteria.
Figure 1: Delivery and acceptance proceed through checklist agreement, delivery-package preparation, office review, independent checks, format review, and final acceptance.
Recommended Deliverable Structure
| Category | Recommended Files | Acceptance Focus |
|---|---|---|
| Original data and project | Complete original data and the agreed SHARE PointClouds Studio project directory | Complete directories, project opens successfully, and version information is clear |
| Point cloud deliverables | LAS, PLY, PCD, E57, or RCS | Scope, coordinates, units, coverage, and file version |
| Registration deliverables | original_name_registered.las, corresponding points, and error records | Reference and moving point clouds are clear; source files are retained |
| Coordinate deliverables | original_name_converted.las, control-point records, or XYZ parameter records | Coordinate system, units, transformation parameters, and review results |
| Quality reports | 3D check report, elevation check report, and independent check point table | Control points and check points are separate; tolerances have a written basis |
| Initial CAD deliverables | DXF and DWG files in the exported ZIP package | Manual review, layers/annotations, and opening validation in the target software |
| Imagery and viewing | Original/undistorted photos, trajectory, photo points, and optional 3D Gaussian splatting (3DGS) | Statement of viewing use and measurement boundaries |
| Support materials | Task status, issue records, and necessary logs | Retry process, software, and workstation environment are traceable |
Whether original data and the project directory are delivered should be specified in the contract or service confirmation. For projects involving privacy or confidentiality, also define access permissions, retention periods, and destruction methods.
How Should Registration and Coordinate Deliverables Be Accepted?
When segmented or repeated scans require manual corresponding-point registration, specify the reference and moving point clouds, select appropriately distributed non-collinear fixed feature points, inspect the preview and error, and generate _registered.las. Point cloud merging applies only to already aligned data and cannot serve as proof of registration. When an existing point cloud must be transformed into a project coordinate system, match at least three valid control points or use confirmed X/Y/Z translation, X/Y/Z rotation, and scale parameters. Verify easting, northing, elevation, length units, and coordinate system, then generate _converted.las. For a global navigation satellite system (GNSS)/post-processed kinematic (PPK) workflow, also document the external PPK tool-generated RTKLIB POS trajectory file, trajectory quality, and the source of fusion parameters.
Submit 3D and Elevation Checks Separately
3D Accuracy Checkspatially compares independent check points against corresponding positions in the point cloud usingMatching Calculation;Elevation Accuracy CheckusesMatching NeighborhoodandMatching Calculationto compare point-cloud elevations with check points;- Control points are used for solving and cannot simultaneously serve as independent check points;
- Office self-check: Verify coverage, trajectory, registration, coordinates, 3D/elevation reports, and file naming.
- Format review: Open the exported ZIP, inspect the DXF and DWG files, and check content and compatibility in the target CAD environment.
- Customer acceptance: Record passed, failed, and pending items one by one against the written baseline.
- Issue closure: Distinguish capture, reconstruction, registration, coordinate, drafting, and format issues. Perform supplementary scanning, recalculation, retry, or manual revision, and retain the updated records. Failed or canceled tasks can be retried. When technical support is required, retain the complete original data, project, deliverables, and logs. Login is required to upload logs; provide a contact, issue description, and workstation environment.
Frequently Asked Questions
Q: Can a scanning project deliver only one LAS file? Only if the contract explicitly requires nothing beyond the point cloud. When project coordinates or accuracy acceptance is involved, also submit the coordinate description, control/check records, and relevant reports.
Q: What is the difference between _registered.las and _converted.las? The former is generated after manual corresponding-point registration; the latter is generated after coordinate transformation using control points or known XYZ parameters. Neither overwrites the source point cloud.
Q: Can DXF be treated as an already accepted finished CAD deliverable? Not automatically. DXF and DWG files in the exported ZIP package are the software’s standard CAD deliverable and still require editing and review by professional CAD, BIM, or SketchUp personnel, plus validation in the target CAD software version.
Q: If 3DGS viewing looks excellent, can the point cloud and accuracy reports be omitted? No. 3DGS is for photorealistic viewing. Dimensions, coordinates, and accuracy acceptance must be based on the point cloud and independent inspection reports.
Q: What should be done if a customer finds a coordinate or drawing issue? First determine whether the cause is the control points, XYZ order and units, registration correspondences, manual drafting review, or format compatibility. Then follow the change or resurvey process and retain records.
