v0 · … · built 2 days 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 — Treatment edges, held or breached
9fa4e3ff-c44f-4e9c-b9ac-d677e5d05360
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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".
v0
2 days ago by Thomas Marsh
2 days 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.