**Chat log** from Bead: Georegister Image · [canonical source](https://redfish.acequia.io/guerin/.agents/58091f55-cb28-41b6-98a9-be56cdab5890/2026-06-17/chats/2026-06-17-georegister-image.md) · session 2026-06-17 · discussion: Talk: Georegister Image *Verbatim chat log: immutable provenance. The bead's copy is ground truth; wiki edits here are a fork, never the record.*
Verbatim user prompt; assistant turn summarized with pointers to durable notes.
**User:** > mount image-pose-uxui and add a note about using kml to initialize the georegistering of an image. > start-bead georegister-image for georesistering an image which will become an ortho-image, right? you can referene georegistering workflows in qgis, google earth and esri. linke that to image-pose-uxui as a lot of the ux ui will be shared. eg, we may not just use GCP but may use UV's from other images with camera poses as a constraint. I also think we can treat georegistration of an image as just a different camera type. an orthophoto camera (Context: followed the incident-viewer IRHS finding — IR/HS items carry a KMZ `GroundOverlay`/`LatLonBox` georeference.) **Assistant:** Mounted **pose-ux-ui** (`edb06426`) and added `2026-06-17/notes/01-kml-init-georegistration.md` (KML `LatLonBox`/`gx:LatLonQuad` = a free initial georegistration = the orthophoto-camera case; refine via the UV↔geopoint editor; soft prior). Opened THIS bead **georegister-image** (`58091f55-…`) with `notes/00-georegister-image.md`: the reframe (georegistration = solving an **orthophoto camera**; ortho-image needs a DEM for true orthorectification), the **constraint model** (GCPs + **cross-image UV tie-points** + KML prior, as a soft-constraint bundle), the **prior-art** (QGIS Georeferencer / Google Earth Image Overlay / ESRI Georeference, with what to take from each), and the **shared-UX map** with pose-ux-ui (UV↔geopoint editor + LM solver + geospatial-ux-ui grammar). Bound the related beads in `names.json`.