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)".
Details
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Example Simulations: Wrights Mesa — Engine routes
d7c9a2cc-bc0e-4151-a262-5d1c34a9b3a5
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 by Thomas Marsh
yesterday by Thomas Marsh
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.
