Nominatim was upgraded from **v4.5 → v5.3.2** on recon-vm (VM 1130). This was a full fresh re-import; no in-place upgrade path exists between 4.x and 5.x due to data model changes.
**Western-11 coverage:** arizona, california, colorado, idaho, montana, nevada, new-mexico, oregon, utah, washington, wyoming. Outside these states the service returns only country-level ("United States") fallback — this was also the case for v4.5; coverage did not change.
The prior v4.5 container, its ~26 GB DB, and the `mediagis/nominatim:4.5` image were removed after cutover validation. `/mnt/nav` has ~70 GB free post-cleanup.
The v4.5 deployment was also western-11 only — this was not always clearly documented. The v5 upgrade was a like-for-like data freshness + engine refresh, not a coverage expansion.
**Photon was left at v1.1.0 (port 2322) and was not touched.** Photon is independent: it runs from a komoot dump, not built from the Nominatim DB. No version coupling applied for this data refresh. The prior doc note about mandatory Photon 1.2.0 co-upgrade was based on an assumption that Photon reads Nominatim's internal tables directly — that does not apply here.
1.**recon-vm `/mnt/nav` disk**: ~70 GB free — insufficient for a full-US build or DB. Would require either reclaiming existing storage or relocating the volume.
2.**matt-desktop build-disk capacity**: the gating number for build scratch space is unconfirmed. Must be established before committing to a full-US build.
Until both blockers are resolved, full-US is deferred.
Nominatim v5 (released February 2025) changed the underlying data model relative to 4.x. A full OSM re-import is required; there is no in-place upgrade path.
