reverse geocoding inaccuracy
I know this most likely isn't an immich issue, but it seems the reverse geocoding process is quite inaccurate in some cases.
See the example in attached screenshot. This location is clearly in the city of Paris, not even too close to its limits (the blue circle), but it is tagged as being in "Bagnolet" (suburb just outside Paris, on the eastern side).
This is not correct.
Same goes for all 18 pics under the other cluster (tagged as in "Saint-Ouen", another adjacent surbub).
The only pic that immich really locates in Paris is the one showing as a thumbnail (single pic in this cluster)
And since Paris is its own "administrative county" ("State" level in the new search engine), you can't even see all those pictures together by not selecting a City.
I'm not sure if this is something that should be reported to the geocoding service used by immich, but it definitely leads to a poor experience here
6 Replies
:wave: Hey @larry.fr,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker compose ps docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
1. :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: I have read applicable release notes.
3. :ballot_box_with_check: I have reviewed the FAQs for known issues.
4. :ballot_box_with_check: I have reviewed Github for known issues.
5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
7. :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
If this ticket can be closed you can use the /close command, and re-open it later if needed.The geocoding isn't based on boundaries, but just whichever 'center' is closest
I get this, but it is still inaccurate.
For reference, Synology Photos flags the exact same picture as being in "France, Île-de-France, Paris, Paris, (...)" which is correct.
Same thing for the native gallery app on my android phone.
I don't know about synophotos, but the native gallery on your phone almost certainly calls out to a Google API to do the geocoding. In Immich it's all done locally, which of course puts some restrictions on how much data we can use. There is still some more detailed data we can inject into the process though, and we'll hopefully do that at some point in the future.
thanks for the explanation, and glad to know ther's something in the pipe !
I have been playing with immich for the last week. I have to say I am very impressed overall except for this. There are other improvements I would like to see but I can wait since they seem to be in the pipes. This is the one issue that I do find truly irritates me (even if it is fairly cosmetic).