Main Menu

approximate date ?

Started by oliver42, February 05, 2018, 06:27:32 AM

Previous topic - Next topic

oliver42

If you use a modern camera, it will write the current date into the exif-portion of the image.

However: if you have digital images scanned from analog pictures, you often do not know the exact date of creation.

I really don't like to put 01.01.1970 on all the images that were taken in the year 1970.

Are there any ideas how to specify an approximate date or a possible range for the date ?

Phil Harvey

See FAQ 5.  As well, technically it is allowed, although not recommended, to leave EXIF date/time fields blank (filled with spaces).  To do this you must add the -n option when writing with ExifTool.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

StarGeek

Quote from: Phil Harvey on February 05, 2018, 07:47:09 AM
As well, technically it is allowed, although not recommended, to leave EXIF date/time fields blank (filled with spaces).

Ah, so it's supposed to be something like "2018:02:05 __:__:__" (using underscores as place holders)?  I've been using just "2018:02:05" (truncated) in my exif timestamps where I don't know the exact time.  I'll have to go back and retest some programs, though I don't expect them to read this format either.

@oliver42, I also don't like the inaccuracy in using the lowest possible number as a place holder for unknown values.  While the XMP tags can hold partial dates, very few programs will use them and read them properly.

One thing I have seen done is putting partial timestamps in keywords.  That does allow for searching for files in photo  management programs. 
* Did you read FAQ #3 and use the command listed there?
* Please use the Code button for exiftool code/output.
 
* Please include your OS, Exiftool version, and type of file you're processing (MP4, JPG, etc).

Phil Harvey

Quote from: StarGeek on February 05, 2018, 11:46:27 AM
Ah, so it's supposed to be something like "2018:02:05 __:__:__"

Yes, this is what I meant.  But re-reading the EXIF spec, maybe I should have said "technically it is possible" instead of "technically it is allowed", because the spec seems to imply an all-or-nothing for the spaces:

The date and time of image creation. In this standard it is the date and time the file was changed. The format is "YYYY:MM:DD HH:MM:SS" with time shown in 24-hour format, and the date and time separated by one blank character [20.H]. When the date and time are unknown, all the character spaces except colons (":") should be filled with blank characters, or else the Interoperability field should be filled with blank characters. The character string length is 20 Bytes including NULL for termination. When the field is left blank, it is treated as unknown.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

StarGeek

Well, to heck with it then.  I'm just going to keep on with my partials.  It may not work well with my DAM, but it makes me happy :D
* Did you read FAQ #3 and use the command listed there?
* Please use the Code button for exiftool code/output.
 
* Please include your OS, Exiftool version, and type of file you're processing (MP4, JPG, etc).

oliver42

So that means, that tools like Adobe Lightroom are not able to interpret the blanks in the date string ?