Facility Expansion

2026-10-14

Spoil pile vs. berm: telling them apart in satellite imagery

A grassy embankment crest with a post-and-rail fence along the top, under a cloudy sky.

A spoil pile and a berm can sit forty meters apart on the same frame and read almost the same at first glance: a raised, roughly linear mass of disturbed earth, lighter than the surrounding ground, casting a shadow that tells you more than the color does. Analysts get this wrong often enough that it's worth writing down the actual tells, because the two mean very different things on a treaty-relevant site. One is debris waiting to be hauled or regraded. The other is a structure someone built on purpose and intends to keep.

Shape and placement give it away first

Berms are engineered. That shows up in the geometry before anything else does. A berm runs as a continuous linear feature with a fairly uniform cross-section along its length, usually following a perimeter, a drainage line, or the edge of a pad. Corners are deliberate, not accidental, and the top width tends to hold steady for the run of the feature. If you can trace a consistent ridge line for fifty or a hundred meters with the same apparent height throughout, you're looking at something designed.

Spoil is the opposite. It piles where the excavator or the haul truck dumped it, which means irregular footprints, conical or mounded cross-sections, and a strong spatial correlation with an open cut or trench nearby. Spoil doesn't follow a line that makes engineering sense; it follows where it was convenient to put dirt. If the mound sits immediately adjacent to a pit and tapers unevenly instead of running straight, that's spoil, not berm.

What the imagery actually shows

At 0.5 m GSD, shadow geometry resolves cleanly enough to estimate height and slope angle, which covers most of the work of telling the two apart. A berm's shadow is consistent in width along its run because the cross-section doesn't change. Spoil throws an irregular shadow that widens and narrows as the pile height varies from one end to the other.

Texture helps too. Freshly placed spoil tends to look rougher and more heterogeneous in RGB, with visible clod structure and uneven tonal variation from moisture and compaction differences. A compacted, engineered berm reads more uniformly, often with a smoother, drier surface because it's been graded and sometimes seeded or capped. If the site has any history in the archive, compare tone against earlier passes of known berms on the same facility. Soil type and lighting angle will vary your reference, so don't rely on a single week's read.

Watching how the pile behaves over weeks

This is where cadence matters more than any single image. A spoil pile is transient by nature: it appears abruptly in one pass, grows or shrinks over the following weeks as material gets added or hauled away, and often disappears entirely once the excavation phase ends. A berm appears once, holds its footprint and height within normal tolerance, and stays. If a mound has been sitting unchanged in three consecutive weekly passes with no adjacent excavation activity, it's almost certainly a berm, or something close enough to one that calling it spoil would be wrong in a report.

Volume trend is the cleanest discriminator, when you can get it. Spoil volume tracks excavation volume with a lag of a week or two; dig more, spoil grows, haul it off, spoil shrinks. Berm volume is flat once construction finishes. If you're logging this by hand across archive tiles every week, that lag is exactly the kind of thing that gets missed between manual comparisons.

Why the distinction matters for compliance tracking

Calling a berm "spoil" in a report buries a hardening signal under routine construction noise. Calling spoil a "berm" can flag transient dirt movement as a permanent defensive feature and waste review time chasing it. Getting this right on a named site you're watching long-term means tracking footprint, volume, and persistence together, not reading a single frame in isolation.

That's closer to a running site map with change annotations than a manual archive pull every week, which is the shape of thing Facility Expansion was built to produce. If you're watching one site and don't want to make this call from scratch every Monday, it's worth a look.

Get started

← Back to the blog