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 "Laramie Simulation: Fuel break across the path 5 (2026-10-25 16:47)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Laramie Simulation: Fuel break across the path 5 — Engine routes
35fe760b-ef70-4399-8374-3e0ce68d4c6c
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 "Laramie Simulation: Fuel break across the path 5 (2026-10-25 16:47)".
v0
2 weeks ago by Thomas Marsh the Darsh
2 weeks ago by Thomas Marsh the Darsh
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.