Architecture¶
You do not need to understand the internals to use Immich ReverseGeo, but the overall shape is simple: the app reads coordinates from immich, matches them against built-in and downloaded location data, and writes the final place names back.
Main components¶
Web app
The web UI handles settings, manual processing, download management, lookups, and logs.
Built-in data
Country matching and airport matching are available right away from data shipped with the app.
Downloaded country data
Extra per-country data is downloaded when needed so state and city matching can be more precise.
Processing pipeline¶
The background processor:
- reads unprocessed assets from immich
- resolves bundled country
- ensures per-country Overture divisions cache exists
- resolves administrative areas from cached divisions
- optionally queries bundled airport infrastructure
- writes city/state/country back to immich when a complete result is available
Active data sources¶
Built in
Country matching data and airport matching data are included in the app image.
Downloaded on demand
Country-specific data is downloaded locally when needed for better state and city matching.
Optional live lookup help
The Lookup page can also show live Overture Places diagnostics when you want to inspect a point more deeply.
Legacy project¶
Older geoBoundaries, static-airport, and Foursquare code is preserved in the legacy project but is no longer part of the active runtime path.