IFTDSS Auto97

BerthoudBurnProbabilityAuto97.zip

v0

6 months ago

BerthoudLandscape-Auto97th.zip

v0

6 months ago

BerthoudLandscape.zip

v0

6 months ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)

Built 2 days ago

Fire run for the simulation "Cushman–Sedona–Rainbow Lake Fire", from Simulations.

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)

Built 2 days ago

Fire run for the simulation "Cushman–Sedona–Rainbow Lake Fire", from Simulations.

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Assets reached

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Burning edge by time

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Burning homes by time

Built 2 days ago

Homes lit house to house (not by the wildland fire itself), drawn as the fire's ground: each time band's homes with their yards, neighbors within about 30 m joined into one shape (grown and shrunk in DuckDB). One ring per band, `minutes` its end and `homes` how many it lit. Shown only: the run's acres stay the wildland's. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Fire pathways

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Perimeters by time

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Roads cut off

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 — Roads reached

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire 2 (2026-11-10 18:56)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Assets reached

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Burning edge by time

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Fire pathways

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Perimeters by time

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Roads cut off

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire — Roads reached

Built 2 days 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 "Cushman–Sedona–Rainbow Lake Fire: Cushman–Sedona–Rainbow Lake Fire (2026-11-10 18:50)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)

Built 2 days ago

Fire run for the simulation "Horseshoe Park–Willis Farms Fire", from Simulations.

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Assets reached

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Burning edge by time

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Fire pathways

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Perimeters by time

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Roads cut off

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Roads reached

Built 2 days 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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)

Built 2 days ago

Fire run for the simulation "May 19–20, 2020", from Simulations.

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Assets reached

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Burning edge by time

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Debris flows (projected)

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Debris-flow basins (projected)

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Perimeters by time

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Smoke (screening estimate)

Built 2 days 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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

May 19–20, 2020: Sprague May 20, 2020 — Watersheds after the fire

Built 2 days ago

Each debris-flow basin: the share burned and at moderate or high severity, and its highest debris-flow likelihood, hazard and volume over the design storms. Written by each run of the fire simulation whose output file is "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)

Built 2 days ago

Fire run for the simulation "Serenity Ridge Fire", from Simulations.

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Assets reached

Built 2 days 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 "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Burning edge by time

Built 2 days 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 "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Fire pathways

Built 2 days 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 "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Serenity Ridge Fire: Serenity Ridge Fire — Perimeters by time

Built 2 days 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 "Serenity Ridge Fire: Serenity Ridge Fire (2026-11-10 18:54)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)

Built 2 days ago

Fire run for the simulation "Wark–Sprague Fire", from Simulations.

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)

Built 2 days ago

Fire run for the simulation "Wark–Sprague Fire", from Simulations.

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Assets reached

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Burning edge by time

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Burning homes by time

Built 2 days ago

Homes lit house to house (not by the wildland fire itself), drawn as the fire's ground: each time band's homes with their yards, neighbors within about 30 m joined into one shape (grown and shrunk in DuckDB). One ring per band, `minutes` its end and `homes` how many it lit. Shown only: the run's acres stay the wildland's. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Fire pathways

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Perimeters by time

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Roads cut off

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire 2 — Roads reached

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire 2 (2026-11-10 18:57)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Assets reached

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Burning edge by time

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Damage per structure (estimate)

Built 2 days ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Engine routes

Built 2 days ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Evacuation zones

Built 2 days ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Fire pathways

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Perimeters by time

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Roads cut off

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

Wark–Sprague Fire: Wark–Sprague Fire — Roads reached

Built 2 days 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 "Wark–Sprague Fire: Wark–Sprague Fire (2026-11-10 18:45)".

v0

2 days ago

IFTDSS Auto97

Files