Bug 311689 - Reverse Geocoding tags are sometimes not saved
Summary: Reverse Geocoding tags are sometimes not saved
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-ReverseGeoCoding (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-14 13:51 UTC by Milan Knížek
Modified: 2017-08-18 19:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.11.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Knížek 2012-12-14 13:51:47 UTC
The images already have GPS info embedded in metadata and it is shown correctly in Image / Geolocation.

After clicking on "Apply reverse geocoding" button, the correct tags are shown next to the images.

After clicking on "Apply" button, all seems to be saved. Corresponding tag structure is created, too.

After clicking on "Close" button, majority of images in thumbnail view have the tags from reverse-geocoding applied.

However, some not - such images do not have the /location tags at all assigned.

There does not seem to be any pattern why some images are excluded. The bug appears on JPEGs from more cameras or RAW convertors. I use "save tags to files" option for metadata. Command line does not show any specific error.

Workaround is to select images w/o tags manually and start over once again. E.g. on a set of 95 images I had to repeat the steps five times.

Reproducible: Sometimes




Interestingly, if Image / Geolocation is used not only for reverse geocoding, but also for setting the GPS coordinates, these are saved always to all images...
Comment 1 caulier.gilles 2015-05-18 13:23:25 UTC
Milan,

This file still valid using last kipi-plugins 4.10.0 ?

Gilles Caulier
Comment 2 Milan Knížek 2015-06-01 19:44:52 UTC
I still use 4.9.0 (Arch Linux) and the bug seems to be resolved already. Hence I am closing the issue now.