O
OriTester1
Guest
Can someone please explain the logic behind the Date Taken property shown in Windows Explorers Properties dialog?
Tests show that the value displayed is that of the DateTimeOriginal EXIF property, or failing that, the DateTimeDigitised EXIF property. However, it isnt as simple as that. Take the following image for example. It has the two EXIF properties mentioned above and yet no Date Taken value is shown:
If I write a small amount of code to load that image into memory, then save it without making any changes, the Date Taken property is then displayed correctly!
Code:
loadedImage = Image.FromFile(tbFile.Text);
loadedImage.Save(tbFile.Text + ".jpg", ImageFormat.Jpeg);
Saved image:
Note that the image in the first screenshot has the EXIF Data written in Little-endian order (Intel) while the images written by .Net have Big-endian order (Motorola), but further tests have shown that the byte order makes no difference.
Continue reading...
Tests show that the value displayed is that of the DateTimeOriginal EXIF property, or failing that, the DateTimeDigitised EXIF property. However, it isnt as simple as that. Take the following image for example. It has the two EXIF properties mentioned above and yet no Date Taken value is shown:
![4fc7cea0359b39821f1cc5f39e0bf08a._.png](/proxy.php?image=http%3A%2F%2Ftest.computerhelp.forum%2Fdata%2FMetaMirrorCache%2F4fc7cea0359b39821f1cc5f39e0bf08a._.png&hash=e1cd688b211e4ff1468ba0a41bcffdaf)
If I write a small amount of code to load that image into memory, then save it without making any changes, the Date Taken property is then displayed correctly!
Code:
loadedImage = Image.FromFile(tbFile.Text);
loadedImage.Save(tbFile.Text + ".jpg", ImageFormat.Jpeg);
Saved image:
![d7809ed46699b54ae757149b2c7e0f42._.png](/proxy.php?image=http%3A%2F%2Ftest.computerhelp.forum%2Fdata%2FMetaMirrorCache%2Fd7809ed46699b54ae757149b2c7e0f42._.png&hash=232a8bb4fba56243a17d0bb7832f1bca)
Note that the image in the first screenshot has the EXIF Data written in Little-endian order (Intel) while the images written by .Net have Big-endian order (Motorola), but further tests have shown that the byte order makes no difference.
Continue reading...