Airports are hostile places for surveying. Half the space sits behind security, the other half is full of passengers, and the building never closes. When Corgan set out to document a roughly 1.6 billion dollar aviation program at LAX, the tool they chose was the Matterport Pro2, a 360 degree camera that captures a room as a set of overlapping panoramas. Five years later the archive still works. Here is the workflow that made that possible, at least the parts I would copy.
Why a 360 camera instead of a lidar rig
A terrestrial laser scanner is more accurate, and it is also slower, heavier, and awkward to move through a live terminal at two in the morning. The Pro2 shoots fast, fits in a bag, and produces a walkable model without a specialist on every trip. The tradeoff is precision. You are not getting millimeter accuracy on a curtain wall. You are getting a room you can recognize and measure well enough to confirm a door location. Battery life and cards matter more than specs. A night shift is six hours, and the camera has to survive all of it.
The scan plan comes before the camera
The usual failure is scanning everything and organizing nothing. Before a single capture, define the zones that matter: areas that change on the construction schedule, interfaces between new and existing work, equipment rooms that get sealed early. Give each zone a naming rule and a revisit cadence. A scan you cannot find later is not a record. It is a file.
Registration and drift
Every panorama has to be tied to its neighbors. Indoors, that means overlapping sightlines and enough feature texture for the software to solve the alignment. Long corridors are the hard case, because they look identical for a hundred feet. The fix is boring: more overlap, a few temporary targets, and a control measurement every so often. When a scan set drifts, the symptom is a wall that bends, and by then the cause is usually three rooms back. I keep a short written log per zone: what was captured, what was blocked, what needs a return trip. The log has saved more time than any software feature.
Coordinates that match the drawings
A scan lives in its own local space until you tie it to the project. Establish control points that exist in both the scan and the design model, transform once, and record the parameters. Keep the transform version with the dataset. The drawings change. The control network should not. If a scan lands two feet off, you want to check the transform, not re scan a concourse.
Volume, storage, and delivery
Five years of scans is a lot of data, and most of it does not need to be hot. I split storage into three tiers: raw captures, processed models, and the lightweight views people actually open in a browser. Only the third tier needs to be fast. The raw data needs to be findable, documented, and backed up, which is a different problem from performance. Name files by zone and date, never by camera serial or a person's initials. In five years nobody will know who those initials belong to.
The verification loop
The scan is only useful if someone compares it to the design on a schedule. Pick a small set of checkpoints, such as door locations, ceiling heights, and equipment clearances, then run them after each revisit. Record the result, not just the image. A photo is nice. A number is a decision. A pass or fail against a specific dimension is what turns a model into a construction record.
Massing before the heavy work
Not every question deserves a scan. When a proposed addition needed a quick read against the existing concourse, I drew a rectangle on a map and let GenAnywhere generate a 3D model of the area. It returned massing in minutes. That is enough to test height, bulk, and how the new piece sits against the old one, and it keeps the scan crew focused on geometry that will actually be built.
What I would automate
Registration reports, revisit reminders, and a dashboard that flags scans older than their zone cadence. None of that is glamorous. All of it is the difference between an archive and a pile of files. The camera gets the credit. The boring logistics keep the record alive.
Top comments (0)