Reports
PDF reports rendered from the same real, cached analysis that backs the map and the API. No report is generated from simulated data — when a component is unavailable, the report says so.
Generate a report
Simple Report
type=simpleFor citizens, property owners and general users. Plain-language risk level, current conditions, the main drivers and the recommended action.
Decision-Support Report
type=decisionFor municipalities, companies, landowners and emergency planners. Adds the fire-danger map, exposure context, protection options and historical lessons.
Scientific / Technical Report
type=scientificFor researchers, technical institutions and government agencies. The full methods, daily series, provenance table and evidence annex.
Every report carries its metadata
The first page of each report states its identity and evidence standing, so a report can always be checked against the data it claims to describe:
| Report ID | A stable content hash of the underlying analysis payload — the same bytes produce the same ID, so a report and its evidence can be verified to match. |
|---|---|
| Generated | The analysis timestamp (real data-acquisition time). |
| Report engine | Report-engine version and risk-model version, with the report type. |
| Data sources | The sources that actually contributed, from the analysis provenance block. |
| Evidence status | Which components are observed, derived, modelled or unavailable. |
| Validation status | Whether the screening score is a validated predictor — currently stated honestly on every report (screening indicator until the validation pipeline passes on real historical data). |