Start here
The forestry storm record: upload your stands, name the event, and read every stand ranked by where to look first.
This guide is for an insurer's claims desk working a storm or beetle season, and for a forest owner association's forest manager who needs a dated record of an estate after one. Both read the same register: stands uploaded once, an event named against them, and a ranked list of where to look first.
What the record is
After a named storm, a snow load, a beetle season or a fire, the record reads the open Sentinel archive over every stand of an estate and ranks them by where a drone or a forester should go first. Each stand is read against its own history: the same weeks of the same months in the three years before the event, so the call is made against what that stand does in a quiet year, not against a fixed number. Reference sets out what that comparison means in plain words.
The record dates a change and ranks it. It does not name a cause, and it does not give a share of timber lost. A stand ranked first moved more than it does without the event, on the dates the record states; a storm, a beetle attack and a harvest can all do that, and the person who visits the stand establishes which.
If you are new
Read Stand register and upload a small file of your own stands, or one estate boundary. Then read Naming an event and reading it to see the record through from a named event to a ranked list.
Finding your way round
Forest stands sits in the portal sidebar once your workspace has this record switched on. The page holds your stand register, the events you have named, and for the event selected the ranked list, a map of the stands coloured by status, and the panel for one stand at a time.
The parts
Stand register
Stand boundaries, estate boundaries, and the import result.
PART 02Naming an event and reading it
The event, its windows, and reading every stand on the register.
PART 03The ranked list and the stand record
The ranked list, the stand map, confidence, and the pictures.
PART 04Estate records, claim references and downloads
Estate record, CSV export, claim reference, downloads and language.
PART 05Reference
The statuses in plain words, and the quiet range explained.
Conventions
- Controls are named as they appear on screen: Choose a file, Name the event, Read every stand.
- Values in
monospaceare what the product or the API itself prints: column names and status codes. - Labels in italics are statuses as the register shows them, such as above the estate's quiet range.
An insurer's claims team or the loss adjuster between them and the owner reads the ranked list as triage: which claims need a visit first. A forest owner association or management firm reads the same list and the stand and estate records as the dated account of the event, to carry to the insurer, the tax authority or the timber buyer.
Other lanes
The portal's EUDR workflow, for plots of tree crops under due diligence, has its own guide, and a workspace importing wood has a third: