Documents and Data Notes
What each file contains, how it is named, and which version to use.
Further Detail of SMFM Mapping Tools Below:
Every file shared through this page is tied to a tool and a monitoring period. The notes below describe the formats and the naming pattern so that files can be matched without guessing.

Forest ridge in early morning. The tile it came from is listed in the metadata sheet with its capture window.
File formats
Most outputs are raster or tabular. Each format is listed below with its typical use.
- GeoTIFF: classified degradation maps, one file per tile
- CSV: change totals by class and year
- GeoJSON: boundary polygons for review
- PDF: signed field check summaries

A path through the forest used as the cover image for the field summary. The route marks the transect walked during validation.
Naming and versions
File names follow a fixed pattern: tool code, tile identifier, rule version, and date of production. Keep the pattern when renaming.
Only the newest rule version should be used for reporting. Older files are kept for audit and are marked in the folder index.

Conifer stand in the reference set. Needle-leaf canopies respond differently to the index, so their files carry a separate note.
Handling notes
On receipt
Check the checksum
Compare the file hash with the value in the metadata sheet before opening it.
Before use
Confirm the version
Match the rule version in the file name to the version named in the tool header.
Questions about a specific file can be sent through the contact details, or checked against the resources page first.

Leaf canopy under strong light. Images like this are kept for the visual check, not for measurement.