immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Reverse geocoding forces wrong place name and cannot be manually corrected (locality not searchable) #8280

New Issue
Closed
opened 2026-02-05 13:38:21 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 13:38:21 +03:00
Owner
Copy Link

Originally created by @hottif on GitHub (Jan 20, 2026).

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

Description:

I am running Immich Server 2.4.1 and I’m encountering a reverse-geocoding issue that currently has no usable workaround.

I am an Immich Supporter and have paid for Immich Server, so I’m reporting this in the hope that it can be properly addressed. :-)

Problem summary

  • GPS coordinates are 100% correct

  • The map marker is placed accurately

  • The resolved place name is wrong

  • Manual correction is not possible, because:

    • the correct locality cannot be found in the “Change location” search
    • moving the marker always re-triggers reverse geocoding and overwrites the place name again

This makes it impossible to store the correct location for certain localities.

Concrete example

Coordinates:
48.48703077768053, 13.43796479440789

Correct location:
Vornbach (part of Neuhaus am Inn, Lower Bavaria, Germany)

Immich resolves to:
Neuburg am Inn (several kilometers away)

  • The map marker is placed correctly near Vornbach
  • The place name is always resolved as Neuburg
  • Manually adjusting the marker immediately resets the place name back to Neuburg

GeoNames data is correct

According to GeoNames, the location is resolved correctly:

  • Name: Vornbach
  • Feature class: PPL (populated place)
  • Administrative hierarchy:
    Germany → Bavaria → Lower Bavaria → Landkreis Passau → Neuhaus am Inn

So this does not appear to be a GeoNames data issue.

Manual correction is not possible

In the “Change location” dialog:

  • Searching for “Vornbach” returns no results at all
  • Only larger municipalities can be selected
  • Selecting “Neuhaus am Inn” places the marker incorrectly (~1 km away)
  • Moving the marker back to the correct spot re-applies the wrong place name (“Neuburg”)

There is currently no way to decouple coordinates and place name or to lock a manually chosen name.

Expected behavior

At least one of the following should be possible:

  1. Allow free-text place names or GeoNames-based search in “Change location”
  2. Allow manually selected place names to be locked
  3. Prefer GeoNames populated places over nearby higher-level admin boundaries
  4. Allow disabling automatic reverse geocoding after manual adjustment

Actual behavior

  • Place name is always overwritten by reverse geocoding
  • Localities without strong administrative boundaries cannot be selected
  • Correct GPS data still results in wrong place names

Environment

  • Immich Server: 2.4.1
  • OS: Linux
  • Deployment: Docker
  • Reverse geocoding enabled (default)

If you need additional logs or test coordinates, I’m happy to provide them.

Thank you for your work on Immich — this is one of the few remaining blockers for correct photo organization in rural / historical locations.

The OS that Immich Server is running on

Ubuntu WSL2 on Docker Desktop for Windows

Version of Immich Server

v2.4.1

Version of Immich Mobile App

v2.4.1 build 3030

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

No response

Your docker-compose.yml content

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:release
    volumes:
      - X:/Photos/Gallery:/data
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    ports:
      - "32283:2283"
    depends_on:
      - redis
      - database
      - immich-machine-learning
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:release-cuda
    gpus: all
    environment:
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=compute,utility
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:9
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      - immich_postgres:/var/lib/postgresql/data
    shm_size: 128mb
    restart: always

volumes:
  model-cache:
  immich_postgres:

Your .env content

# Speicherorte IM Container (weil X:/Photos/Gallery nach /data gemountet ist)
UPLOAD_LOCATION=/data/upload
LIBRARY_LOCATION=/data/library
THUMBNAIL_LOCATION=/data/thumbs
PROFILE_LOCATION=/data/profile
ENCODED_VIDEO_LOCATION=/data/encoded-video
BACKUP_LOCATION=/data/backups

# DB bleibt wie bei dir
DB_DATA_LOCATION=./postgres
TZ=Europe/Berlin
IMMICH_VERSION=v2
DB_PASSWORD=mypassword
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Reproduction steps

  1. Add photo with GPS coordinates of Vornbach (48.48703077768053, 13.43796479440789)
  2. Look at info panel in image viewer
  3. Info panel shows "Neuburg"
Image

Relevant log output

Additional information

No response

