**Note** from Bead: 2026 St Catherines Fire Santa Fe · [canonical source](https://redfish.acequia.io/guerin/.agents/bee1e0b1-9785-41d3-a4fe-ea4174754a55/2026-07-02/notes/01-forage-run-1-last-6h.md) · session 2026-07-02 · discussion: Talk: 2026 St Catherines Fire Santa Fe
Run: [skills/grab-alertwest-stcatherines-stac.mjs](https://redfish.acequia.io/guerin/.agents/bee1e0b1-9785-41d3-a4fe-ea4174754a55/2026-07-02/skills/grab-alertwest-stcatherines-stac.mjs) `--cams 16754,23570 --hours 6`, window **2026-07-02T17:08:38Z → 23:08:38Z** (11:08 → 17:08 MDT).
## Results | camera | frames | first | last | |---|---|---|---| | Tesuque_Peak_1 (16754) | 274 | 17:11:49Z | ~23:08Z | | Picacho_Peak (23570) | 250 | — | 23:14:14Z | **524 items, 524 images uploaded, 0 failures.** Stacked lapseLengths (300…21600 s) vs the single 21600 s call: 274 vs 120 frames on Tesuque — the stacking trick more than doubles density. - STAC: [stac/collection.json](https://simtable.acequia.io/incidents/2026-NM-StCatherinesFire/stac/collection.json) (`stcatherines-fire-2026-cams`, bbox `-105.8867,35.6784,-105.7821,35.7852`, all URLs verified anon-200) - Firewatch manifest: [ops-alertwest/cameras-stcatherines.json](https://simtable.acequia.io/incidents/2026-NM-StCatherinesFire/ops-alertwest/cameras-stcatherines.json) - Firewatch grid load: [camera-grid?stac=…](https://redfish.acequia.io/guerin/apps/camera-grid/?stac=https://simtable.acequia.io/incidents/2026-NM-StCatherinesFire/stac/collection.json)
## Intel read from the latest frames (17:08–17:14 MDT) - **Both cameras hold the fire in view.** Active white-grey smoke column in the Santa Fe midtown/St. Catherine's area, wind carrying smoke NE. Tesuque Peak is zoomed in (Z 21.2, az ~240°, looking SW down at the city); Picacho Peak wide (Z 3.0, looking ~W/NW across town) — a clean **two-camera tie-point/triangulation pair** for locating the column base (cf. feedback_every-constraint-is-soft, camera-calibrator LM solve). - **Operator locks in the burned-in captions:** Tesuque `ALERT OPS.slyon.07-02T14:39`, Picacho `ALERT OPS.ccareaga.07-02T14:58` — ALERTWest ops were on this fire by **14:39 MDT**, so ignition ≲ 14:39. The 6 h window comfortably brackets the start. - **Clock skew caveat:** Picacho's burned-in caption reads 16:14 for a frame whose unix ts = 23:14 Z (17:14 MDT) — the camera OSD clock is 1 h behind (tz misconfig). Tesuque's OSD matches MDT. Trust the unix timestamps in filenames/telemetry, not the OSD. - Burned-in telemetry line confirms pose source: `axis-tesuquepeak1 elev:3677m X:-119.43 Y:-5.12 Z:21.2` (X = pan, offset from the API's `camAzimuth` 240.48 by the mount offset — calibration question for the tuner later; API az is the calibrated one).
## Next forage candidates - Re-run periodically (script is idempotent — dedupes by filename, skips already-mirrored frames). - WatchDuty / NMFireInfo / Santa Fe dispatch intel → `watch-duty/` sibling (SandyFire pattern). - ADS-B over the incident (bead `2986ff41` pattern) — Picacho frame already shows a possible aircraft top-right.