matt/echo6-docs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
echo6-docs/vault/projects/nominatim-v5-reimport.md
echo6-autocommit df50f03fd1 auto: docs sync 2026-06-20T00:00:07+00:00 
Files changed: .claude/settings.local.json engine/lint-report.md vault/.obsidian/workspace.json vault/.trash/2026-06-19.md vault/.trash/Untitled.canvas vault/CLAUDE-baseline.md vault/projects/fleet-patch-audit.md vault/projects/nominatim-v5-reimport.md
2026-06-20 00:00:07 +00:00

2.1 KiB
Raw Blame History

title type tags related status updated
Nominatim v5 Re-import (deferred project) project
recon
storage
planned 2026-06-19

Nominatim v5 Re-import (deferred project)

Spun off from the fleet-patch-audit (2026-06-19). Explicitly out of scope for that patch pass — to be scheduled as its own maintenance window.

Context

Nominatim on recon-vm (VM 1130, data node) is running 4.5.0 via Docker image mediagis/nominatim:4.5 (~14 months old). Latest upstream is 5.3.2.

This is NOT a routine version bump. Nominatim v5 (released February 2025) changed the underlying data model. Moving from 4.x to 5.x requires deploying the mediagis/nominatim:5.x image and running a full OpenStreetMap re-import — there is no in-place upgrade path.

Coupled dependency: Photon

Photon must be upgraded from 1.1.0 → 1.2.0 in coordination. Photon 1.2.0 was released specifically to read the Nominatim v5 data model. Upgrading only one side risks incompatibility; both must move together at cutover.

Constraints and risks

  • Disk is the primary blocker. The data node is at ~92% capacity (~73 GB free). A full OSM re-import is large and disk-heavy. The import must target external or provisioned storage — not the existing data pool. Disk and time budgets must be planned before starting.
  • Re-imports are slow; schedule a maintenance window with adequate runway.
  • The 4.5 deployment must remain live until validation is complete — do not destroy it before cutover.

Suggested steps (high level)

  1. Provision sufficient disk on or attached to recon-vm for the import scratch space and new data volume.
  2. Stand up nominatim:5.x alongside the running 4.5 deployment (parallel, not replacement).
  3. Run a fresh OSM import into the new deployment.
  4. Upgrade Photon to 1.2.0 and point it at the new Nominatim v5 data.
  5. Validate geocode and reverse-geocode parity between old and new stacks.
  6. Cut over (update any consumers pointing at Nominatim/Photon endpoints).
  7. Retire the 4.5 deployment and reclaim its disk.

Status

Deferred. Not scheduled. Pick this up as a standalone maintenance window separate from routine fleet patching.