v0 · … · built 5 hours ago
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 "Elk Creek FPD: Pine Junction December 19th 2025 with Treatment (2026-11-10 17:28)".
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: Pine Junction December 19th 2025 with Treatment — Debris flows (projected)
9113ab01-8d8c-4769-a225-13a1fff8b1e4
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 "Elk Creek FPD: Pine Junction December 19th 2025 with Treatment (2026-11-10 17:28)".
v0
4 hours ago by Thomas Marsh
4 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.