Proposal: new API call to fix-up malformed EXIF date/time strings
Added by Jim Nelson over 9 years ago
In Shotwell, we have code to correct bad EXIF date/time formats that certain manufacturers inject into their metadata. (The code can be seen here: http://redmine.yorba.org/projects/shotwell/repository/revisions/2857fb8d47ea9ac1484bc3b2a425a0a2ce313fd4/entry/src/MediaMetadata.vala, lines 94 - 103.)
It would make sense to offer this functionality to all users of Exiv2, otherwise this has to be reinvented for each project. A new call could be added that would fix up bogus strings and return them in the proper EXIF format. I don't believe such a thing exists in Exiv2 today, correct?
Replies (1)
RE: Proposal: new API call to fix-up malformed EXIF date/time strings - Added by Robin Mills over 9 years ago
Jim
This sounds like a good idea to me. I'm adding a new sample application "geotag" to read gpx (xml) files and write GPS tags. I originally wrote this in python 4 years ago. In converting to C++, I have discovered that my python code has a date format error when I write Exif.GPSInfo.GPSTimeStamp. And some of my photos (which have been geotagged by other applications) have different date format errors on the same tag. Grrrr. I agree - much better for the library to deal with this and be consistent (and hopefully correct).
However let's hear what Andreas has to say.
If Andreas is happy about this being added to the library, I'll undertake the task in time for the 0.24 version (which will be about Nov/Dec, I expect).