Fire Simulation

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments — Treatment edges, held or breached

Built 2 days 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 "Berthoud Community Fires, Apr 22, 2022: Foothills with Treatments (2026-11-10 23:52)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Foothills — 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 "Berthoud Community Fires, Apr 22, 2022: Foothills (2026-11-10 23:41)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Horseshoe Park–Willis Farms–Wilfred Fire, Apr 22, 2022 (2026-11-10 19:06)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Serenity Ridge Fire, Apr 22, 2022 (2026-11-10 19:07)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)

Built 2 days ago

Fire run for the simulation "Berthoud Community Fires, Apr 22, 2022", from Simulations.

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 — Treatment edges, held or breached

Built 2 days 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:37)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 — Treatment edges, held or breached

Built 2 days 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:55)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 — Treatment edges, held or breached

Built 2 days 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 2 (2026-11-10 23:50)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 — 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 "Berthoud Community Fires, Apr 22, 2022: Wark–Sprague Fire, Apr 22, 2022 (2026-11-10 19:03)".

v0

2 days ago

BerthoudFire.zip

v0

6 months ago

BerthoudFireStart.zip

v0

6 months ago

May 19–20, 2020: Burn It (2026-11-06 19:24)

Built 6 days ago

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

v0

6 days ago

May 19–20, 2020: Burn It More (2026-11-06 19:30)

Built 6 days ago

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

v0

6 days ago

May 19–20, 2020: Burn It More Structure (2026-11-06 19:37)

Built 6 days ago

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

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Assets reached

Built 6 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: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Burning edge by time

Built 6 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: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Burning homes by time

Built 6 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 "May 19–20, 2020: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Damage per structure (estimate)

Built 6 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 "May 19–20, 2020: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Engine routes

Built 6 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: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Evacuation zones

Built 6 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: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Fire pathways

Built 6 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 "May 19–20, 2020: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Perimeters by time

Built 6 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: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More Structure — Roads reached

Built 6 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 "May 19–20, 2020: Burn It More Structure (2026-11-06 19:37)".

v0

6 days ago

May 19–20, 2020: Burn It More — Assets reached

Built 6 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: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Burning edge by time

Built 6 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: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Damage per structure (estimate)

Built 6 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 "May 19–20, 2020: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Engine routes

Built 6 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: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Evacuation zones

Built 6 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: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Fire pathways

Built 6 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 "May 19–20, 2020: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Perimeters by time

Built 6 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: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It More — Roads reached

Built 6 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 "May 19–20, 2020: Burn It More (2026-11-06 19:30)".

v0

6 days ago

May 19–20, 2020: Burn It — Assets reached

Built 6 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: Burn It (2026-11-06 19:24)".

v0

6 days ago

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

Built 6 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: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Damage per structure (estimate)

Built 6 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 "May 19–20, 2020: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Engine routes

Built 6 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: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Evacuation zones

Built 6 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: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Fire pathways

Built 6 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 "May 19–20, 2020: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Perimeters by time

Built 6 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: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: Burn It — Roads reached

Built 6 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 "May 19–20, 2020: Burn It (2026-11-06 19:24)".

v0

6 days ago

May 19–20, 2020: May 19–20, 2020 (2026-11-06 19:16)

Built 6 days ago

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

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

May 19–20, 2020: May 19–20, 2020 — Burning homes by time

Built 6 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 "May 19–20, 2020: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

May 19–20, 2020: May 19–20, 2020 — Damage per structure (estimate)

Built 6 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 "May 19–20, 2020: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

May 19–20, 2020: May 19–20, 2020 — Landslide potential (experimental)

Built 6 days ago

Burned slopes by post-fire landslide potential: high on 30 degrees or more burned at moderate or high severity, moderate on 20 degrees or more. A screening index, not a geotechnical assessment. Written by each run of the fire simulation whose output file is "May 19–20, 2020: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

May 19–20, 2020: May 19–20, 2020 — Roads reached

Built 6 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 "May 19–20, 2020: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

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

Built 6 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: May 19–20, 2020 (2026-11-06 19:16)".

v0

6 days ago

New Simulation: New Simulation (2026-11-11 00:54)

Built 2 days ago

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

v0

2 days ago

New Simulation: New Simulation 2 (2026-11-11 00:55)

Needs upload

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

2 days ago

New Simulation: New Simulation 2 (2026-11-11 00:59)

Built 2 days ago

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

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation 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 "New Simulation: New Simulation 2 (2026-11-11 00:59)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

New Simulation: New Simulation — 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 "New Simulation: New Simulation (2026-11-11 00:54)".

v0

2 days ago

Fire Simulation

Files