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

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

            Bug ID: 381347
           Summary: Non expected geolocation error message
           Product: digikam
           Version: 5.5.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Geolocation-Editor
          Assignee: [hidden email]
          Reporter: [hidden email]
  Target Milestone: ---

Created attachment 106152
  --> https://bugs.kde.org/attachment.cgi?id=106152&action=edit
Geolocation error message

While my Digikam settings do not require to save metadata into files, when I
Apply the new geolocations I get the attached error message.
I'm expecting to have the geolocation (as any other tag, xmp or iptc data) only
in digikam database.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

--- Comment #1 from philippe weyland <[hidden email]> ---
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 case, Digikam,
unlike for raw files, doesnt' keep the geolocation in database.
I think that's is an important feature because the original files should not be
modified.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

--- Comment #2 from philippe weyland <[hidden email]> ---
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 are stored in the database but Digikam 5.6 doesn't show
them while Digikam 5.5 does.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

--- Comment #3 from philippe weyland <[hidden email]> ---
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 file, as
Informations, but unlike Tags.

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #4 from [hidden email] ---
yes, the problem is know and another report is open about this feature.

The Metadata interface must be patched to re-route GPS info accordingly with a
dedicated settings. It's not yet done.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=381347

--- Comment #5 from philippe weyland <[hidden email]> ---
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 Side Bar Metadata / 3. XMP => xmp file.
All information flow from 1. to 3. except (not seen in 2.):
- Description / Pick label, Color label and Rating
- Informations / Subjects (I could not define them from templates)
- Map / Altitude, Latitude & Longitude

--
You are receiving this mail because:
You are the assignee for the bug.