Organization
 
Log In
Fire Behavior

Files

Tables

Tiles

Files
190

What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:14)

Needs upload
Fire run for the simulation "Fire Simulation w/ Treatments 2", from Simulations.
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)

Built 7 days ago
Fire run for the simulation "Fire Simulation w/ Treatments 2", from Simulations.
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Assets reached

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Burning edge by time

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Fire pathways

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Perimeters by time

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Roads cut off

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Roads reached

Built 7 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 "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Spot landings

Built 7 days ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Fire Simulation w/ Treatments 2: Run 1 - Coal Creek (2026-10-26 13:32)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 1 - Coal Creek — Spotting

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

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)

Built 7 days ago
Fire run for the simulation "Fire Simulation w/ Treatments 2", from Simulations.
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Assets reached

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Burning edge by time

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Fire pathways

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Perimeters by time

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Roads cut off

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Roads reached

Built 7 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 "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Spot landings

Built 7 days ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Fire Simulation w/ Treatments 2: Run 2 - Coal Creek (2026-10-26 13:59)".
v0
7 days ago

Fire Simulation w/ Treatments 2: Run 2 - Coal Creek — Spotting

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

Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)

Built 2 weeks ago
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 1 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 1 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 1 — Fire pathways

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

Fire Simulation with Mitigation Treatments: Run 1 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 1 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 1 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 1 (2026-10-22 19:13)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)

Built 2 weeks ago
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 — Fire pathways

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

Fire Simulation with Mitigation Treatments: Run 2 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 2 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 2 (2026-10-22 19:27)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 3 (2026-10-22 21:45)

Built 2 weeks ago
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 3 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 3 (2026-10-22 21:45)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 3 — Burning edge by time

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

Fire Simulation with Mitigation Treatments: Run 3 — Fire pathways

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

Fire Simulation with Mitigation Treatments: Run 3 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 3 (2026-10-22 21:45)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 3 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 3 (2026-10-22 21:45)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 3 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 3 (2026-10-22 21:45)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:50)

Built 2 weeks ago
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:51)

Built 2 weeks ago
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:51)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:50)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Burning edge by time

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

Fire Simulation with Mitigation Treatments: Run 4 — Burning edge by time

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

Fire Simulation with Mitigation Treatments: Run 4 — Fire pathways

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

Fire Simulation with Mitigation Treatments: Run 4 — Fire pathways

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

Fire Simulation with Mitigation Treatments: Run 4 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:51)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:50)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:50)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:51)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:51)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 4 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 4 (2026-10-22 21:50)".
v0
2 weeks ago

Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:18)

Needs upload
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
last week

Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)

Built last week
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:33)

Needs upload
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)

Built last week
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Assets reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Burning edge by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Fire pathways

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Perimeters by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Roads reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Spot landings

Built last week
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge (2026-10-25 19:36)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 - Coyote Ridge — Spotting

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

Fire Simulation with Mitigation Treatments: Run 5 — Assets reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 — Burning edge by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 — Fire pathways

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 — Perimeters by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 — Roads cut off

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 5 — Roads reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 5 (2026-10-25 19:28)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 (2026-10-25 19:20)

Needs upload
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
last week

Fire Simulation with Mitigation Treatments: Run 6 (2026-10-25 19:28)

Needs upload
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)

Built last week
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Assets reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Burning edge by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Burning edge by time, without the timed ignitions

Built last week
The part of the edge still burning at each time step of the fire without the run's timed ignitions (worked out in DuckDB from its perimeters). Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Fire pathways

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Perimeters by time

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Perimeters by time, without the timed ignitions

Built last week
The fire as it would have gone without the run's timed ignitions: spread from the first one's time on the same ground with the run's own barriers, one polygon per time step, cumulative, at the run's own steps. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Roads reached

Built last week
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 "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Spot landings

Built last week
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge (2026-10-25 21:42)".
v0
last week

Fire Simulation with Mitigation Treatments: Run 6 - Coyote Ridge — Spotting

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

Fire Simulation with Mitigation Treatments: Run 7 - Coyote Ridge V.2 (2026-10-25 21:52)

Needs upload
Fire run for the simulation "Fire Simulation with Mitigation Treatments", from Simulations.
last week

Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI Additional Ignition Point (2026-10-22 18:02)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI With Speed — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI With Speed (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI (2026-10-22 17:56)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T New AOI.V2 — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T New AOI.V2 (2026-10-22 18:07)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Marshal Conditions - T.V2 — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Marshal Conditions - T.V2 (2026-10-22 18:03)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (copy) (2026-10-22 17:44)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)".
v0
2 weeks ago

Marshall Replication: Run 1 - 12 Tribes Ignition Location — Smoke (screening estimate)

Built 2 weeks ago
Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 1 - 12 Tribes Ignition Location (2026-10-22 17:27)".
v0
2 weeks ago

Marshall Replication: Run 12 (2026-10-22 18:25)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 12 - With treatments (2026-10-22 18:54)

Needs upload
Fire run for the simulation "Marshall Replication", from Simulations.
2 weeks ago

Marshall Replication: Run 12 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Spot landings

Built 2 weeks ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 12 (2026-10-22 18:25)".
v0
2 weeks ago

Marshall Replication: Run 12 — Spotting

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

Marshall Replication: Run 3 (2026-10-22 17:52)

Needs upload
Fire run for the simulation "Marshall Replication", from Simulations.
2 weeks ago

Marshall Replication: Run 3 (2026-10-22 17:53)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 3 (2026-10-22 17:55)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 3 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:55)".
v0
2 weeks ago

Marshall Replication: Run 3 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Burning edge by time

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

Marshall Replication: Run 3 — Burning edge by time

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

Marshall Replication: Run 3 — Debris flows (projected)

Built 2 weeks ago
Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Debris-flow basins (projected)

Built 2 weeks ago
The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Fire pathways

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

Marshall Replication: Run 3 — Fire pathways

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

Marshall Replication: Run 3 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:55)".
v0
2 weeks ago

Marshall Replication: Run 3 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:55)".
v0
2 weeks ago

Marshall Replication: Run 3 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:55)".
v0
2 weeks ago

Marshall Replication: Run 3 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:53)".
v0
2 weeks ago

Marshall Replication: Run 3 — Smoke (screening estimate)

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

Marshall Replication: Run 3 — Spot landings

Built 2 weeks ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 3 (2026-10-22 17:55)".
v0
2 weeks ago

Marshall Replication: Run 3 — Spotting

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

Marshall Replication: Run 4.V2 (2026-10-22 18:04)

Built 2 weeks ago
Fire run for the simulation "Marshall Replication", from Simulations.
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Assets reached

Built 2 weeks ago
Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Burning edge by time

Built 2 weeks ago
The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Fire pathways

Built 2 weeks ago
The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Perimeters by time

Built 2 weeks ago
The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Roads cut off

Built 2 weeks ago
Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Roads reached

Built 2 weeks ago
Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Spot landings

Built 2 weeks ago
Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Marshall Replication: Run 4.V2 (2026-10-22 18:04)".
v0
2 weeks ago

Marshall Replication: Run 4.V2 — Spotting

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

SuperiorBurnProbability97th.zip

v0
last year

SuperiorFireBehavior97th.zip

v0
last year

SuperiorFireSimulation.zip

v0
last year

TownofSuperior.zip

v0
last year
Bintel