Open davidebbo opened 3 years ago
I encountered the same problem. My images are extracted from video footage and this means milliseconds are important.
For my purposes, I had to parse the actual millisecond value; add a flag to ExifDateTime
specifying if the loaded timestamp had milliseconds, allow property collection Set()
to specify if milliseconds are to be written and finally supply the actual byte data with the millisecond part if present/needed (https://github.com/RudyTheDev/exiflibrary/commit/4d87cf05b9d6eccd1fe6ddfc68775b9a610ecbb9).
I haven't added any tests.
I understand that this doesn't follow the EXIF spec, but that's the only way to work with sub-second values with stuff like Mapillary.
I just found there is SubSecTimeXxx in EXIF spec for fractional seconds. The issue though is that the source software does not use this, nor does the target software.
I have a jpg with a creation time that has a partial second: "2016:07:31 10:10:20.291".
This causes it to blow up when parsing the date:
The image is personal, so I'll share it separately via email.