Bug 472704

Summary: Tags are not saved on exit
Product: [Applications] digikam Reporter: Mitch Rauth <mitch>
Component: Geolocation-ReverseGeoCodingAssignee: Digikam Developers <digikam-bugs-null>
Status: CLOSED NOT A BUG    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.1.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In: 8.2.0
Sentry Crash Report:

Description Mitch Rauth 2023-07-27 15:12:05 UTC 
SUMMARY
After adding tags by ReverseGeoCoding in Geolocation Editor, these are not saved to the image after exiting.

STEPS TO REPRODUCE 
remark: I use digikam with German as selected language and are translating back, thus the menues and buttons might be called slighly differently in the English version.

I updated from 7.10.0 to 8.1.0 and did my normal workflow.

1. Select at least one image with coordinates in the main grid view
2. Open "Geolocation Editor" 
3. select the image, click on "Georeferencing", click on "do reverse geocoding" => tags corresponding to the selected setting are added to the image.
4. Click on "Close" and confirm that the changes should be saves "Yes"
5. Hove with the mouse over the image in the main grid view. 

OBSERVED RESULT
The tags have not been saved

EXPECTED RESULT
The tags are saved and visible for the image

SOFTWARE/OS VERSIONS
Windows: Windows 10 Pro 21H2, build 19044.3086

ADDITIONAL INFORMATION
Downgrading to digikam 7.10.0 and repeating the workflow on exactly the same images yields the expected result
Comment 1 Maik Qualmann 2023-07-27 16:47:38 UTC 
Expand the options in the reverse geolocation tool and enable tag writing. You can now decide whether you only want to write IPTC location metadata and/or also tags.

Maik
Comment 2 Maik Qualmann 2023-07-27 16:52:32 UTC 
Note this Bug 469015, for new users on digiKam this option is already always enabled.

Maik
Comment 3 Mitch Rauth 2023-07-28 06:36:48 UTC 
Wow, thanks for this hint. Works fine. Would have never thought of it and did not find 469015 when searching for a known bug.
I'll close this issue.