3 ms·
Don't dogmatically choose either. I had one case where it made sense not to use UTC but was hard to get across to those who were stuck on ALWAYS. The case was f
by karmakaze 7y ago
Don't dogmatically choose either. I had one case where it made sense not to use UTC but was hard to get across to those who were stuck on ALWAYS. The case was for photos taken around the world on a photo site. Each photo effectively has a place and time at that place. Storing UTC would have shown NYE midnight pictures at an arbitrary hour based on viewers tz.
- koyote 7y agoI'd argue that in that case you store two values: 1. The time the photo was taken in UTC (as usual). 2. The UTC offset for the photo location.
- mceachen 7y agoI banged my head on this several times until I came up with basically the same conclusion. PhotoStructure stores both the raw EXIF value, a nullable timezone that tries to adopt sibling's timezones (normally only inferable when you have GPS tags, including GPS acquisition time, which is always in UTC). It also stores the source of the inference, so other heuristics know how much it can "trust" that value. I open-sourced the GPS location and offset inference code: https://github.com/photostructure/exiftool-vendored.js https://github.com/photostructure/exiftool-vendored.js
- karmakaze 7y agoOthers before tried just that. Photo métadata is notoriously inconsistent and incomplete. You're much more likely to have accurate local time and not much else.