Fire Simulations

Example Simulations: Ames (2026-11-09 18:17)

Built yesterday

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

v0

yesterday

Example Simulations: Ames (2026-11-09 18:26)

Built yesterday

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

v0

yesterday

Example Simulations: Ames Burn (2026-11-09 18:32)

Built yesterday

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

v0

yesterday

Example Simulations: Ames Burn — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Ames Burn — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Engine routes

Built yesterday

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 "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Evacuation zones

Built yesterday

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 "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Ames Burn — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames Burn — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Ames Burn (2026-11-09 18:32)".

v0

yesterday

Example Simulations: Ames — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: Ames — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Ames — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Ames — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: Ames — Engine routes

Built yesterday

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 "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Engine routes

Built yesterday

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 "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: Ames — Evacuation zones

Built yesterday

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 "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: Ames — Evacuation zones

Built yesterday

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 "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Ames — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Ames — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: Ames — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Roads cut off

Built yesterday

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

v0

yesterday

Example Simulations: Ames — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:26)".

v0

yesterday

Example Simulations: Ames — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Ames (2026-11-09 18:17)".

v0

yesterday

Example Simulations: CR 43Z S (2026-11-09 18:34)

Built yesterday

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

v0

yesterday

Example Simulations: CR 43Z S — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Engine routes

Built yesterday

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 "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Evacuation zones

Built yesterday

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 "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: CR 43Z S — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: CR 43Z S — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: CR 43Z S (2026-11-09 18:34)".

v0

yesterday

Example Simulations: Down Valley (2026-11-09 18:42)

Built yesterday

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

v0

yesterday

Example Simulations: Down Valley with Treatments (2026-11-09 19:05)

Built yesterday

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

v0

yesterday

Example Simulations: Down Valley with Treatments — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Burning homes by time

Built yesterday

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 "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Engine routes

Built yesterday

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 "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Evacuation zones

Built yesterday

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 "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Fire pathways

Built yesterday

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley with Treatments — Treatment edges, held or breached

Built yesterday

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 "Example Simulations: Down Valley with Treatments (2026-11-09 19:05)".

v0

yesterday

Example Simulations: Down Valley — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Down Valley — Burning homes by time

Built yesterday

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 "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Engine routes

Built yesterday

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 "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Evacuation zones

Built yesterday

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 "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Down Valley — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Down Valley — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Down Valley (2026-11-09 18:42)".

v0

yesterday

Example Simulations: Hidden Lake (2026-11-09 18:13)

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Engine routes

Built yesterday

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 "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Evacuation zones

Built yesterday

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 "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake with Treatment — Treatment edges, held or breached

Built yesterday

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 "Example Simulations: Hidden Lake with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Hidden Lake — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Engine routes

Built yesterday

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 "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Evacuation zones

Built yesterday

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 "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Hidden Lake — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Hidden Lake — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Hidden Lake (2026-11-09 18:13)".

v0

yesterday

Example Simulations: Mountain Village (2026-11-09 18:31)

Built yesterday

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

v0

yesterday

Example Simulations: Mountain Village with Treatment (2026-11-09 19:04)

Needs upload

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

yesterday

Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)

Built 23 hours ago

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

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Assets reached

Built 23 hours ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Burning edge by time

Built 23 hours ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Burning homes by time

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Damage per structure (estimate)

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Debris flows (projected)

Built 23 hours ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Debris-flow basins (projected)

Built 23 hours ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Engine routes

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Evacuation zones

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Fire pathways

Built 23 hours ago

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

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Perimeters by time

Built 23 hours ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Roads cut off

Built 23 hours ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Roads reached

Built 23 hours ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Smoke (screening estimate)

Built 23 hours ago

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

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Treatment edges, held or breached

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village with Treatment — Watersheds after the fire

Built 23 hours 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 "Example Simulations: Mountain Village with Treatment (2026-11-09 22:58)".

v0

23 hours ago

Example Simulations: Mountain Village — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Mountain Village — Burning homes by time

Built yesterday

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 "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Debris flows (projected)

Built yesterday

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Debris-flow basins (projected)

Built yesterday

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Engine routes

Built yesterday

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 "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Evacuation zones

Built yesterday

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 "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Mountain Village — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Mountain Village — Smoke (screening estimate)

Built yesterday

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

v0

yesterday

Example Simulations: Mountain Village — Watersheds after the fire

Built yesterday

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 "Example Simulations: Mountain Village (2026-11-09 18:31)".

v0

yesterday

Example Simulations: Spud Patch (2026-11-09 18:44)

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch (2026-11-09 19:07)

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch 3d (2026-11-09 19:20)

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch 3d — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Engine routes

Built yesterday

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 "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Evacuation zones

Built yesterday

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 "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Fire pathways

Built yesterday

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch 3d — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch 3d (2026-11-09 19:20)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Engine routes

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Evacuation zones

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Fire pathways

Built yesterday

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape with Treatment — Treatment edges, held or breached

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape with Treatment (2026-11-09 19:41)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Engine routes

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Evacuation zones

Built yesterday

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 "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Fire pathways

Built yesterday

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch Updated Landscape — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch Updated Landscape (2026-11-09 19:35)".

v0

yesterday

Example Simulations: Spud Patch — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 18:44)".

v0

yesterday

Example Simulations: Spud Patch — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Spud Patch — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch — Engine routes

Built yesterday

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 "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Spud Patch — Engine routes

Built yesterday

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 "Example Simulations: Spud Patch (2026-11-09 18:44)".

v0

yesterday

Example Simulations: Spud Patch — Evacuation zones

Built yesterday

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 "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Spud Patch — Evacuation zones

Built yesterday

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 "Example Simulations: Spud Patch (2026-11-09 18:44)".

v0

yesterday

Example Simulations: Spud Patch — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Spud Patch — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Spud Patch — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 18:44)".

v0

yesterday

Example Simulations: Spud Patch — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Spud Patch — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Spud Patch (2026-11-09 19:07)".

v0

yesterday

Example Simulations: Trout Lake (2026-11-09 18:14)

Built yesterday

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

v0

yesterday

Example Simulations: Trout Lake (2026-11-09 18:21)

Needs upload

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

yesterday

Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)

Built yesterday

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

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Burning edge by time

Built yesterday

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Engine routes

Built yesterday

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 "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Evacuation zones

Built yesterday

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 "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Fire pathways

Built yesterday

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake Hwy 145 — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake Hwy 145 (2026-11-09 18:15)".

v0

yesterday

Example Simulations: Trout Lake — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Trout Lake — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Engine routes

Built yesterday

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 "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Evacuation zones

Built yesterday

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 "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Trout Lake — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Trout Lake (2026-11-09 18:14)".

v0

yesterday

Example Simulations: Wrights Mesa (2026-11-09 18:45)

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Engine routes

Built yesterday

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 "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Evacuation zones

Built yesterday

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 "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa with Treatment — Treatment edges, held or breached

Built yesterday

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 "Example Simulations: Wrights Mesa with Treatment (2026-11-09 19:04)".

v0

yesterday

Example Simulations: Wrights Mesa — Assets reached

Built yesterday

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Burning edge by time

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa — Damage per structure (estimate)

Built yesterday

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 "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Engine routes

Built yesterday

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 "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Evacuation zones

Built yesterday

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 "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Fire pathways

Built yesterday

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

v0

yesterday

Example Simulations: Wrights Mesa — Perimeters by time

Built yesterday

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Roads cut off

Built yesterday

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Example Simulations: Wrights Mesa — Roads reached

Built yesterday

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulations: Wrights Mesa (2026-11-09 18:45)".

v0

yesterday

Fire Simulations

Files