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
Local date extracted instead of UTC #84
Comments
Most cameras do not store the timezone in their EXIF data, and you dont have any way to know which timezone the date stored in EXIF is. The current code for handling the dates is here: exifr/src/dicts/tiff-revivers.mjs Lines 48 to 62 in 6cbf6e9
If there is a timezone indication it is dropped, and the date is created as if it was using the current timezone. You can check the exact value in your file using https://exif.tools. If a timezone is indeed included, then we should probably patch the current implementation to take it into account. You can also use the |
Thank you for your reply! I understand. By luck, in my project I developed a time offset compensation using a QRCode, it was initialy made to fix small offsets (generally for some seconds between the clock of the camera and my reference clock) but it also fixes this kind of issue. Thank you I know the reason, thanks! |
I have an issue with the date fields (CreateDate, ModifyDate, DateTimeOriginal) and time offsets.
The date extracted from these fields is formated like an UTC (GMT 0) date but the issue I have is the value I read matches with the local time.
For example, if I take a picture in France at 11:39:54 (GMT+1), the value I extract for CreateDate will be 2021-12-19T11:39:54.000Z instead of 2021-12-19T10:39:54.000Z.
This is a known issue? Do you think it is my devices which write some bad data?
Best regards.
The text was updated successfully, but these errors were encountered: