feat(integrations): M3 — geocoding (Nominatim) in the import slice #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/m3-geocoding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Roadmap M3 (geocoding part). First real vendor integration; places resolve to modern coordinates. Testable in the browser.
Changes
Geocodertrait +GeoQuery/GeoHit(query carries only a place string — FR-PRV-09); Nominatim adapter (reqwest/rustls, OSM, no key, descriptive UA);StaticGeocoderfake.TreeStore::replace(mem + pg) so geocoded/edited trees persist./tree/:id(stable URL);GET /tree/:idrenders from store;POST /tree/:id/geocoderesolves un-geocoded places (sequential, ~1.1s/req per Nominatim policy, cap 25), saves, re-renders with name/country/coords.Verify
Live-tested: places resolve to "Lyon, …, France (45.758, 4.832)". CI stays network-free (only the
StaticGeocoderunit test runs).just qagreen.Traces: FR-IMP-07, FR-INT-09, FR-PRV-09 · tech-spec 05.