Reality Capture: Drones, Laser Scanning & Using the Data

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, Reality Capture: Drones, Laser Scanning & Using the Data. Don't let the plain title fool you. Here's the part that actually matters on the job: Reality capture earns its cost only when the capture is planned around a specific decision, tied to survey control, and compared against the model or the drawings while there is still time to act. Learn it well and you'll find the slab that is out, the sleeve that is missing, and the stockpile that is short before they cost you.

The intro course covered what drones, photogrammetry, and laser scanning are. This lesson is how to plan a capture, do it legally and accurately, and turn the files into decisions.

Plan the capture around a decision

Start with the question, not the equipment. Progress percentage for a pay application, earthwork quantities, existing conditions for design, verification of installed work before close-in, or a dated record for a dispute each need a different method, accuracy, and cadence.

• Drone photogrammetry suits large outdoor areas and progress. With ground control, horizontal accuracy within a few centimeters is commonly achievable; vertical accuracy is worse.
• Terrestrial laser scanning suits interiors, structure, and anything that will be compared to a model, with accuracy in the millimeters.
• Mobile or handheld scanners trade some accuracy for speed and are good for weekly progress and context.
• 360-degree photo walks are the cheapest record and often enough for progress and documentation; spend the scan budget where measurement matters.

Set the cadence in the quality plan: weekly flights for progress, scans at milestones such as underground MEP before the slab, structure before the deck pour, and overhead rough-in before ceilings close.

Flying under FAA Part 107

In the United States, commercial drone operations on a jobsite generally fall under FAA Part 107. Verify the current rules before every program, because they change, but the stable parts include a remote pilot certificate with recurrent training, aircraft registration, keeping the aircraft within visual line of sight, staying at or below 400 feet above ground level unless within 400 feet of a structure, authorization before flying in controlled airspace near airports, yielding to manned aircraft, and restrictions on flying over people who are not part of the operation. Remote identification requirements also apply to most registered aircraft. Beyond the regulation, a company drone program needs a preflight checklist, a crew briefing, coordination with crane operations so the aircraft never shares airspace with a load, and respect for neighbors and the owner's rules on photography.

Flight planning and ground control

Use an automated flight plan at a fixed altitude with roughly 70 to 80 percent front and side overlap, which is the common rule of thumb for photogrammetry. Lower altitude gives finer ground resolution and more photos. For measurable results, place ground control points that the surveyor measures in project coordinates, well distributed across the site, or use survey-grade positioning on the aircraft, and in either case hold back independent check points to report the accuracy. Fly the same plan each week so progress datasets compare cleanly. Outputs are an orthomosaic, a surface model, a point cloud, a mesh, and volumes computed between surfaces.

Laser scanning workflow

Plan scan positions so every surface that matters is seen from at least two positions, with overlap between positions. Register the scans to each other using targets or cloud-to-cloud matching, then georeference the result to project control so it overlays the model. Read the registration report; an error you cannot explain means a bad scan position, not a rounding problem. Clean the cloud of people, equipment, and noise, export it at a density the BIM tools can handle, and name it by date, area, and capture type.

Putting the data to work

• Model versus as-built deviation — a color map of installed structure against the model shows columns out of plumb and decks high or low. The decision is either fix the work or update the model and warn the downstream trades.
• Floor flatness and levelness — a scan heat map finds the problem areas early; the specified test method is usually ASTM E1155 and a scan report does not replace it unless the specification says so.
• Progress and quantities — successive captures show what was installed; surfaces give cut, fill, and stockpile volumes for pay applications.
• Existing conditions — a scan-to-BIM model of an existing building, with the modeling tolerance stated in the BEP.
• The permanent record — the pre-close-in scan is the as-built of everything inside that wall and ceiling.

Data management

Point clouds and photo sets are enormous. Decide up front where they live, who can view them (web viewers beat sending raw files), how they are named, how long they are kept, and who owns them under the contract. A capture nobody can find in six months was never worth taking.

Going Deeper (Intermediate)

Separate resolution from accuracy and relative from absolute. A scan can be internally tight and still be in the wrong place if it was never tied to control. Every report should state its accuracy relative to project control and how it was checked. Write the capture points into the quality control plan and the subcontracts so the pre-close-in scan is an expected step and rework found then is the sub's to fix before the finishes go on.

Advanced / Pro-Level

Pros automate the comparison: scheduled flights, automatic alignment to the model, element-by-element progress recognition, and deviation reports delivered to the coordination meeting. They scan existing buildings so prefabrication can be built to real conditions on renovations, and they treat each milestone scan as a gate in the schedule. They also understand the limit: reality capture supports but does not replace a licensed surveyor where law or contract requires one.

Practice Challenge

A scan of the Level 3 steel before the deck pour shows the east column line 22 mm west of the model at the top. The mechanical sub has prefabricated duct racks for the east corridor. What do you do? (Answer: do not just file it — flag it to the structural side to confirm whether 22 mm is within erection tolerance, update the coordination model to the as-built position, and have the mechanical detailer check the racks against the real steel before they ship; a fit problem found now is a hanger relocation, found later it is a fabricated rack that does not fit.)

In Practice

A team that scans before each pour and each close-in, on control, and sends the deviation report the same day fixes problems for the cost of a phone call. A team that flies the drone for the marketing video and never ties it to control has beautiful pictures and no idea the slab is an inch low.

Common Mistakes to Avoid

• Capturing without a question, so the data is never compared to anything
• Skipping ground control and check points, then trusting the numbers
• Flying without the Part 107 basics or near crane operations
• Accepting a registration report with unexplained error
• Storing clouds nobody can find or open six months later

Takeaway: Reality capture earns its cost only when the capture is planned around a specific decision, tied to survey control, and compared against the model or the drawings while there is still time to act.

Educational content only — not design, engineering, surveying, or legal advice, and not a substitute for training, your company's procedures, or review by a licensed design professional or surveyor. Software and hardware are described as generic categories and no product is endorsed. Follow the applicable codes and regulations as adopted in your jurisdiction, your contract, and the manufacturer's instructions for every instrument and device.