| Summary: | Preserve timezone offset Timestamp in metadata. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Chris <chrisc.gigamail> |
| Component: | Metadata-Date | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | caulier.gilles, dion, metzpinguin, stephen.j.hilton |
| Priority: | NOR | ||
| Version First Reported In: | 8.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Chris
2024-10-28 22:00:02 UTC
First of all, it would be wrong to simply adopt the existing time offset, because this could also be wrong if you have to correct the date. Maik @Maik I suppose you are right. I'm more asking for configuration options, so my scripted prep of date fields (with exiftool) are not overwritten. Especially if I do not touch the date fields. When date fields are touched, it might also be interesting to default the timezone to what was registered originally, but with ability to change it. A further extension could be to use of GPS coordinates as an option to auto suggest timezones (which may require a paid service). /Chris Additional comment. I could solve this by unchecking "Configure Digikam" -> "Metadata" -> "Behavior" -> "Write This Information to the Metadata" -> "Timestamps" However, I had a bug with that, which caused no metadata to be updated at all inside the files. It was consistently and persistently not saving metadata to some files. But when I was writing up a bug report and made a minimum reproduction, I could not find a way to reproduce the error. So I'm still working on that, but even so... I'd still like any timestamp metadata edited in Digikam to be saved in the files, I'd just like to decide which tags to update and which tags should have timezone info and which tags should be stored in UTC time. Hi, Refereing to your problem from the comment 3, digiKam 8.7.0 pre-release for Windows have been rebuild from scratch today with many improvements and updates especially with the Exiv2 and ExifTool versions. Please check if the problem is reproducible. Link to download: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier When digikam writes xmp files, it only includes date and time in the CreateDate and ModifyDate. It does not add the time zone offset, even if the timezone is shown in the original photograph file's EXIF data. e.g. xmp:CreateDate="2020-01-01T00:01:01.69" xmp:ModifyDate="2020-01-01T00:01:01.69" Any application that prioritises xmp from the sidecar file over exif from the original file reads the local time without knowing the timezone offset. If that application then assumes the time is UTC, the time that it displays will be off. Immich is an example of such an application. If there is no xmp file for a photo, it will read the time/date correctly from the photo's EXIF data (i.e. incorporating the timezone offset). However, as soon as Digikam writes an xmp file, immich will display the time and date as if the time in the xmp file is UTC time. Git commit ad5bb7d1da29dc6d90e4961d53afe79bbfa429b3 by Maik Qualmann. Committed on 19/04/2026 at 06:40. Pushed by mqualmann into branch 'master'. prepare database update to add ImageTagProperties index and a timezone field Related: bug 519125, bug 514970, bug 517889, bug 510261, bug 491608, bug 485836, bug 251357 M +46 -1 core/data/database/dbconfig.xml.cmake.in M +8 -0 core/libs/database/coredb/coredbschemaupdater.cpp https://invent.kde.org/graphics/digikam/-/commit/ad5bb7d1da29dc6d90e4961d53afe79bbfa429b3 |