-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable reverse geocoding using Nominatim #84
Comments
Yes, Nominatim. No, location is resolved for all picture files that have coordinates (regardless of the country), and there are currently no options to disable this behaviour (except for blocking access to that service at the server level). |
Thank you. I forgot about filtering traffic to the domain altogether... I'll do that with my Pi-hole. |
Ok, I tried it, and unfortunately a Nextcloud notification pops up every time it tries reverse geocoding (which is every time I click on a photo with lat/long exif metadata), saying: "Connection to server lost". Just a bit annoying, but it does of course prevent any connections to Nominatim since the DNS lookup fails (since the Pi-hole returns |
See also: #85 |
Maybe it is possible to implement a better workaround, but in any case it would be just a workaround. I haven't considered that the use of Nominatim could have an impact on privacy, but I'm open to argument. To understand better what was already said - the issue mentions "United States address" - is there anything special about that country addresses? As this can potentially be a feature, I'm reopening. |
I'm sure they're fine, just allow me to play devil's advocate. I don't know anything about the service. Someone runs their servers, right? Who are they? Where are they, and what laws are they governed by? What data are they sent (IP addresses for my request, lat/long coords for my photos, etc)? Who has usage rights for these data besides Nominatim? What does Nominatim do with the data? What are their terms? Did I agree to their EULA? What rights do I have over the data I send? What about users in Europe or California? Again, I'm sure it's all fine, this code is fine, they're fine, there's not enough data to identify me, etc... but I'd rather not care to even think about Nominatim and I don't want or need the reverse geocoding feature, so I'd rather not send any data their way at all. I try to generally follow a "local first" principle when it comes to my data. This includes reverse geocoding, face recognition, stuff like that. If I can do it offline, I prefer to. I thought given the "private cloud" ethos of Nextcloud that other admins/users might appreciate having this manner of control as well.
Nope, that's just where I live, so I wasn't sure how it behaves for addresses outside the US.
Cool, thanks. That was my idea as well, that this could be a feature/enhancement if it is desirable. Thanks for your time, -Adam |
I noticed metadata for some of my photos includes a "Location" line with a human-readable United States address. How is this geo-to-location translation performed?
Ah, looks like Nominatim / OSM. Is that right? Is there any way to turn this off? I guess I'd rather not reach out to that service because I don't need the "Location" line in the metadata.
The text was updated successfully, but these errors were encountered: