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

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

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…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…