Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT with Treatment (2026-10-21 17:02)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Example Simulation: Run 1 MTT with Treatment — Debris flows (projected)
ea80e65b-d3de-4dd5-a7d4-6c1f33b9e19f
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT with Treatment (2026-10-21 17:02)".
v0
2 weeks ago by Thomas Marsh
2 weeks 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.