-
-
Notifications
You must be signed in to change notification settings - Fork 94
Allow photos to be geotagged if they have no geotag at all so far #1216
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
Comments
You can place Fotos via the right click menu. Additionally, there is the button suggest photo location. This might load a while. It get the locations from GPX tracks or device location for the time the image was taken. |
Thanks for the comment, however, there is no right-click nextcloud-menue on photos for me (no matter how I access them, e.g. the files or photo app); I only get the browser's context menu. I know about the GPX tracks, but again I don't have that. So right now, the challenge remains for me - how to geotag a new photo who has no geo information at all on the map? |
There should be a right click menu on the map. |
I found it and can select a photo, but then nothing happens. After selecting a photo and confirming it the view returns to the map. Even another left- or right-click just brings up the usual contact menues, but not placing the photo (geo-tagging) on a location. Hmm, what am I doing wrong? |
Sometimes pictures don't have correct geotags - either the wrong place or no geo-info at all.
To correct a wrong geo-place it's really great to use the move-feature of 'maps' to easily update the place of photos taken.
What I'm missing is geo-tagging for pictures with no geo-information at all. They simply don't appear on the map, so can't be moved around (obviously). What I'm looking for is a kind of place on the webpage that contains all of the photos without geotagging, so one could take photos out of it and move it onto the map.
Hope, I did not overlook something, but searching around did not reveal anything yet...
The text was updated successfully, but these errors were encountered: