4 ms·
Specific to photos, and most commonly scanned photos is the problem of "approximate" or "uncertain" dates. The various blogs (exiftool forum &c) all discuss di
by ggm 5y ago
Specific to photos, and most commonly scanned photos is the problem of "approximate" or "uncertain" dates.
The various blogs (exiftool forum &c) all discuss different ways of coercing "probably 1952" or "before 1940 and after 1920" into the EXIF structure.
I'd love to hear of ways to leverage tags to do this. perhaps assign a specific date (the blogs often say 1952-01-01:01:02:03 as a datetime, to signal "uncertainty") could be improved on by an "uncertain" tag.
There's also the syntax of tag separation inside EXIF. The various systems can't entirely agree what notation to use.
- ogurechny 5y ago> 1952-01-01:01:02:03 as a datetime, to signal "uncertainty" I instantly thought that least significant fields are used to indicate uncertainty range (10 days around 1952-01-01, or 10 years around 1952?). After all, the older the photo, the less sure we can be about its timestamp (usually), so we can use even/odd seconds as a flag to indicate exact time or uncertain period length (log scale). It would be quite an evil hack of a common fixed timestamp format.
- ggm 5y agoThat's very clever. I thought about using alternate daytime fields to signal the degree of uncertainty as a magnitude to the declared date Time, which then becomes the centre. Or you can use some positive/negative signals to show not before or not after.
- mceachen 5y agoExifTool 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 on those values. I'd also really like a way to identify very-rough dating. A (custom?) tag could encode "precision", maybe with a time units, so a +/- 10 year "precision" would handle your "between 1920 and 1940" case. If you've got a suggestion, I'm interested: PhotoStructure has a ton of users with this same issue.
- ggm 5y agoI 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 agoAgreed 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!