Axine Axine Forestry storm record guide API Open the portal

Part 02

Naming an event and reading it

A storm, a beetle season, a snow load or a fire, with the dates that set the windows every stand is read on.

Naming an event

Forest stands

An event is what you are reading the estate against: a storm, a bark beetle season, a snow load, a fire, or another kind. Give it a name, a kind, and a date. A beetle season or anything spanning weeks also takes an end date, under To, for a season.

Naming an event: the name, kind, and dates, before Name the event.

The windows the record will use

Naming the event answers with the windows it will read, before anything is read. An event that falls in the growing season is read on the weeks either side of it. A winter storm is read on the same growing-season weeks in the year before and the year after, so the two looks are taken at the same time of year and under the same sun, rather than comparing a winter look with a summer one. The radar half of the read always covers the month either side of the event itself, whatever the season, so a winter storm still has a reading within weeks.

Check these windows before reading the estate. If a date was mistyped, the windows will show it.

Reading every stand

Forest stands

Read every stand reads the event over the whole estate in one pass. The event's status moves from new through reading to done, and the page refreshes itself while it runs. An estate of a few hundred stands in one area is usually done within minutes. Read again repeats the read once it has finished, which is the route to take if a stand was added after the first read.

One read at a time

An event reads in one job. If you add stands partway through, finish the read, then press Read again to bring the new stands in.

The Lisaris client portal is built by Axine Labs.

Contains modified Copernicus Sentinel data.