Bug 481255 - Process reverse geocoding writes locations metadata even if 'Write locations metadata" is unset
Summary: Process reverse geocoding writes locations metadata even if 'Write locations ...
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-ReverseGeoCoding (show other bugs)
Version: 8.2.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-12 09:52 UTC by mahikeulbody
Modified: 2024-02-12 17:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mahikeulbody 2024-02-12 09:52:48 UTC
SUMMARY

Process reverse geocoding writes locations metadata even if 'Write locations metadata" is unset.
Comment 1 Maik Qualmann 2024-02-12 10:24:29 UTC
No, just tested, no location metadata is written.

Maik
Comment 2 caulier.gilles 2024-02-12 10:26:06 UTC
Idem. here... I test with current 8.3.0 and it's not reproducible unde Kubuntu 23.04
Comment 3 mahikeulbody 2024-02-12 11:01:53 UTC
Sorry but I can reproduce it with 8.2.
Comment 4 caulier.gilles 2024-02-12 11:09:31 UTC
In 8.3.0, we have more than 200 files closed as fixed. I strongly advice you to double check with the pre-release bundle :

https://files.kde.org/digikam/
Comment 5 caulier.gilles 2024-02-12 11:10:15 UTC
List a 8.3.0 files closed :

https://invent.kde.org/graphics/digikam/-/blob/master/NEWS?ref_type=heads
Comment 6 mahikeulbody 2024-02-12 11:19:02 UTC
(In reply to caulier.gilles from comment #4)
> In 8.3.0, we have more than 200 files closed as fixed. I strongly advice you
> to double check with the pre-release bundle :
> 
> https://files.kde.org/digikam/

The one that crashes ? I would like ;-)

I hope I am not opening too many bugs already fixed in 8.3.
Of course, I would prefer test 8.3 instead of 8.2.
Comment 7 mahikeulbody 2024-02-12 11:20:12 UTC
(In reply to caulier.gilles from comment #5)
> List a 8.3.0 files closed :
> 
> https://invent.kde.org/graphics/digikam/-/blob/master/NEWS?ref_type=heads

Ok, thanks. I will check that before opening new reports.
Comment 8 mahikeulbody 2024-02-12 12:20:08 UTC
> In 8.3.0, we have more than 200 files closed as fixed. I strongly advice you to double check with the pre-release bundle

I did not find any file closed related to reverse geocoding and this report. So I attached a picture which I am able to reproduce the problem (with 8.2).

(I made exiftool -xmp:all= p.jpg in order to remove all xmp metadata)

1) I select this file, I do reverse geocoding with 'Write locations metadata" is unset (and also "Write locations tags" unset).
2) Apply
3) locations metadata is added
Comment 9 mahikeulbody 2024-02-12 12:23:13 UTC
The file is too large to be attached here. You can download it here : https://transfert.free.fr/lx1mQcL   (only during the next 30 days)
Comment 10 mahikeulbody 2024-02-12 12:26:08 UTC
I tried with another file from the same device (pixel 5) and I cannot reproduce the problem (???).
Comment 11 Maik Qualmann 2024-02-12 12:40:27 UTC
There is definitely no location metadata added. Just removing XMP is not enough, check whether there are any in IPTC, these will be mirrored in XMP if sidecars are in the game.

Maik
Comment 12 Maik Qualmann 2024-02-12 12:46:17 UTC
Also keep in mind that location metadata can still be in the DB, check the template viewer in the right sidebar. Even if you don't write any in the Geolocation Editor, the ones saved in the template can be written again.

Maik
Comment 13 mahikeulbody 2024-02-12 12:54:55 UTC
Indeed there were IPTC metadata locations and removing them don't add anymore XMP metadata locations.

But why these IPTC metadata are added to XMP (really added in the file, not just mirrored in the viewer) ?
Moreover when geo metadatas flags are unset ?

> if sidecars are in the game.

There are not sidecars in the game.
Comment 14 Maik Qualmann 2024-02-12 13:01:56 UTC
You can only choose not to change/add anything in the geolocation editor. If there are any in the DB, they are written as part of the template. In the template we write both IPTC and XMP. There is currently no advanced metadata setting to adjust the behavior of template metadata.

Maik
Comment 15 mahikeulbody 2024-02-12 13:18:58 UTC
Ok, I understand what append, now.

As a tester, I use sometimes exiftool in the middle and that could reveal some points about digikam which are not a real problem for the normal user.

Thanks for the explanation.