Part 01

Stand register

Upload stand boundaries, or one estate boundary to be cut into cells.

Stand register

Forest stands

The register holds a stand per row: its reference, name, species, estate, area and, for an estate cut into cells, the cell it belongs to. Upload once and add to it at any time; a reference already on the register is updated rather than duplicated.

Two ways to load it, chosen under Upload:

Stand boundaries. A file of polygons, one per stand: GeoJSON, a zipped shapefile, KML or KMZ, in WGS 84. Each polygon's reference, name, species and claim reference are read from the columns your forestry system already uses (avdelning, kuvio, bestand, tradslag, treslag, puulaji, baumart, skadenummer, forsikringssak among them), so a file exported as it stands usually needs no relabelling.
One estate boundary. A single outline, cut into square cells of about five hectares each, named by row and column from the north-west corner. Give the estate a name before choosing the file. Uploading the same estate again replaces its cells.

Stand register: the Upload choice, the estate name field, and Choose a file.

The import result

Importing stand boundaries answers with how many stands were added and updated, and how many rows were refused with the reason for each, such as a boundary too small for the archive to read on its own. Cutting an estate answers with the estate's name and how many cells were made.

A stand too small to read on its own

A stand under about a third of a hectare is refused on import: at the pixel size of the open Sentinel archive, a stand that small cannot carry a reading of its own. Group it with an adjoining stand, or carry it on the estate boundary instead, where it becomes part of a cell.

Deleting a stand

Removing a stand removes its reads for every event. Re-upload it under the same reference to bring it back; its event history starts again.