v0 · … · built 5 hours ago
Each treatment's edge where the fire reached it: `status` held (the fire came within a cell and stopped) or breached (it burned across, on both sides of the edge), `treatment` its index in the run and `name`, `minutes` when the fire first came near. Worked out in DuckDB from the run's burned area. Written by each run of the fire simulation whose output file is "Elk Creek FPD: Conifer December 19th 2025 with Thinning (2026-11-10 16:56)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Elk Creek FPD: Conifer December 19th 2025 with Thinning — Treatment edges, held or breached
4c5b8cea-f8e8-4e14-8853-d82adfe68e82
Each treatment's edge where the fire reached it: `status` held (the fire came within a cell and stopped) or breached (it burned across, on both sides of the edge), `treatment` its index in the run and `name`, `minutes` when the fire first came near. Worked out in DuckDB from the run's burned area. Written by each run of the fire simulation whose output file is "Elk Creek FPD: Conifer December 19th 2025 with Thinning (2026-11-10 16:56)".
v0
5 hours ago by Thomas Marsh
5 hours ago by Thomas Marsh
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.