Large projects are easier to manage when the team starts from the agreed deliverables. Separate measurement-grade point-cloud work, computer-aided design (CAD) drafting, and three-dimensional Gaussian splatting (3DGS) visualization. 3DGS supports photorealistic viewing; measurement, accuracy checks, and drawing production should use the point cloud.

This workflow applies to data from SHARE SLAM S20, SHARE SLAM S20 SE, SHARE SLAM S100, and the SHARE3DCAM C10 Series processed in SHARE PointClouds Studio.

Protect and Organize the Source Data

Figure 1: Limit the active working extent with two-dimensional or three-dimensional cropping and reduce unnecessary parallel tasks.

Copy the complete device data directory without changing filenames or folder structure, and retain an untouched source copy. Organize responsibilities and working scopes by deliverable, floor, room, or construction zone, then use two-dimensional or three-dimensional cropping to limit the active extent. If separate capture tasks or segments are required, plan and create them on site in the SHARE Capture app; cropping in SHARE PointClouds Studio only limits the active post-processing extent and does not split one capture into separate capture tasks. These are team and processing conventions rather than software-generated project structures or packaged engineering projects.

A practical team structure separates:

• source data;
• active processing results;
• reviewed deliverables;
• backups and archived records.

Agree on naming, coordinate reference, software version, ownership, and review status before several people exchange files.

Processing Workflow

1. Review coverage and trajectory. Check for voids, drift, noise, and incomplete routes. When undistorted photographs are available, use the linked trajectory, photo points, photographs, and two-dimensional or three-dimensional view to inspect the affected location.
2. Crop the working scope. Remove irrelevant areas from the active task as post-processing scope control; this does not create separate field capture tasks. Remove irrelevant areas from the active task and avoid running more concurrent tasks than the workstation can support. Keep the original dataset intact.
3. Process the required point-cloud outputs. Record settings, software version, source dataset, and output location so another team member can reproduce the result.
4. Register multiple scans manually. Select a reference point cloud and a point cloud to be registered. Pick matching fixed features in both viewports, distribute the points across the overlap, and avoid clustered or collinear selections. Review overlap and errors, then generate original_name_registered.las. Merging does not solve spatial relationships; register first and merge only after alignment is accepted.
5. Transform coordinates. Import and match at least three valid control points, or enter confirmed X/Y/Z translations, X/Y/Z rotations, and scale. Save the result as original_name_converted.las without overwriting the source.
6. Run independent checks. Perform separate three-dimensional and elevation checks. A control point used to calculate the transformation must not also be used as an independent check point.
7. Prepare and review deliverables. Export the agreed point-cloud formats and verify file readability, coordinates, units, naming, and completeness.

External PPK Trajectories

Post-processed kinematic (PPK) computation occurs in an external tool using rover, base-station, and navigation data. After checking the generated RTKLIB POS trajectory for continuity and solution quality, select it in SHARE PointClouds Studio only as the Trajectory Source in GNSS Fusion. This global navigation satellite system (GNSS) input does not replace control points or independent checks.

Storage and Collaboration Checks

CAD Delivery Boundary

Sections and plan views can support CAD drafting, but complex furniture, occlusions, inclined surfaces, and irregular structures require manual interpretation. CAD drafting export generates both drawing exchange format (DXF) and DWG files in the exported ZIP package. The ZIP is an export container for those drawing files, not a complete engineering project archive. RVT, IFC, and complete building information modeling (BIM) deliverables require downstream professional modeling and verification.

Network and Support Boundary

Without an available network, login may not complete, some advanced functions such as 3DGS may not work normally, and logs cannot be uploaded. When a task fails, retain the source data, project, outputs, and local diagnostic information. Record the failing stage, full software version, workstation configuration, and reproduction steps. Upload only sanitized samples through the approved support channel when network access is available.

Frequently Asked Questions

Should I upgrade the workstation before reducing a large working scope?

First crop the active scope and reduce concurrent tasks. Then compare the remaining workload with the current SHARE PointClouds Studio requirements and the workstation resources.

How should multiple scans be combined?

Complete manual corresponding-point registration, review the errors, and generate _registered.las before merging accepted results.

How many control points are required for coordinate transformation?

Use at least three valid control points, unless the project already provides confirmed translation, rotation, and scale parameters. Independent checks are still required.

Can the exported CAD package be issued without drafting review?

No. The exported ZIP contains both DXF and DWG files, but linework, layers, annotations, units, coordinates, and critical dimensions require manual review.

Can 3DGS replace point-cloud acceptance?

No. 3DGS is for photorealistic viewing, not measurement or accuracy acceptance.