yellowstone-burn-recovery
Two-epoch NBR over the 1988 Yellowstone fires, which burned about 3,200 km² of the park in one season. The baseline epoch is the pre-fire forest and the recent epoch is today's canopy, so the difference reads as RECOVERY rather than severity: the stand-replacing lodgepole burn has been regrowing for more than three decades.
- recipe
- Apache-2.0
- outputs
- CC-BY-4.0
The contract
Read from this recipe's own declarations — parameters:,
outputs:, requires:, and the ops its layers name. Not from its
style blocks and not from any benchmark: a colour ramp is not a contract, and a measured
run is evidence about one AOI rather than a domain.
Parameters
The legacy dialect has no typed parameter schema. Read the folia.yaml for what this recipe takes; nothing here can type-check it.
Outputs
| output | kind | layer | what it is |
|---|---|---|---|
deficit_recent |
answer | answer/deficit-recent |
Pixels whose canopy is still short of the pre-fire stand. THE answer. |
deficit_baseline |
answer | answer/deficit-baseline |
The same test applied to the baseline against itself — a near-zero self-check. |
nbr_change |
raster | compute/nbr-change |
dNBR raster, recent minus pre-fire (show-your-work). |
Capabilities it requires
The legacy dialect has no requires: block.
Where it runs
- Browser preview does not run here answer/deficit-baseline: layer type "answer" is not one folia-view parses; answer/deficit-recent: layer type "answer" is not one folia-view parses; compute/deficit-baseline: carries an unsubstituted ${...} template; and 7 more
- Local CLI (folia run) runs here runs locally through the legacy (no spec_version) parser
- Operated fleet (POST /plan, /run) runs here legacy dialect: a lock binds by the cut's layer names, not by digest
registry/recipes/yellowstone-burn-recovery/folia.yaml