| Summary: | No support to resync GPS data from digikams database into into jpg files | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | krienke |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | b-misc, caulier.gilles, mephisto, metzpinguin |
| Priority: | NOR | ||
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/kde/digikam/commit/5f58c6e079a730d68e218f0d5b8e384900db9bc0 | Version Fixed In: | 7.0.0 |
| Sentry Crash Report: | |||
|
Description
krienke
2010-03-01 11:01:14 UTC
This file still valid using digiKam 3.5.0 ? Gilles Caulier Just tested with digikam 3.5.0. This bug report is still valid. GPS information is not rewritten when using "More->Write Metadata to each file" in sidetab "Caption/Tags". Ok, Thanks And with Maintenance tool ? You can process now a single album to sync metadata with DB. It's the same problem or not ? Just to know if problem is general or only limited to caption and tags sidebar. Gilles Caulier The maintenance tool doesn't do the job either. It writes all sort of other meta data like tags, camera info etc into exif, iptc and xmp but no gps tags like GPSLongitude and GPSLatitude etc. Rainer Yesterday I ran into the same problem: In the past I had geo-located many but not all photos and yesterday I began correcting some wrong geo tags and setting missing ones. For the initial test as well as most images that seemed to work fine, but at some point in time I realized, that there are images where digikam shows the corrected gps data, but the xmp files are not updated correctly. Furthermore there might be a bug that gps data is written into the jpg although I've set it to write to metadata only. I tried to get the gps data in the sidecar files by both Write Metadata to File and by using the Maintenance Tool, but neither of them worked. Now I wonder how I can check that all gps tags are written correctly to the xmp's - yesterday I loaded test files into darktable, but that's not perfect and doesn't scale that well... And the fact that gps coordinates can be specified in different formats doesn't help either, converting them isn't that much fun... Is there a way to force digikam to write the gps data into the xmp files, maybe on the command line? Another idea for a workaround? Do you need more info or is there another way I can help? My settings: write all metadata to sidecar files only. My version: digikam 4.4 on Debian Jessie (4.14 in jessie-backports misses gps support completely, but that's a different problem). *** Bug 418658 has been marked as a duplicate of this bug. *** This bug has been reported 10 years ago and is still valid (I also checked against digikam 7.0.0 beta 2, bug is still present). Any chances it will get fixed soon? We currently have no configuration option to enable or disable the writing of GPS data. We could connect it to an existing option e.g. pair with tags when tag writing is enabled. Or create an additional option for GPS. Gilles, what do you think? The geolocation tool always writes the GPS information into the metadata. Maik Well, i vote for a stand alone option for GPS info, excepted if user feedbacks in bugzilla want another workaround. Gilles I would vote for a separate option as well. Actually, this was the first thing I was looking for after realizing that GPS data is missing in the exported xmp files. Yes, an extra option was my thought. Maik Git commit 5f58c6e079a730d68e218f0d5b8e384900db9bc0 by Maik Qualmann. Committed on 09/03/2020 at 22:01. Pushed by mqualmann into branch 'master'. add metadata option to write GPS data to the image Related: bug 418658 FIXED-IN: 7.0.0 M +3 -1 NEWS M +28 -4 core/libs/fileactionmanager/metadatahub.cpp M +2 -1 core/libs/fileactionmanager/metadatahub.h M +5 -0 core/libs/metadataengine/engine/metaenginesettingscontainer.cpp M +1 -0 core/libs/metadataengine/engine/metaenginesettingscontainer.h M +11 -1 core/utilities/setup/metadata/setupmetadata.cpp https://invent.kde.org/kde/digikam/commit/5f58c6e079a730d68e218f0d5b8e384900db9bc0 Great, thanks for the quick fix. I will evaluate it with 7.0.0beta3 release and give feedback here when I find any issues. |