4 ms·

ExifTool handles zeroes in datetime strings (I had to add that support to PhotoStructure a couple months ago!), but I suspect most other applications will croak

• ggm 5y ago
  I prefer the custom tag approach, remembering that precision may go to day or month or year independently: I may know its easter, but not which year the wedding is, if you follow my reasoning, or know its 1932, but not which day of which month. That said, in month digits you have 13-99 and in day digits you have 32-99 as well as 00 in each field. So if you find yourself wanting to overload a field, there is one special value in each of month and day to flag one thing, and then 6 bits in each other field than year, to signal specific things. Could be 1 bit for +/- and then 32 values of imprecision, which means you can express uncertainty within a year completely, relative to any date. The standards guy in me says "please don't overload fields" here's http://www.loc.gov/standards/datetime/ http://www.loc.gov/standards/datetime/ and a community discussion I found when I looked at this https://www.photools.com/community/index.php?topic=517.0 https://www.photools.com/community/index.php?topic=517.0
  • mceachen 5y ago
    Agreed with not overloading fields: that way leads to madness. I really like the LOC standard: it follows already-used conventions for inexact dates. Thanks for the pointer!