**Note** from Bead: Pose Ux Ui · [canonical source](https://redfish.acequia.io/guerin/.agents/edb06426-e7b9-4df1-aca5-64b385ba0d02/2026-06-17/notes/01-kml-init-georegistration.md) · session 2026-06-17 · discussion: Talk: Pose Ux Ui
Added 2026-06-17 (Stephen). Hatched alongside the new bead **georegister-image** (`58091f55-cb28-41b6-98a9-be56cdab5890`), which carries the full georegistration design; this note records the KML-initialization hook for the pose-setting UX.
## The hook A KMZ/KML **ground overlay** already encodes an image's ground placement, so when an image arrives with a KML it gives a **free initial georegistration** (an initial pose) that the manual pose-setting UX then refines — no need to start from nothing. - `<GroundOverlay><LatLonBox>` → `north / south / east / west / rotation`: a **north-up (or rotated) axis-aligned ground rectangle**. This is exactly an **orthophoto-camera** placement (nadir, orthographic) on a flat ground plane. - `<GroundOverlay><gx:LatLonQuad>` → four corner lon/lats: a general **affine/projective ground quad** (the oblique/keystoned case). **Worked example (live):** the incident-viewer's `imagery-irhs` IR/HS items each ship a KMZ whose KML carries a `LatLonBox` (e.g. Sandy `IRImage_174841423`: N 34.289279 / S 34.182359 / E -118.713203 / W -118.798221, rotation 0) over a GCP-warped PNG — i.e. the producer already georegistered it; we just read the box. (See incident-viewer `be9c3efd` note 04 / `cbf8b027` Sandy STAC.)
## How it plugs into this bead's pose-setting UX - **Initialization, not ground truth.** The `LatLonBox`/`LatLonQuad` seeds the pose; the human then drags corners (2D map, santafe.live) and/or drops **UV↔geopoint constraints** (the campanile editor) to refine it. Treat the KML box as a **soft prior** (cf. feedback_every-constraint-is-soft), reweighted as real constraints land — not a lock. - **It is the orthophoto-camera case of the camera spectrum.** A KML ground overlay = the degenerate orthographic/nadir end of the same pose+intrinsics tuple the snapshot-view-as-pose (perspective) end produces. So the pose-setting UX should expose **"orthophoto / ground-overlay"** as one pose mode beside the perspective modes — and import/export KML for it. - **Shared UX with `georegister-image`.** The UV↔geopoint constraint editor, the solver, and the layer-tree/`geospatial-ux-ui` grammar are common; georegistration is the same interaction aimed at producing an **ortho-image** rather than an oblique-photo pose. See `58091f55…/2026-06-17/notes/00-georegister-image.md`.
## References (bead cross-links) - Bead: Georegister Image · [canonical](https://redfish.acequia.io/guerin/.agents/58091f55-cb28-41b6-98a9-be56cdab5890/)