Gaussian splatting is a way to reconstruct a scene as a cloud of anisotropic “splats” rather than a mesh or a classic point cloud. From a well-captured set of photographs, it can produce a view that looks closer to standing on site than many photogrammetric meshes do — especially on vegetation, thin structures, and messy interiors.
It is not a replacement for every other deliverable. It is a new one, and it belongs in the same project conversation as orthos, clouds, and meshes.
What a splat actually is
Under the hood, the scene is represented by millions of 3D Gaussians: position, covariance, opacity, and view-dependent color. Renderers project those primitives into the camera. The result is a radiance-field-like view that holds together as you move, without requiring a watertight mesh.
That is why splats can look convincing at a glance. It is also why they are a poor place to hide a quantity takeoff. You are looking at a learned appearance of the site, not a classified LAS file.
Where it helps professional work
Splats are useful when the client needs to recognize the place:
- Marketing and stakeholder walkthroughs of a site
- Construction progress that has to be understood by people who will never open a point cloud
- Heritage and interiors where mesh holes and texture swimming are distracting
- Any job where “does this look like the site?” is the first question
They are a weak fit when the first question is “what is the volume of that pile?” or “what is the clearance on that pipe?” Keep the measurable cloud or mesh for that work.
Capture notes that actually matter
Gaussian splat quality is still a photography problem:
- Coverage and overlap beat heroic camera settings
- Motion blur and rolling shutter still show up
- Thin objects and mirrors remain difficult
- Scale and georeferencing are not automatic just because the viewer looks 3D
If the rest of the job is controlled in a CRS, do not treat the splat as a second, unnamed world. Either it is aligned to the same site, or it is a visual sidecar. Say which.
Formats and delivery
Export names vary by tool — PLY, compressed splat containers, and engine-specific packages all appear. The operational issue is the same as with LAS: the client does not have your viewer.
A splat that can only be opened after installing a desktop build is an internal asset. A splat that opens in the same project as the ortho and the report is a deliverable.
Treat it that way. Put it in the project, label the capture date, and keep the survey-grade products beside it instead of pretending one format does every job.