[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In|

[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 --- Comment #5 from philippe weyland --- OK, thanks. Assuming all metadata could be saved in the xmp structure, I've checked the path: 1. Informations + Tags + Geolocation (all information are in database) => 2. Right

[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 --- Comment #3 from philippe weyland --- Side effect. Unlike other Metadata (managed by Item/Edit Metadata), geolocation is stored in the database. But Item/Write Metadata to File doesn't write the geolocation to the

[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 --- Comment #2 from philippe weyland --- To correct the previous comment "set the jpg as read only. But in that case, Digikam, unlike for raw files, doesnt' keep the geolocation in database." This is not exact, the data

[digikam] [Bug 381347] Non expected geolocation error message

https://bugs.kde.org/show_bug.cgi?id=381347 --- Comment #1 from philippe weyland --- The other side of this issue is that I've not found the way to prevent Digikam to write the geolocation to jpg file. In fact there is one: set the jpg as read only. But in that