What This Looks Like in Practice
Aerial mapping is not a photo. It is a coordinated dataset.
Most clients who ask for a "drone survey" are actually asking for one of four things: an orthomosaic they can drop into their site plan, a digital surface model their civil engineer can pull contours from, a volumetric report that closes the gap between estimated and actual stockpile or earthwork, or an NDVI map their agronomist can use to direct fertilizer or irrigation. The flight is the same shape — overlapping nadir grid, RTK-corrected positions, photogrammetric reconstruction — but the deliverables and the accuracy thresholds diverge sharply.
Willamette Valley conditions add a planning layer most national mapping services either ignore or charge extra to handle. Wet ground delays GCP placement. Marine-layer ceilings sit at 250–500 m AGL for two hours after sunrise on most spring mornings, which means a 100 m AGL survey altitude is fine but a 300 m AGL high-altitude run is grounded until the layer breaks up. KEUG Class D airspace requires LAANC for anything overhead the central Eugene shelf — typically same-day, occasionally next-day for off-hours requests. None of this is dramatic; it is just the honest planning surface for a Eugene-based mapping operation.
The detailed write-up of how this actually shakes out — what the deliverables look like, where ground control points are necessary versus optional, and how Oregon terrain shapes flight planning — lives on the blog. The two posts below are the canonical references for new clients who want to see the process in plain language before scoping a job.
The Differentiator
RTK on, GCPs when needed, and Willamette Valley conditions baked into the plan.
The honest version of an aerial mapping job in 2026 is that a current-generation RTK-capable drone with a clean satellite view delivers 2–5 cm absolute accuracy at the camera, which is sufficient for most engineering, agricultural, and progress-monitoring deliverables. We default to RTK-on, no GCPs, because that gets the data out the door faster, cheaper, and accurate enough for what most projects actually need. We add GCPs only when the deliverable is going into a survey-grade product, when satellite reception is degraded by tree canopy or terrain, or when an independent QC layer is required. The supporting blog post on aerial mapping in the Pacific Northwest covers the RTK-versus-GCP tradeoff in detail — recommended reading before scoping any job.
Standard mission profile: 60–80 m AGL · 80% forward overlap, 70% side overlap · nadir grid · RTK on · 2–4 cm GSD · per-mission battery budget tuned to the parcel · LAANC pre-cleared if KEUG Class D applies
For the Willamette Valley specifically, the planning layer that separates a smooth job from a rebooked one is weather windowing. October through February it is a 2-out-of-3-day delivery medium. We bid that in as flex up front rather than learning it during the job. Atmospheric haze, low cloud ceilings, and saturated soils are the variables that move a flight day; sustained wind almost never grounds an M30T or Mavic 3 Pro inside their published envelopes.
Coverage
Where we fly.
Eugene · Springfield · Junction City · Cottage Grove · Coburg · Veneta · Creswell · Corvallis · Albany · Salem · McMinnville · Lane County · Linn County · Benton County · Marion County · Polk County · Yamhill County · Willamette Valley · Oregon Coast · Cascade foothills
KEUG Class D LAANC turnaround is routine — same-day for planned flights, occasionally next-day for off-hours requests. Outside controlled airspace, most of the Willamette Valley and surrounding terrain is unrestricted Class G and flights can be scheduled as needed. Coordination with civil engineers, surveyors, agricultural operators, and county planning departments is part of the standard workflow rather than an extra step.
Reading Material
Two field guides written from the operator's seat.
Mapping is one of the few drone services where the marketing language is reliably worse than the operational reality. The two posts below are the long-form versions of what we tell clients during a scoping call, written so a civil engineer or agricultural operator can read them and immediately know whether a mapping engagement is going to produce what they actually need.
What aerial mapping produces (it is not a photo). The Oregon terrain problem and how flight planning addresses it. Ground control points: when to use them and when you don't need to. What post-processing actually takes. Who actually uses aerial mapping in the Willamette Valley.
What agricultural drone mapping actually measures. The equipment stack that makes the data reliable. Where the process breaks down. What a single mapping season looks like on a working farm. Includes specific numbers — flight altitude, overlap, image counts — that match the standard mission profile.
Cut/fill and stockpile reporting on its own page, for clients who only need the volumetrics deliverable rather than a full survey. Same RTK photogrammetric workflow, different scope and deliverable focus.