**Note** from Bead: Wildfire Imagery Acquisition & Catalog Ops · [canonical source](https://redfish.acequia.io/guerin/.agents/b3461c66-1a49-4f62-8920-d6dcc9838942/2026-06-08/notes/sorrento-incident-identity.md) · session 2026-06-08 · discussion: Talk: Wildfire Imagery Acquisition & Catalog Ops
> 2026-06-08. Stephen pointed out a **second** Sorrento incident folder, written by the EGP mission-browser: > `https://simtable.acequia.io/incidents/CA-SND-SORRENTO/` — distinct from the `2026-CA-Sorrento/` I built. > Same fire. This is the concrete instance of the catalog naming/identity problem > (mission-browser-as-catalog + sibling bead `c38c1239`).
## The EGP airborne surface (CA-SND-SORRENTO/) Flat per-incident, written by the mission-browser (vendor **AEVEXIMAGERY**, aircraft tail **N57B**): | File | What | |---|---| | `VIDEOCLIP_181752225.mp4` (64 MB) + `_klv.json` (1.6 MB) | FMV clip + KLV telemetry (the MISB surface) | | `VIDEOCLIP_181752225_perimeter.kml` | per-clip footprint | | `HSImage_180303888.{kmz,png}` | hyperspectral, georeferenced | | `IRImage_175658951.{kmz,png}`, `IRImage_175728995.{kmz,png}` | IR, georeferenced | | `PERIM_180330105_63acres.kml` | airborne-mapped fire perimeter, **63 acres** | | `mission.json` | manifest | `mission.json` shape: `{ mission:{id, name:"CA-SND-SORRENTO", vendor, tailNumbers, status, videoCount, imageCount, featureCount, coords, createdOn}, products:[{id, type:VIDEO|IMAGE|FEATURE, displayText, lat, lon, bbox, createdOn, signedPath, …}], archivedAt }`. Products' `signedPath` point at the EGP S3 archive (`xentity-fam-egp-airborne-archive.s3…`); the mission-browser localized the actual bytes here. Confirms the `<mission>/{mission.json + products}` structure documented in mission-browser-as-catalog.
## The collision | | `2026-CA-Sorrento/` (mine) | `CA-SND-SORRENTO/` (mission-browser) | |---|---|---| | naming | WatchDuty `geo_event` 101783 + my date-prefixed slug | EGP **mission name** (CA / SND=San Diego / SORRENTO) | | surfaces | AlertWest ground cams (353 frames) + WatchDuty perimeter/evac | EGP airborne: FMV+KLV, HS/IR, perimeter | | perimeter | **FIRIS, 90 acres** (18:25 UTC) | **AEVEX airborne, 63 acres** (~18:03 UTC) | | coords | 32.9101, −117.2136 | 32.9112, −117.2131 | **Same fire, two roots, two conventions** — and even two perimeters from two sources/times (FIRIS 90 ac vs airborne 63 ac). This is exactly `c38c1239`'s requirement #8 (grouping = incident → source → leaf) and the multi-source-same-attribute case, now real.
## Proposal (NOT acted on — Stephen's call + a `c38c1239` format decision) The incident is the natural **grouping node**; the three surfaces should hang off **one** incident identity: ``` incidents/<one-incident-id>/ ├── ops-alertcalifornia/ ← AlertWest ground cameras (mine) ├── egp-airborne/ ← mission-browser EGP/AEVEX (HS/IR, FMV+KLV, perimeter) [= current CA-SND-SORRENTO/] └── watch-duty/ ← WatchDuty perimeter/evac/geo_event ``` Options: - **(A) Consolidate** under one slug with per-source subtrees (above). Cleanest; matches the catalog's incident→source→leaf tree. Cost: MOVE the mission-browser tree + teach the bookmarklet the incident path. - **(B) Keep separate folders, join by manifest** — an `incident.json` that references all three roots by URL. No moves; the join lives in metadata. Fits "namespace composed, not reified" but leaves two roots. I did **not** move or rename anything — the mission-browser folder is Stephen's output, and which slug is canonical (plus whether the bookmarklet should target the incident path) is his decision, and it's coupled to the unified-catalog `Entry`/grouping design in `c38c1239`. Recommend (A) with a stable incident id, and **updating the bookmarklet to write `incidents/<id>/egp-airborne/`** instead of a top-level mission slug.
## For the catalog-format bead (`c38c1239`) This Sorrento case is a ready worked example for its design: one incident, three producer surfaces, two perimeters from different sensors — exercises grouping (#8), media-by-reference (#5), and the platform/look/subject + multi-source-attribute points. Worth docking as an example if Stephen wants.