Summary: | exif dates shown are wrong in some images | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Martin Althoff <martin.althoff> |
Component: | Metadata-Exif | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | metzpinguin |
Priority: | NOR | ||
Version: | 7.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/kde/digikam/commit/5d8b8cf2f862ebd52259dc2355fac6f7c24a3083 | Version Fixed In: | 7.0.0 |
Description
Martin Althoff
2020-03-30 08:21:35 UTC
Ok, since the original does not appear again in the image except for the GPS date (which we are not testing), it fails in the final test because we do not consider the priority in the final test. I will fix it. Yes, determining the correct date is not easy. In principle, your camera has already made a mistake, since digitization and original date are so different. Maik Git commit 5d8b8cf2f862ebd52259dc2355fac6f7c24a3083 by Maik Qualmann. Committed on 30/03/2020 at 17:11. Pushed by mqualmann into branch 'master'. use the date with the highest priority in the end result FIXED-IN: 7.0.0 M +2 -1 NEWS M +6 -12 core/libs/metadataengine/engine/metaengine_item.cpp https://invent.kde.org/kde/digikam/commit/5d8b8cf2f862ebd52259dc2355fac6f7c24a3083 Maik,
Thanks for that fix. You are right, the camera (or further handling) has introduced two
unmatching dates.
If date conflicts arise which are difficult to resolve, I wonder if it helps to give the
user a choice about dates. As you said, making decision on the "correct" date is
challenging, let the user do so.
I have no idea why in my files a 2002 date appears, it was taken 2016. This is a challenge
of dealing with images that come from hardware that is long gone.
Thanks again and keep healthy,
Martin
On Mon, 2020-03-30 at 11:19 +0000, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=419409
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |metzpinguin@gmail.com
>
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> Ok, since the original does not appear again in the image except for the GPS
> date (which we are not testing), it fails in the final test because we do not
> consider the priority in the final test. I will fix it. Yes, determining the
> correct date is not easy. In principle, your camera has already made a mistake,
> since digitization and original date are so different.
>
> Maik
>
Since we have had this topic for a long time, I now have a lot of test images with date information. There are images where the users have already corrected the dates in the XMP field with other programs, but Exif is still wrong, etc. With a manual selection, it would only fit for a part of the images. No, digiKam must solve this itself as intelligently as possible. Maik Got you :) makes sense At the risk of being annoying (sorry), how about looking possibly existing gps dates for judgement? Martin |