Bug 381347 - Non expected geolocation error message
Summary: Non expected geolocation error message
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (show other bugs)
Version: 5.5.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-18 05:51 UTC by philippe weyland
Modified: 2020-03-10 17:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0


Attachments
Geolocation error message (488.33 KB, image/png)
2017-06-18 05:51 UTC, philippe weyland
Details

Note You need to log in before you can comment on or make changes to this bug.
Description philippe weyland 2017-06-18 05:51:20 UTC
Created attachment 106152 [details]
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.
Comment 1 philippe weyland 2017-06-25 09:55:33 UTC
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.
Comment 2 philippe weyland 2017-06-26 18:37:51 UTC
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.
Comment 3 philippe weyland 2017-07-02 09:07:00 UTC
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.
Comment 4 caulier.gilles 2017-07-02 09:47:16 UTC
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
Comment 5 philippe weyland 2017-07-02 16:15:20 UTC
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
Comment 6 Maik Qualmann 2020-03-10 17:56:47 UTC
Git commit 656f31462625e3ce6a31d7ea6cb83571859e0375 by Maik Qualmann.
Committed on 10/03/2020 at 17:55.
Pushed by mqualmann into branch 'master'.

use the metadata setting for writing tags and GPS
FIXED-IN: 7.0.0

M  +5    -10   core/libs/database/item/containers/itemgps.cpp
M  +1    -1    core/libs/database/item/containers/itemgps.h
M  +12   -6    core/utilities/geolocation/geoiface/items/gpsitemcontainer.cpp
M  +3    -0    core/utilities/geolocation/geoiface/items/gpsitemcontainer.h

https://invent.kde.org/kde/digikam/commit/656f31462625e3ce6a31d7ea6cb83571859e0375