Aerial Mapping in the Pacific Northwest: What the Data Actually Looks Like After the Drone Lands

A 40-acre parcel in the southern Willamette Valley. Twelve distinct elevation zones across a single timber lot. One flight, one operator, one DJI Matrice 30T — and about 2,400 overlapping images that, when processed correctly, become a survey-grade orthomosaic accurate to within a few centimeters.

That's what aerial mapping actually produces. Not a pretty photo. Not a flyover video. A measurable, queryable, spatially accurate dataset that engineers, landowners, contractors, and surveyors can load into GIS software and do real work with.

I want to talk about that gap — between what people think aerial mapping is, and what it actually delivers when it's done right.

---

What Aerial Mapping Produces (It's Not a Photo)

The word "mapping" gets used loosely. Sometimes people mean they want a bird's-eye photo of a job site. That's not mapping — that's an aerial still. Useful, but different.

True aerial mapping produces deliverables with spatial data attached:

**Orthomosaics** are geometrically corrected, stitched aerial images where every pixel has a real-world coordinate. Unlike a regular aerial photo — which has perspective distortion and no coordinate system — an orthomosaic lets you measure distances, areas, and positions directly on the image. A contractor can drop one into AutoCAD or QGIS and take accurate measurements without ever touching a tape measure on site.

**Digital Elevation Models (DEMs)** are raster datasets where each cell represents a ground elevation value. From a single flight, you get a complete topographic picture of the survey area. This is what you use for drainage analysis, grading plans, flood modeling, cut-and-fill calculations.

**Point Clouds** are three-dimensional datasets — millions of XYZ points that together represent the surface of the terrain and anything on it. Processed from photogrammetry, a point cloud lets you take cross-sections, build 3D models, calculate volumes with genuine accuracy.

**Volume Reports** come from point clouds and DEMs. Stockpile volumes. Cut-and-fill estimates. Material loss calculations between surveys. The kind of numbers a civil engineer or site manager needs — not estimates, actual measurements.

All of that comes from one calibrated flight with overlapping imagery and, where precision demands it, ground control points.

Why Overlap Percentage Matters More Than Most Clients Realize

Aerial mapping quality is largely determined before the drone ever leaves the ground — in the mission planning phase. The key variable is image overlap: the percentage of each photo that duplicates what the previous photo captured.

For standard mapping, 75% frontal overlap and 60% side overlap is a common starting point. For high-accuracy work — survey-grade deliverables, complex terrain, tall structures — I run 80/70 or higher. That increases flight time and raw image count, but it's what feeds the photogrammetry software enough redundant data to produce accurate results.

On a recent commercial lot inspection in the Eugene area, I ran a grid pattern at 85/75 overlap to generate a point cloud dense enough for an accurate volumetric calculation on a gravel stockpile. The client needed to know, within a few percent, how much material was on site. That level of overlap is why the number was reliable.

---

The Oregon Terrain Problem (And How Flight Planning Addresses It)

Most aerial mapping tutorials assume flat terrain. Eugene and the surrounding region does not cooperate with that assumption.

To the west: Coast Range foothills with steep draws, dense canopy, and rapid elevation changes. To the east: Cascade foothills with similar rugged character. The valley floor is relatively flat, but the moment you move into timber ground, agricultural hill ground, or any of the properties along the river corridors, you're dealing with terrain that actively works against a flat-altitude mapping mission.

The problem is this: if the drone flies a fixed altitude above the launch point, and the terrain rises 200 feet across the survey area, your ground sample distance (GSD — the real-world size of each image pixel) is going to vary significantly from one end of the survey to the other. You might plan for 2 cm/pixel resolution and end up with 4 cm/pixel in the elevated corners. For a visual deliverable, that's tolerable. For a measurement deliverable, it degrades accuracy.

Terrain-Following Flight Paths

The fix is terrain-following — planning the flight path so the drone maintains a consistent altitude above ground level (AGL) across the entire survey area, not a fixed altitude above the launch point. This requires a terrain elevation dataset fed into the mission planning software before the flight, so the drone adjusts its altitude dynamically as the terrain rises and falls.

The DJI Matrice 30T handles this well with proper pre-mission planning. On a hillside timber parcel I surveyed earlier this year north of Eugene, the elevation change across the survey area was close to 180 feet. A fixed-altitude pass would have produced inconsistent GSD throughout. Terrain-following produced uniform resolution edge-to-edge.

This is the kind of planning detail that separates a useful map from an impressive-looking flight.

---

Ground Control Points: When to Use Them and When You Don't Need To

Ground control points (GCPs) are physical markers placed on the ground at surveyed positions — known latitude, longitude, and elevation — that get photographed during the mapping flight and used as reference anchors in post-processing. They're how you push a mapping deliverable into true survey accuracy.

The honest answer about when you need them: it depends on what accuracy is required.

**Consumer and commercial drone RTK GPS** (Real-Time Kinematic) has improved the baseline accuracy of drone mapping without GCPs significantly. On the DJI M30T with RTK positioning, absolute horizontal accuracy approaches 1-3 cm on a clear sky, good satellite geometry flight. For many commercial applications — site documentation, general progress monitoring, infrastructure inspection mapping — that's more than adequate without a single GCP on the ground.

**Where GCPs still matter:** When you need to hit survey-grade vertical accuracy for engineering deliverables. When the site has tree canopy or obstructions that degrade GPS signal quality. When the deliverable needs to tie into an existing coordinate system or match previously surveyed benchmarks. When a licensed surveyor needs to stamp the output.

I'm not a licensed surveyor. BarnardHQ's mapping deliverables are measurement tools, not legal surveys. That distinction matters and I say it plainly to every client who asks. What I produce is accurate, useful, and often more current than any existing survey on a property — but if a licensed boundary survey is what you need, that's a different engagement. What drone mapping does is give engineers, contractors, and landowners a highly detailed, spatially accurate foundation to work from between survey milestones.

The Practical Use Case

A commercial contractor managing a grading project doesn't need a licensed survey every two weeks to track progress. They need to know if the grading is on track, how much material has moved, where they're running ahead or behind the plan. A drone mapping flight every two weeks — or even once a month — delivers that. They can compare this week's orthomosaic and DEM against last month's and get a clear picture of site progress without mobilizing a survey crew.

That's real value. That's what the data is for.

---

What Post-Processing Actually Takes

The flight is the fastest part of the job.

A 40-acre mapping mission at appropriate overlap might take 45 minutes to an hour in the air. The post-processing — photogrammetry computation, alignment, dense cloud generation, DEM extraction, orthomosaic stitching, quality report review — takes significantly longer. Depending on image count, area size, required deliverable resolution, and computing hardware, a mapping project can take anywhere from two to six hours of processing time before I have a final deliverable ready to deliver.

DroneOps Command, my self-hosted flight logging and operations platform, ties into this workflow. Every flight is logged with GPS coordinates, flight parameters, weather conditions, and mission notes — so when a client needs a follow-up survey six months later, I have the original mission data to reference and replicate. Consistent methodology matters for comparison surveys.

The deliverable package I provide typically includes: the georeferenced orthomosaic (GeoTIFF), the DSM/DEM (GeoTIFF), a processing quality report, and where applicable, volume calculations or annotated callout exports. The client gets files they can open in standard GIS or CAD tools — not a locked web viewer that disappears if someone stops paying a subscription.

---

Who Actually Uses Aerial Mapping in the Willamette Valley

The clients who get the most value from regular mapping engagements tend to fall into consistent categories locally:

**Civil contractors and earthwork operators** who need ongoing site documentation for owner reporting, volume tracking, and plan conformance checks.

**Agricultural operations** across the valley floor — vineyard row mapping, field boundary documentation, irrigation infrastructure surveys.

**Timber and land management** in the Coast Range foothills and Cascades — parcel documentation, road condition surveys, harvest area mapping.

**Commercial real estate and development** — site feasibility analysis, existing conditions documentation before design work begins, progress documentation through construction.

**Public agencies and utilities** — infrastructure corridor surveys, stormwater feature documentation, facility condition baselines.

None of these clients need a pretty aerial photo. They need accurate, actionable spatial data delivered in formats they can actually use.

---

Where to Start If You're Considering a Mapping Engagement

Before reaching out to any drone operator for mapping work, have answers to three questions: What deliverable format does your downstream software or workflow require? What accuracy level does the project actually need? And what's the timeline — is this a one-time documentation flight or a recurring survey over multiple phases?

Those three answers determine the flight plan, the GCP strategy, the processing pipeline, and the turnaround time. They also tell me whether what you need is straightforward or whether it warrants a pre-flight site visit to assess terrain complexity and access.

If you're in the Willamette Valley or the broader Lane County area and working through a project that might benefit from aerial mapping data, BarnardHQ is based in Eugene and available for consultation. The starting point is a conversation about what you're building, not a sales pitch about what I fly.

Plan it right. Fly it clean. Deliver something useful.