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

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…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …