Reality capture is most useful when its scope follows a production decision. Start by writing one sentence: Our team needs to use the captured geometry to… That answer determines what must be measured, what must be modeled and who should review the result.
1. Identify the physical scope
Mark the projection surfaces and the surrounding context that matters. A facade-only assignment is different from one that also needs recesses, adjoining scenery, projector sightlines or reference features. Include exclusions so everyone understands what will remain outside the dataset.
Photos and drawings can help define this brief. They do not establish that the installed geometry matches the drawing. Record how and when existing documents were created, and identify changes since then.
2. Choose the capture milestone
Capture a component in fabrication when its shape needs review. Capture an installed environment when final spatial relationships matter. If surfaces will move, be repainted, receive cladding or change before opening, communicate those milestones before choosing the capture date.
A capture records conditions at a point in time. It cannot keep the model current after the environment changes. Assign someone to report those changes to the receiving teams.
3. Plan access and coverage
Laser scanning is a line-of-sight measurement method. Recesses, obstructions and hidden surfaces may require additional positions or access. Reflective, transparent and other challenging finishes should be identified rather than assumed to produce complete usable measurements.
For an operating attraction, define permitted work areas, access windows, public separation and site-specific safety requirements. Discuss whether equipment or scenery can be moved and who authorizes that access. Heritage and museum environments may require additional permissions.
4. Agree the spatial reference
The receiving teams need consistent units, origin and orientation. State whether the work needs a local production reference or a connection to survey/site control. Survey accuracy or certified control should not be inferred from the existence of a point cloud.
Document any transformations applied between measured data and production models. A silent change of scale or axis can make a correct measurement difficult to use.
5. Separate measurements from derived assets
A registered point cloud contains coordinated measured points. A mesh connects surface faces and may include interpolation or simplification. A production model can be further adapted for a media or fabrication workflow.
Agree which of these is required. For a derived model, discuss priority surfaces, polygon budget, smoothing, permitted exclusions and the ownership of UV mapping or content templates. Avoid using “3D model” as the entire specification.
6. Define review and acceptance
Name the team that receives the files, the person who checks them and the production decision they must support. Confirm required formats and software versions rather than presuming compatibility.
A representative test import can reveal coordinate, units or complexity issues before the final handoff. Review registration, coverage and important features using the project’s agreed criteria. Required tolerances and validation are scope items, not universal promises.
A brief you can use
- Environment and site location
- Production stage and target milestones
- Intended use and receiving team
- Marked projection surfaces, adjacent context and exclusions
- Access, operational and material constraints
- Units, coordinates and reference requirements
- Measured data versus derived model requirements
- Format, detail and test-import criteria
- Review owner and change-notification process
Capture is one part of the show
Spatial data can inform media and AV work. The projection system still needs optical design, appropriate projector setup, on-site calibration and commissioning. Assign those responsibilities alongside the capture rather than leaving them implicit.
Read point cloud versus mesh or the scan-to-show process. To discuss a project, use the inquiry form; a non-confidential summary is enough to begin.
Technical references
- Leica laser scanning workflow: capture, registration/review and export stages.
- Disguise OmniCal overview: calibration, point-cloud reconstruction and model adjustment in a projection workflow.