Bark Beetle Detection

What is a scored layer in forest health monitoring?

Pine-covered ridgelines receding into hazy mountains under a cloudy sky.

A scored layer is a map product where every polygon, usually a stand or a compartment, carries a number instead of just a color. The number tells you where that stand sits on a known scale, most often the progression from green-attack through red-attack to grey-attack. It's a step up from a straight classification map because it lets you sort, filter, and rank stands the same way you'd sort a spreadsheet.

Most agencies are used to two kinds of infestation data: aerial detection survey (ADS) sketch-maps flown once or twice a season, and ground reports that come in whenever a district forester or contractor happens to walk a stand. Both are useful, but neither gives you a number you can compare across a whole monitoring area on a fixed schedule. A scored layer does that by assigning a value to the same stand boundaries every time it's generated, so September's score and October's score are measuring the same thing the same way.

How the spectral infestation score gets built

The score comes from multispectral imagery read against known reflectance patterns for each infestation stage. Healthy conifer canopy, fading red-attack foliage, and bare grey-attack stems each throw back a distinct spectral signature. The scoring process reads that signature pixel by pixel within a stand boundary and rolls it up into a single value for the polygon, weighted by how much of the stand shows which stage.

That's different from a simple "infested or not" flag. A stand that's 15% red-attack scores differently than one that's 60% red-attack, even though both would get the same red dot on an old-style sketch-map. The score carries that proportion forward, which is the detail a salvage planner actually needs.

Reading a stand-level score

A stand-level score isn't a severity rating in isolation. Read it as a position on the red-to-grey progression, with the score moving as foliage condition changes month to month. A stand climbing steadily toward the grey end of the scale over two or three monthly reads is a different priority than one that spiked once and held flat. The trend across months tells you more than any single number does.

Practically, this means pulling the scored layer into your GIS alongside cruise data, access routes, and mill proximity, then sorting stands by score to build a salvage queue. Stands near the top of the grey-attack range with road access and standing merchantable volume get looked at first. Stands still early in red-attack but trending up go on a watch list for next month's read rather than this week's cutting plan.

A scored layer still needs ground verification before cutting. The score tells you which stands are worth sending a cruiser into this month, narrowing a monitoring area down to the places worth a field visit rather than serving as a stand-alone harvest authorization.

Cadence matters as much as the score itself

A single scored layer is a snapshot. The value comes from having one every month, generated the same way, against the same stand boundaries, so you can watch a compartment move through the color progression instead of guessing from a flight window that might land six weeks late. Agencies that have relied on ADS alone know the gap between a June flight and an August fire season decision. A monthly cadence closes most of that gap without replacing the field crew's judgment call on any given stand.

Bark Beetle Detection builds exactly this kind of register, a monthly scored layer over your forest health monitoring area, tracking that red-to-grey progression stand by stand so your salvage list updates on a schedule instead of waiting on the next aerial survey window.

If prioritizing salvage units by infestation stage is the problem on your desk this fall, that's worth a closer look.

Start a project

Back to the blog