-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Date of capture issues with different time zones #397
Comments
Are you importing a google takeout archive? |
No. Asia/Shanghai(GMT +8). |
Linux? Windows? MacOS? |
Windows |
The system tries to guess the date of capture without reading its content, based on the name of the file or on its full path. In the first screen shot, the date is taken from the file name: IMG_20230925_165908.jpg. In the second screen shot, the name isn't not enough to infer the date. So the file is read to file the relevant info. |
But in my country, phones usually use the local time zone :( Is it possible to add a configuration to set the time zone? |
Its a google Pixel... all UTC, in USA as well... surely the same in China. Could you run the exiftool command on one of your IMG file and share the result? |
|
Thanks. The time zone in the exif aren't precised for the relevant fields:
So this isn't easy |
But the GPS date could help
|
but there still many photos not have GPS info😢 Can't we simply configure the time zone of the date is captured from the |
I'm wondering how immich does in that case. What date is used when you drop one of your files on the application page? I'm thinking to the following:
|
I mean, take on file from your directory and import it directly in the immich web page, and check its time |
First of all, thank you for developing immich-go, which helped me a lot to start using immich.
Here is my usage situation:
I am importing photos from a directory and the capture date works fine.
But since I live in GMT+8:00, the date in the photo file name also corresponds to GMT+8:00.
I checked the log file and found
capture date"="2022-08-23 14:23:39 +0000 UTC"
, but I looked through the README and there was no configuration for setting the time zone.The text was updated successfully, but these errors were encountered: