OUR FRAMEWORK

How We Turn a Question

Into Useful Aerial Data

​

Every aerial project begins with a question: what needs to be understood, documented, measured, compared, or preserved? That question should determine everything that follows.

​

THE FLYING LIZARD uses a simple operating framework built around purpose, aviation discipline, intentional data collection, and honest interpretation. We do not begin by choosing a drone product. We begin by understanding the assignment.

​

Before a mission is planned, we want to understand why the information is needed and how it will be used. A construction baseline is different from an airport documentation project. A one-time orthomosaic is different from a repeatable dataset intended for comparison over time. A detailed 3D model requires different acquisition decisions than a straightforward aerial record. The question comes first because the answer determines the mission.

​

Once the objective is understood, the mission can be designed around it. Flight altitude, coverage, overlap, camera angle, ground control, airspace, site geometry, terrain, obstructions, lighting, and the required deliverables all influence how the data should be collected. The aircraft does not decide the mission. The intended use of the data does.

​

Aviation shapes how we operate. Preparation, situational awareness, airspace, aircraft condition, weather, surrounding traffic, site hazards, and changing conditions are part of every mission.

The aircraft may be unmanned, but the responsibility is not. The goal is not simply to complete the flight. The goal is to return with the information the mission was designed to collect.

​

Processing follows the same logic. Photogrammetry software can generate many products, but that does not mean every product belongs in every project. Orthomosaics, point clouds, surface models, three-dimensional models, source imagery, and other outputs should be selected because they match the purpose of the mission and the way the information needs to be used. We do not create complexity for its own sake. The deliverable is the answer to the question that drove the mission.

​

Accuracy should be evaluated rather than assumed. Where the project requires it, ground control, checkpoints, Real-Time Kinematic positioning, coordinate reference systems, and processing metrics can be used to strengthen and evaluate the dataset. Just as important is knowing where the limits are. A beautiful model can still contain weak geometry. A high-resolution image can still lack positional accuracy. A measurement is only as reliable as the data supporting it.

​

We would rather state those limits clearly than imply confidence the dataset has not earned.

​

Aerial data is also valuable because it can preserve more than an isolated view. It can preserve location, relationships, surrounding conditions, and the larger site at a specific moment in time. That context becomes especially important when conditions change. Construction advances. Landscapes evolve. Infrastructure is modified. Damage is repaired. Temporary conditions disappear. Once that happens, the opportunity to capture the earlier condition is gone.

​

The final product should be understandable, appropriate for the project, and useful to the people who need it. Sometimes that means a single orthomosaic. Sometimes it means a three-dimensional model. Sometimes it means a repeatable series of datasets. Sometimes it means preserving a condition before anyone knows exactly how important that record may become.

​

The format changes.

The principle does not.

​

Understand the question. Design the mission. Collect deliberately. Process appropriately. Verify what the data supports. Deliver something useful.

​

That is our framework.