Drone Stockpile Volume Measurement in Oregon

One quarry, six stockpiles, a 48-hour bid deadline.

A quarry manager in Junction City called late last fall with a problem most aggregate operators recognize. He had six stockpiles — gravel, crushed basalt, mixed fill — and a contract bid due in 48 hours. His survey crew was booked out two weeks. A manned aircraft survey company quoted $1,800 with a three-day turnaround. A SaaS drone mapping platform wanted him to upload his flight data to their cloud and pay per-acre processing fees before he could download his own deliverables. None of that fit the deadline or the budget.

I flew the site with the DJI Matrice 30T, processed the point cloud locally on hardware I control, and had cubic-yard volume reports on his desk the same afternoon. He won the bid. The full methodology is documented in the volumetric measurement post — what photogrammetry actually does, where the numbers come from, what degrades them, and why local processing matters when your imagery contains operational detail you would rather not park on someone else's infrastructure.

Where stockpile volumetrics fit.

Where the numbers come from.

Volumetric accuracy is not magic. It comes from discipline in three places: image quality, ground control, and consistency in flight planning. Everything else is software.

Flight Planning

For stockpile sites in the Willamette Valley I typically fly double-grid missions at 60–80 meters AGL depending on stockpile height, with 80% frontal overlap and 70% side overlap. The Mavic 3 Pro's Hasselblad sensor and the M30T's wide camera both produce ground sampling distance around 2.4 cm/pixel at those altitudes — fine enough to resolve individual aggregate pieces. Endurance covers most single-site jobs on one battery with margin; multi-pile yards stage batteries at a central point and run sequential flights as one project for consistent coordinate registration.

Ground Control

Consumer-grade drone GPS is accurate to roughly 1–3 m horizontal and 5–10 cm vertical. That is not good enough for volume calculations where base plane elevation is critical. With ground control points placed on a calibrated RTK rover and tied to a survey benchmark, horizontal accuracy drops to 2–5 cm and vertical to 3–8 cm. With the M30T's RTK module anchored to a base station for full RTK during flight, the numbers tighten further. The mission brief defines which tier the application requires — internal monthly inventory tracking does not need RTK; a pre-acquisition audit usually does.

The Base Plane Problem

This is where most methodology errors happen, even from operators using good equipment. The base plane is the reference surface from which volume is calculated; if your base plane is off by ten centimeters, every cubic-yard number in your report is off by a consistent offset and you may not catch it until you reconcile against a weigh ticket. For active stockpiles on compacted grade, the base plane can be defined by sampling perimeter ground points where material meets undisturbed grade. For piles on sloped terrain or reclaimed footprints with irregular sub-grade, a flat base plane will overstate or understate volume. The honest fix is a pre-stockpile DTM on file as a baseline, or a wider flight that extracts a bare-earth surface model from the surrounding area.

For recurring clients I keep pre-stockpile DTMs on file. When they call for a volume check, I compare the current surface model against the baseline. It is fast, it is accurate, and it removes the ambiguity of manually defining base-plane points on an irregular perimeter.

What we use.

Processing runs locally on hardware under our control — WebODM, DJI Terra, or Pix4D depending on deliverable spec. Raw imagery never leaves our infrastructure. For audit-grade work see also drone mapping & survey; volumetric flights inherit the same RTK-grounded base.

Where we operate.

Barnard HQ is based in Eugene, Oregon and serves Lane County and the Willamette Valley as primary territory: Eugene, Springfield, Junction City, Cottage Grove, Creswell, Veneta, Coburg, Harrisburg. Up the I-5 corridor we cover Corvallis, Albany, Salem, and Lebanon for routine work. We travel further for project work — the Oregon Coast for forestry log-deck volumes, Central Oregon and the Cascade foothills for mining and reclamation, Southern Oregon for aggregate yards on the Rogue. KEUG Class D airspace is home — we fly LAANC-compliant out of it daily and know the operating envelope cold.

Site reconnaissance happens before mission day. We pull airspace, terrain, and prevailing-wind data, identify the GCP placement strategy, and confirm any operational constraints (active equipment, blasting schedules at quarries, animal welfare at ag sites) so the flight day is tight and predictable.

Local processing — your data stays your data.

Every major cloud-based drone mapping platform processes imagery on their servers. Upload gigabytes of raw image data, it lives on their infrastructure, you pay per-acre to download results. For a large site those fees add up to hundreds of dollars per mission. Your imagery — which may contain sensitive facility layouts, operational details, or proprietary site information — sits on someone else's server.

We process locally. Point cloud reconstruction, orthomosaic generation, and volume calculation run on hardware we control. The raw images never leave our infrastructure. The deliverables are produced and audited on machines we own. For clients in industries where facility security matters, that is not a minor point. The same philosophy runs through EyesOn (self-hosted live drone streaming) and DroneOps Command (open-source ops platform): the data stays where you put it, on infrastructure you own, with no third party holding the deliverable behind a subscription wall.

Field reports.

The methodology and a real Junction City quarry mission are documented in detail:

• Drone Volumetric Measurement: How to Calculate Stockpile Volume Without Paying Per-Acre Fees — the full methodology piece. What photogrammetry actually does, where the numbers come from, what degrades them, and how local processing changes the cost structure.
• Aerial Mapping in the Pacific Northwest: What the Data Actually Looks Like — companion piece on PNW-specific mapping conditions, base-plane strategy on sloped Willamette Valley terrain, and what point cloud density looks like under typical regional weather.
• Agricultural Mapping with a Drone: What the Numbers Actually Tell You — overlap with ag-specific volumetric work (silage, grain, compost) and what an inventory-grade deliverable looks like for ag lenders.

FAQ