Laramie Simulation: Fuel break across the path 4 — Treatment edges, held or breached
v0 · … · built 2 weeks 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 "Laramie Simulation: Fuel break across the path 4 (2026-10-25 16:00)".
Details
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Laramie Simulation: Fuel break across the path 4 — Treatment edges, held or breached
e3d8c94a-fe1d-45ad-a5ba-f91599afcf8f
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 "Laramie Simulation: Fuel break across the path 4 (2026-10-25 16:00)".
v0
2 weeks ago by Thomas Marsh the Darsh
2 weeks ago by Thomas Marsh the Darsh
Versions
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Schedules
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.
