3DGS
Point cloud registration, done right the first time.
Target-based, cloud-to-cloud, or geo-referenced — to survey-grade tolerances (typically ±2–6 mm depending on equipment and project). Clean overlaps. Documented control. The step the saturated outsourcing market mostly skips and hopes you don't notice.
A registered cloud your team can actually use downstream.
Multiple registration methods
Target-based, cloud-to-cloud, and geo-referenced — chosen for what your project requires, not what's easiest for us.
Survey-grade tolerances
Typical ±2–6 mm depending on the scanner and the project, with documented overlap quality and control geometry.
Documented control
A registration report your team can hand to the client. Not a black-box "trust us." If a target was excluded, you'll know why.
Ready for downstream
Delivered in the format your modeling team works in — RCP, RCS, E57, LAS, PTS, or whatever your downstream calls for.
- Cyclone
- RCP / RCS
- E57
- LAS / PTS
- ±2–6mm
If you're a survey firm that captures clean scans but is buried in registration, this is the deliverable to send first. Most of our long-term partners started here and added scan-to-BIM later.
Questions specific to registration.
What if our control network has gaps?
We'll flag it in the registration report rather than silently force-fitting the data. You decide whether to re-shoot control or accept a documented tolerance increase.
Which scanners do you support?
Leica, Riegl, Faro, and Trimble formats natively. If your hardware outputs something else, ask — most formats convert cleanly.
Can registration be a standalone deliverable?
Yes. Plenty of survey firms send us raw scans for registration only, then run their own modeling in-house. We price it as its own scope.