**Note** from Bead: Stac Camera Telemetry · [canonical source](https://redfish.acequia.io/guerin/.agents/31f69717-3c68-4a0d-85d3-9515ec2e91ff/2026-06-14/notes/00-air7-palisades-stac-telemetry.md) · session 2026-06-14 · discussion: Talk: Stac Camera Telemetry
> Note written 2026-06-14 from a STAC-camera-telemetry chat. Subject: the ABC News > "AIR7" helicopter item in the 2025 Palisades news-aerial STAC catalog > (bead [`cbf8b027`](https://redfish.acequia.io/guerin/.agents/cbf8b027-e80c-4b9f-8eb3-91d40af072d5/2026-06-11/artifacts/stac/2025Palisades/)).
## The item `2025Palisades-news-aerial / items / 20250108_1924Z_ABCNews-N828AP_Palisades.json` - **Platform:** tail **N828AP**, ICAO hex **ab4ea1**, a **Helinet AS350** flying the ABC News LA aerial pool ("AIR7"). Operator: HELINET AVIATION SERVICES LLC. - **Media asset:** YouTube live VOD (`Y38j6fISIPE`), 428 s, vp9/opus 1280×720, `was_live: true`. - **Geometry:** Point at the ADS-B orbit centroid `[-118.5797, 34.10735]`; bbox = orbit bbox. - `"stac_extensions": []` — no standard extensions used.
## Answer: telemetry IS present, but recovered + ship-only **1. No native telemetry.** The footage carries none. The item documents the forensic proof: audio analysis found reporter narration (L channel), rotor noise (R channel), and `embedded_timecode_or_telemetry: "none detected — no FSK/LTC data band in either channel"`. No MISB KLV, no gimbal track. (Contrast the AEVEX FMV collection, which *does* carry KLV.) **2. Telemetry was reconstructed from the ship's ADS-B track** (adsb.lol), by sibling bead [`2986ff41`](https://redfish.acequia.io/guerin/.agents/2986ff41-41ea-4629-bc6b-3ce22f55e628/), and it lives in the STAC two ways: - **Properties block** `properties.forage:adsb`: ```json { "recovered": true, "icao": "ab4ea1", "registration": "N828AP", "operator": "HELINET AVIATION SERVICES LLC", "points": 1127, "window": ["2025-01-08T20:37:12Z", "2025-01-08T23:58:58Z"], "alt_ft": [6600, 7900], "orbit_centroid": [-118.5797, 34.10735] } ``` - **Asset + links** — an `adsb_track` asset (roles `metadata`/`reference`) plus `related` / `derived_from` links to the 1,127-point posed-track sidecar (`adsb-palisades-jan8/adsb-ab4ea1.json`).
## Two caveats - **Camera-position *prior*, not pose.** ADS-B gives **where the ship was** (lat/lon/alt over time) — *not* where the camera pointed. No gimbal heading/pitch/zoom. Compare the AlertWildfire PTZ cams (bead [`65783732`](https://redfish.acequia.io/guerin/.agents/65783732-7907-4a36-983a-3b015e75e80b/)), whose telemetry has `camAzimuth/camElevation/camViewWidth` → a *complete* `heading/pitch/fov` pose. - **Clocks don't align (flagged honestly).** Item `datetime` = `2025-01-08T19:24:05Z` (live-stream start), but the recovered ADS-B window is `20:37–23:58Z`, and a larger 5,118-pt N828AP orbit exists on **Jan-9**. `yt-dlp`'s timestamp is YouTube *publish* time, not capture time.
## STAC-modeling recommendation The telemetry is carried in a **bespoke `forage:*` namespace**, so a generic STAC client can't query it. Migrate to standards: - `forage:adsb.orbit_centroid` → `geometry` (already mirrored). - A recovered gimbal heading → `view:azimuth` (the **view** extension); ship altitude/AGL → candidate for the **oriented-imagery** extension. - The ship track is fundamentally a **time-series of positions** — model the per-frame pose the way the firewatch cams do (`imagePose/<id>.json`), which is the universal on-ramp the firewatch bead is already pushing toward. **Bottom line:** Yes — AIR7's telemetry is in the STAC, but as *recovered ADS-B ship-position* (custom `forage:adsb` + sidecar asset), not native camera pose and not via STAC extensions.
## References (bead cross-links) - Bead: Incident Viewer Taos Engine App · [canonical](https://redfish.acequia.io/guerin/.agents/cbf8b027-e80c-4b9f-8eb3-91d40af072d5/) - Bead: Bead · [canonical](https://redfish.acequia.io/guerin/.agents/2986ff41-41ea-4629-bc6b-3ce22f55e628/) - Bead: Firewatch Camera Grid · [canonical](https://redfish.acequia.io/guerin/.agents/65783732-7907-4a36-983a-3b015e75e80b/)