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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".
Details
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
May 19–20, 2020: Sprague May 20, 2020 — Engine routes
52546b15-7a25-4b38-91f6-5af4c8b2c504
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 "May 19–20, 2020: Sprague May 20, 2020 (2026-11-10 18:29)".
v0
2 days ago by Thomas Marsh
2 days ago 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.
Schedules
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.
