v0 · … · built 3 weeks ago
An analysis run's assets that could burn, one point per asset: `risk` high / moderate, `bp` burn probability (class lower bound), `flame` flame length in feet (class lower bound), `crown` 1 surface / 2 torching / 3 active crown, `value` and `expectedLoss` (value times the burn probability class middle). Scored in DuckDB against the run's band tables. Written by each run of the fire simulation whose output file is "Laramie Simulation: Big fire · burn probability & fire behavior (2026-10-20 02:38)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Laramie Simulation: Big fire · burn probability & fire behavior — Assets at risk
7711083a-8b12-4094-8ec4-b4b16b69d77c
An analysis run's assets that could burn, one point per asset: `risk` high / moderate, `bp` burn probability (class lower bound), `flame` flame length in feet (class lower bound), `crown` 1 surface / 2 torching / 3 active crown, `value` and `expectedLoss` (value times the burn probability class middle). Scored in DuckDB against the run's band tables. Written by each run of the fire simulation whose output file is "Laramie Simulation: Big fire · burn probability & fire behavior (2026-10-20 02:38)".
v0
3 weeks ago by Thomas Marsh the Darsh
3 weeks ago by Thomas Marsh the Darsh
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.