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 "Laramie Simulation: Active hours repro (QA test) (2026-10-29 17:13)".
Details
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Laramie Simulation: Active hours repro (QA test) — Fire pathways
8afaa231-6162-4046-ac53-e59e327bff87
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 "Laramie Simulation: Active hours repro (QA test) (2026-10-29 17:13)".
v0
last week by Thomas Marsh the Darsh
last week by Thomas Marsh the Darsh
Versions
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Schedules
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.