Originally created by @hottif on GitHub (Jan 20, 2026). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug **Description:** I am running **Immich Server 2.4.1** and I’m encountering a reverse-geocoding issue that currently has no usable workaround. I am an **Immich Supporter** and have paid for Immich Server, so I’m reporting this in the hope that it can be properly addressed. :-) --- ### Problem summary * GPS coordinates are **100% correct** * The **map marker is placed accurately** * The **resolved place name is wrong** * Manual correction is **not possible**, because: * the correct locality cannot be found in the “Change location” search * moving the marker always re-triggers reverse geocoding and overwrites the place name again This makes it impossible to store the correct location for certain localities. --- ### Concrete example **Coordinates:** `48.48703077768053, 13.43796479440789` **Correct location:** Vornbach (part of Neuhaus am Inn, Lower Bavaria, Germany) **Immich resolves to:** Neuburg am Inn (several kilometers away) * The map marker is placed correctly near Vornbach * The place name is always resolved as *Neuburg* * Manually adjusting the marker immediately resets the place name back to *Neuburg* --- ### GeoNames data is correct According to GeoNames, the location is resolved correctly: * Name: Vornbach * Feature class: PPL (populated place) * Administrative hierarchy: Germany → Bavaria → Lower Bavaria → Landkreis Passau → Neuhaus am Inn So this does **not** appear to be a GeoNames data issue. --- ### Manual correction is not possible In the **“Change location”** dialog: * Searching for **“Vornbach”** returns no results at all * Only larger municipalities can be selected * Selecting “Neuhaus am Inn” places the marker incorrectly (~1 km away) * Moving the marker back to the correct spot re-applies the wrong place name (“Neuburg”) There is currently **no way to decouple coordinates and place name** or to lock a manually chosen name. --- ### Expected behavior At least one of the following should be possible: 1. Allow free-text place names or GeoNames-based search in “Change location” 2. Allow manually selected place names to be **locked** 3. Prefer GeoNames populated places over nearby higher-level admin boundaries 4. Allow disabling automatic reverse geocoding after manual adjustment --- ### Actual behavior * Place name is always overwritten by reverse geocoding * Localities without strong administrative boundaries cannot be selected * Correct GPS data still results in wrong place names --- ### Environment * Immich Server: 2.4.1 * OS: Linux * Deployment: Docker * Reverse geocoding enabled (default) --- If you need additional logs or test coordinates, I’m happy to provide them. Thank you for your work on Immich — this is one of the few remaining blockers for correct photo organization in rural / historical locations. ### The OS that Immich Server is running on Ubuntu WSL2 on Docker Desktop for Windows ### Version of Immich Server v2.4.1 ### Version of Immich Mobile App v2.4.1 build 3030 ### Platform with the issue - [x] Server - [ ] Web - [ ] Mobile ### Device make and model _No response_ ### Your docker-compose.yml content ```YAML name: immich services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:release volumes: - X:/Photos/Gallery:/data - /etc/localtime:/etc/localtime:ro env_file: - .env ports: - "32283:2283" depends_on: - redis - database - immich-machine-learning restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:release-cuda gpus: all environment: - NVIDIA_VISIBLE_DEVICES=all - NVIDIA_DRIVER_CAPABILITIES=compute,utility volumes: - model-cache:/cache env_file: - .env restart: always redis: container_name: immich_redis image: docker.io/valkey/valkey:9 restart: always database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: '--data-checksums' volumes: - immich_postgres:/var/lib/postgresql/data shm_size: 128mb restart: always volumes: model-cache: immich_postgres: ``` ### Your .env content ```Shell # Speicherorte IM Container (weil X:/Photos/Gallery nach /data gemountet ist) UPLOAD_LOCATION=/data/upload LIBRARY_LOCATION=/data/library THUMBNAIL_LOCATION=/data/thumbs PROFILE_LOCATION=/data/profile ENCODED_VIDEO_LOCATION=/data/encoded-video BACKUP_LOCATION=/data/backups # DB bleibt wie bei dir DB_DATA_LOCATION=./postgres TZ=Europe/Berlin IMMICH_VERSION=v2 DB_PASSWORD=mypassword DB_USERNAME=postgres DB_DATABASE_NAME=immich ``` ### Reproduction steps 1. Add photo with GPS coordinates of Vornbach (48.48703077768053, 13.43796479440789) 2. Look at info panel in image viewer 3. Info panel shows "Neuburg" <img width="359" height="425" alt="Image" src="https://github.com/user-attachments/assets/dfccabd4-8011-4d4b-9112-101378f9d8de" /> ### Relevant log output ```shell ``` ### Additional information _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#8280
Delete Branch "%!s()"

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?