-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata: UTC should be overridden by local time with unknown zone #2876
Comments
Please use "exiftool -n -g filename". Also, if you want us to test this, we require a file sample: https://photoprism.app/contact |
I already sent to photo to your email address.
|
Was this file directly created as JPEG by an iPhone or did you convert it from HEIC, either manually or automatically when syncing / uploading? Never this this before and we have a lot of iPhone users... |
I guess the solution is to use "SubSecDateTimeOriginal" since "CreateDate" does not contain the offset directly. For whatever reason the offset is exclusively in "OffsetTime", although the other timestamps include it as expected:
|
It was taken as by a friend in a HEIC format, uploaded to Google Photos and shared. I downloaded it from Google Photos and it was already a JPEG. Reached out to her to get the original, but I'm still waiting. I actually have another example from iPhone 6s, picture taken in GMT+1 at 12:54, downloaded via USB. Sending the original via email, in the same
|
The whole thing was bugging me quite a bit so I did some test. Turns out a complete rescan corrects the time to actual local time (with no changes made to the original). I took a look at the After initial indexingAfter a full re-scanExiftool output of the original after re-index
|
Problem might be how the built-in Exif parser and data from Exiftool interfere with each other the first time. |
It would be awesome if initial indexing would read the time correctly. Indexing may be a lengthy operation when you have a lot o pictures in a single folder, so I'd like to avoid that in the future :) |
We will improve this. It's Sunday, please give it a bit of time :) |
Signed-off-by: Michael Mayer <michael@photoprism.app>
Signed-off-by: Michael Mayer <michael@photoprism.app>
An updated preview build will be available for testing soon: We hope you have a few minutes to let us know if it works so we can release the update tomorrow! |
Happy testing! 🎁 |
Everything looks fine to me :)
|
I have a picture taken with an iPhone 14 around 13:30 GMT+1. Picture does not have any GPS data. Exiftool snippet below.
When imported to Photoprism, it is displayed as taken 12:30:04 local time, but actually it is actually UTC
I would expect the timestamp to be 13:30:04 of local time. I have the same problems with other iPhone photos (taken in 2021 and 2022 with iPhone 6s and 14). Other pictures, taken with Samsung S8 are imported correctly. One thing I noticed is that iPhone pictures have
Offset Time
tags, but Samsung's photos don't. I sent the photo to samples email.I am using the latest image with MariaDB.
The text was updated successfully, but these errors were encountered: