Fire Simulation

50604__WeatherHourly__10-07-2021__01-08-2022.fw21

v0

2 weeks ago

52003__WeatherHourly__09-29-2021__01-02-2022.fw21

v0

2 weeks ago

52003__WeatherHourly__12-26-2020__01-01-2021.fw21

v0

2 weeks ago

55522201__WeatherHourly__04-09-2026__04-15-2026.fw21

v0

2 weeks ago

Arvada Simulation Sample: Run 2 (2026-10-21 16:48)

Built 2 weeks ago

Fire run for the simulation "Arvada Simulation Sample", from Simulations.

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)

Built 2 weeks ago

Fire run for the simulation "Arvada Simulation Sample", from Simulations.

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Debris flows (projected)

Built 2 weeks 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 "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 Copy - with structure value — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 Copy - with structure value (2026-10-21 17:02)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Debris flows (projected)

Built 2 weeks 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 "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 2 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 2 (2026-10-21 16:48)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 (2026-10-21 17:15)

Built 2 weeks ago

Fire run for the simulation "Arvada Simulation Sample", from Simulations.

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Debris flows (projected)

Built 2 weeks 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 "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Arvada Simulation Sample: Run 3 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Arvada Simulation Sample: Run 3 (2026-10-21 17:15)".

v0

2 weeks ago

Example Simulation: Farsite Run (2026-10-21 16:41)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Farsite Run (copy) (2026-10-21 17:00)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (copy) (2026-10-21 17:00)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run Marshall with Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run Marshall with Treatment (2026-10-21 17:04)".

v0

2 weeks ago

Example Simulation: Farsite Run — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Farsite Run — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Example Simulation: Farsite Run (2026-10-21 16:41)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (2026-10-21 16:34)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Spot landings

Built 2 weeks ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT (copy) — Spotting

Built 2 weeks ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (copy) (2026-10-21 18:58)".

v0

2 weeks ago

Example Simulation: Run 1 MTT with Treatment (2026-10-21 17:02)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Run 1 MTT with Treatment — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. 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

Example Simulation: Run 1 MTT with Treatment — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. 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

Example Simulation: Run 1 MTT with Treatment — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Run 1 MTT with Treatment (2026-10-21 17:02)".

v0

2 weeks ago

Example Simulation: Run 1 MTT with Treatment — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. 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

Example Simulation: Run 1 MTT with Treatment — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. 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

Example Simulation: Run 1 MTT with Treatment — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. 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

Example Simulation: Run 1 MTT with Treatment — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. 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

Example Simulation: Run 1 MTT with Treatment — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. 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

Example Simulation: Run 1 MTT with Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. 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

Example Simulation: Run 1 MTT with Treatment — Spot landings

Built 2 weeks ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. 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

Example Simulation: Run 1 MTT with Treatment — Spotting

Built 2 weeks ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. 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

Example Simulation: Run 1 MTT — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Debris flows (projected)

Built 2 weeks 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 "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Spot landings

Built 2 weeks ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 1 MTT — Spotting

Built 2 weeks ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Example Simulation: Run 1 MTT (2026-10-21 16:34)".

v0

2 weeks ago

Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs (2026-10-22 15:31)

Built 2 weeks ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 weeks ago

Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs (2026-10-22 15:31)".

v0

2 weeks ago

Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs (2026-10-22 15:31)".

v0

2 weeks ago

Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs (2026-10-22 15:31)".

v0

2 weeks ago

Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Run 7 - Farsite Marshall Sugarloaf RAWs (2026-10-22 15:31)".

v0

2 weeks ago

farsight_ignition.gpkg

v0

2 years ago

marshall_2021-12-30.wxs

v0

2 weeks ago

marshall_52003__WeatherHourly__12-26-2021__12-31-2021.fw21

v0

2 weeks ago

Sample Simulation 1: Run 1 (2026-10-21 16:44)

Built 2 weeks ago

Fire run for the simulation "Sample Simulation 1", from Simulations.

v0

2 weeks ago

Sample Simulation 1: Run 1 — Assets reached

Built 2 weeks ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Burning edge by time

Built 2 weeks ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Debris flows (projected)

Built 2 weeks 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 "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Fire pathways

Built 2 weeks ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Perimeters by time

Built 2 weeks ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Roads cut off

Built 2 weeks ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Roads reached

Built 2 weeks ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Spot landings

Built 2 weeks ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Sample Simulation 1: Run 1 — Spotting

Built 2 weeks ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Sample Simulation 1: Run 1 (2026-10-21 16:44)".

v0

2 weeks ago

Fire Simulation

Files