Skip to main content

EXIF Writing in Python

How much does it suck to transfer a few hundred photos from your camera, only to afterwards notice the date on the camera was wrong? So, here I go looking for an EXIF batch updating program, and the pickings are much slimmer than I would expect. Of course, writing my own seems like a pretty viable option and the EXIF.py module would be grand to apply here, save for one problem: It was written in 2002 and it still doesn't write back to the image.

What's a dad with hundreds of family photos to do? Fix it. Talked with someone else interested in this and came up with three options to move forward.
  1. Replace the entire module with a ctypes wrapping over the libexif library.
  2. Jam EXIF writing into the existing module by invoking the exif command-line utility.
  3. Reverse engineer the EXIF format from the modules parsing functions and properly implement writing into the library.
Cross-platform support is great, but I'm having a crappy time trying to cross-compile the exif utility to windows, I can't find binaries for it, and that is some sand in my pants. Then again, I really wouldn't use it on Windows, so I can defer the search for the command line utility on Windows until later. For ease of implementation, this will probably be the route taken. I'll post the results here later, but I probably won't send patches to the maintainer, because the methods I'll use won't match well there. The current library isn't really designed well for this, so I think a redesign would be needed to do it in a really good way.

If anyone knows that this is futile and a solution already exists, please let me know.


Comments

Cat said…
Take a look at this:

http://www.sno.phy.queensu.ca/~phil/exiftool/

It's not in Python but it might be just good enough to get the job done.
Michael Urman said…
Did you try the cheeseshop? Pexif 0.8 looks likely to be useful.
Chris Lambacher said…
Here are some options that work on Linux, not sure about cross platform.

Exiv2 claims to have been born because of the exact problem you want to solve.
http://www.exiv2.org/

I have used jhead before to extract info, but it also claims to be able to "relative adjust" timestamps.
http://www.sentex.net/~mwandel/jhead/
Anonymous said…
Hmm, you sure its that good?

Ibiza
mzt said…
https://pypi.python.org/pypi/piexif

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…