How does PhotoStructure capture captured-at?
One of the most important pieces of metadata about a photo or video is when a given image or video was captured.
PhotoStructure has advanced heuristics to determine this “Captured-At” time.
What’s a “valid date,” according to PhotoStructure? #
Any date between 1826 (the first year a photograph was captured) and 2 days from now is considered a “valid date.”
If you have paintings or other imagery from before 1826, change the
Step 1: Look at EXIF metadata #
PhotoStructure first looks at IPTC, EXIF, and other metadata tags, stored both in the original file, and in sidecars, with these tag names:
SubSecDateTimeOriginal(fractional seconds for
DateTimeOriginal(date/time when original image was taken)
DateTimeDigitizedby the EXIF spec)
SubSecTimeDigitized(fractional seconds for
SubSecTime(fractional seconds for
The oldest “valid date” wins.
Step 2: Look for an ISO-compliant filename and path #
If we’ve got to this step, no EXIF, IPTC or other metadata tags encoded the captured-at time, so we have to resort to more fuzzy heuristics.
Several cameras and smartphones encode the date and time as the filename of the photo or video. If this is ISO compliant, fully-specified, and “valid date,” PhotoStructure will use this as the captured-at time.
Step 3: Look for a date-like filename and path #
If the filename encodes something that can be decoded as a datestamp, and that datestamp matches either the file’s “birthdate,” PhotoStructure will return that datestamp.
Step 4: Infer a date interval from siblings #
We look at “sibling” files in the same directory, with similar names and similar filestamps, that have captured-at times that were extracted via Step 1 or Step 2.
If we can find both an upper and lower bounding sibling, we set the capture-at time to be a date interval between these two files.
PhotoStructure has this (fairly exotic) heuristic for two reasons:
Video formats regularly omit EXIF or IPTC timestamps, and we don’t want to revert to filesystem times.
If you’ve used applications that strip metadata (say,
-copyoption), you may have inadvertently removed metadata. This “sibling inference” at least puts the image into the correct ballpark.
Step 5: Fuzzy date parsing #
At this point we’re scraping the bottom of the heuristics barrel.
If any containing directory of the file has a name that is, ideally, a valid
YYYY-MM-DD, we’ll return that as the captured-at day.
You can disable this step with the
fuzzyYearParsing configure strictness of this step.
Step 6: Use filesystem times #
PhotoStructure really tries to avoid using filesystem times, as it’s frequently incorrect.
Many backup and file synchronization applications don’t retain the source file’s filesystem times. The filesystem time frequently reflects when the file was first copied to that volume, rather than when the file was originally captured.
If you don’t want to import photos or videos that require this step, set the
setting to false.
What should I do with scanned photos? #
If your scanning software adds metadata with the incorrect datestamp (so PhotoStructure is using “Step 1”), you can clear the times with ExifTool, and then put these scanned images into a directories with the roughly-correct date (formatted as YYYY-MM-DD, or “August 1983” or “1983 AUG”). PhotoStructure will then resort to using Step 5 for the captured-at time.
The forum has some additional tips for handling scanned images.