immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 08:41:28 +03:00
Code Issues 26 Packages Projects Releases 10 Wiki Activity

[BUG] Response from database for reverse geocoding ... was null #1820

New Issue
Closed
opened 2026-02-05 03:58:56 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 03:58:56 +03:00
Owner
Copy Link

Originally created by @SlavikCA on GitHub (Dec 18, 2023).

The bug

In the log, I see quite a few messages about reverse geocoding failing for valid coordinates.
For example:

[Nest] 7 - 12/17/2023, 10:57:37 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0635888888889, longitude: -120.78605 was null
[Nest] 7 - 12/17/2023, 10:57:37 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0639472222222, longitude: -120.786963888889 was null
[Nest] 7 - 12/17/2023, 11:00:53 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0635305555556, longitude: -120.787122222222 was null
[Nest] 7 - 12/17/2023, 11:00:53 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0634777777778, longitude: -120.791644444444 was null
[Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0620583333333, longitude: -120.836644444444 was null
[Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.06015, longitude: -120.842733333333 was null
[Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0613361111111, longitude: -120.855058333333 was null
[Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0621666666667, longitude: -120.864147222222 was null
[Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0625722222222, longitude: -120.866586111111 was null

The OS that Immich Server is running on

Docker on Synology

Version of Immich Server

1.91.3

Version of Immich Mobile App

n/a

Platform with the issue

  • Server
  • Web
  • Mobile

Reproduction steps

1. I installed new instance
2. I added external library
3. I started scan

I would gladly share the photo, so issue can be reproduce,
but unfortunately I can not see the filename of the photo in the log,
so I can't figure out which files has this issue
Originally created by @SlavikCA on GitHub (Dec 18, 2023). ### The bug In the log, I see quite a few messages about reverse geocoding failing for valid coordinates. For example: [Nest] 7 - 12/17/2023, 10:57:37 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0635888888889, longitude: -120.78605 was null [Nest] 7 - 12/17/2023, 10:57:37 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0639472222222, longitude: -120.786963888889 was null [Nest] 7 - 12/17/2023, 11:00:53 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0635305555556, longitude: -120.787122222222 was null [Nest] 7 - 12/17/2023, 11:00:53 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0634777777778, longitude: -120.791644444444 was null [Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0620583333333, longitude: -120.836644444444 was null [Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.06015, longitude: -120.842733333333 was null [Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0613361111111, longitude: -120.855058333333 was null [Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0621666666667, longitude: -120.864147222222 was null [Nest] 7 - 12/17/2023, 11:00:54 PM WARN [MetadataRepository] Response from database for reverse geocoding latitude: 49.0625722222222, longitude: -120.866586111111 was null ### The OS that Immich Server is running on Docker on Synology ### Version of Immich Server 1.91.3 ### Version of Immich Mobile App n/a ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Reproduction steps ```bash 1. I installed new instance 2. I added external library 3. I started scan I would gladly share the photo, so issue can be reproduce, but unfortunately I can not see the filename of the photo in the log, so I can't figure out which files has this issue ```
OVERLORD commented 2026-02-05 03:59:01 +03:00
Author
Owner
Copy Link

@zackpollard commented on GitHub (Dec 18, 2023):

This is a symptom of the way we do reverse geocoding now within postgres. We limit the results to 25km, so if there is no place within 25km that has a population of > 500 people, we will get no results. We log this out for now due to it being an unexpected but not impossible scenario. This is probably something we will fix in later revisions of the reverse geocoding code, but for now it is expected behaviour.

@zackpollard commented on GitHub (Dec 18, 2023): This is a symptom of the way we do reverse geocoding now within postgres. We limit the results to 25km, so if there is no place within 25km that has a population of > 500 people, we will get no results. We log this out for now due to it being an unexpected but not impossible scenario. This is probably something we will fix in later revisions of the reverse geocoding code, but for now it is expected behaviour.
OVERLORD commented 2026-02-05 03:59:02 +03:00
Author
Owner
Copy Link

@mschiff commented on GitHub (Jul 7, 2024):

I am seeing lots of the same messages. But what does it mean? Will those coordinates be used for the map view or not?

Would it be possible to return the area/country/continent/ocean if no "Place" is found? I for example have many shots from ocean crossings which I would love to see at least in a category like "Pacific Ocean" or something.

TIA

@mschiff commented on GitHub (Jul 7, 2024): I am seeing lots of the same messages. But what does it mean? Will those coordinates be used for the map view or not? Would it be possible to return the area/country/continent/ocean if no "Place" is found? I for example have many shots from ocean crossings which I would love to see at least in a category like "Pacific Ocean" or something. TIA
OVERLORD commented 2026-02-05 03:59:05 +03:00
Author
Owner
Copy Link

@zackpollard commented on GitHub (Jul 8, 2024):

We are currently looking into improvements to the reverse geocoding, there is an open PR to get at least the correct country even if the normal process doesn't find a place. Oceans however are entirely unsupported right now, but might come with some of the other improvements we are currently looking into.

@zackpollard commented on GitHub (Jul 8, 2024): We are currently looking into improvements to the reverse geocoding, there is an open PR to get at least the correct country even if the normal process doesn't find a place. Oceans however are entirely unsupported right now, but might come with some of the other improvements we are currently looking into.
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
documentation
external-library
format
good first issue
needs-answer
nice to have
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#1820
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?