Bug 251357 - SCHEMA : add time zone support as properties of items
Summary: SCHEMA : add time zone support as properties of items
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Schema (other bugs)
Version First Reported In: 2.8.0
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 443098 456262 474834 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-09-15 19:11 UTC by Matthieu Pupat
Modified: 2026-07-24 17:24 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthieu Pupat 2010-09-15 19:11:40 UTC
Version:           1.2.0 (using KDE 4.4.5) 
OS:                Linux

It would be nice to have time zone support. I take some pictures in different timezones and would like to be bale to have the "local time" of the picture as well as the time zone it was taken in.

I know some other softwares does this by;

* storing "local"  date and time in EXIF "Date and Time"
* storing "UTC" date and time in EXIF "GPS Date Stamp" and "GPS Time Stamp" respectively
* figuring out the time zone from the UTC and local time

Reproducible: Always
Comment 1 caulier.gilles 2010-09-15 19:32:28 UTC
This is a job for digiKam DB properties, to dispatch later to plugin...

Gilles Caulier
Comment 2 julien.t43+kde 2012-12-01 19:52:38 UTC
still valid in 2.8.0.
got a mixup of chronological order when traveling timezone.
Comment 3 José Oliver-Didier 2021-01-28 01:50:42 UTC
Now that time zone is supported in the new EXIF standard it would be nice to revisit this bug.

EXIF 2.32 Time Zone fields:
0x9010 OffsetTime string ExifIFD (time zone for ModifyDate)
0x9011 OffsetTimeOriginal string ExifIFD (time zone for DateTimeOriginal)
0x9012 OffsetTimeDigitized string ExifIFD (time zone for CreateDate)

Also, timezone are supported in XMP dates.

Ref email sent to the Digikam Mailing list: http://digikam.1695700.n4.nabble.com/digiKam-users-Determining-Time-Zone-based-on-date-location-and-supporting-new-EXIF-time-zone-offset-s-td4714273.html
Comment 4 Maik Qualmann 2021-09-29 05:59:23 UTC
*** Bug 443098 has been marked as a duplicate of this bug. ***
Comment 5 José Oliver-Didier 2023-05-10 20:52:38 UTC
Adding comment from Bug 377857

The MWG 2.0 spec (the group seems to have disbanded, but the spec is still referenced) has some thoughts on timezones on page 33. https://s3.amazonaws.com/software.tagthatphoto.com/docs/mwg_guidance.pdf

Also, something which I stumbled upon some time ago:
"TimeZoneOffset is a non-standard tag that was made before the EXIF standard actually added time zone tags.  There are three time zone tags, EXIF:OffsetTimeOriginal, EXIF:OffsetTime, and EXIF:OffsetTimeDigitized, which correspond to EXIF:DateTimeOriginal, EXIF:ModifyDate, and EXIF:CreateDate respectively."
https://exiftool.org/forum/index.php?topic=13170.0
Comment 6 Maik Qualmann 2023-09-24 14:22:08 UTC
*** Bug 474834 has been marked as a duplicate of this bug. ***
Comment 7 caulier.gilles 2025-04-11 23:50:48 UTC
*** Bug 456262 has been marked as a duplicate of this bug. ***
Comment 8 José Oliver-Didier 2025-05-04 11:39:22 UTC
Checking up on this old bug. Any updates?
Comment 9 Maik Qualmann 2026-04-19 06:41:25 UTC
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 495506, bug 491608, bug 485836

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
Comment 10 caulier.gilles 2026-07-24 06:20:43 UTC
Maik,

What's about this file and other ones related to this topic ? These can be closed now ?

Gilles
Comment 11 Maik Qualmann 2026-07-24 17:24:53 UTC
No, it cannot be closed yet. Only a necessary database update was performed; the code to handle time zones still needs to be written. I am planning to do that in the autumn.

Maik