Image Field And Image To Merge By Drupal 7

I'm at the Drupal and Multimedia session at DrupalCamp NYC 5 and they were briefly going over the modules that there are (a) there are a lot and (b) there's usually several ways to do something. One thing they pointed out was that by Drupal 7, the plan is for image module and imagefield module to merge. Great, this will cut down on redundancy and it will give site-builders a clear solution that will hopefully do everything they need it to do.

I also think that MAQUM should be migrated to imagefield and a lot of the metadata should be shoved into a CCK field.

Fixing HoudahGeo's City And State Reverse Geocoding

I've been looking into geotagging my photos and finally got around to purchasing a GPS logger. Initially, I just wanted a script to automate the merging of the latitude and longitude from the GPS log into each image's EXIF information, after which, I'd just import the images into Aperture as normal. But then I found out that even more useful would be to reverse geocode the images. This would mean the the IPTC fields for city, state and country would be automatically populated, saving me from the task of manually entering each in Aperture.

Well, HoudahGeo does it better and more elegantly than any other software out there. After downloading a demo and reading Brett Gross' write-up on Aperture and houdahGeo I was sold.

The one glitch is that HoudahGeo saves both the city and the state into the IPTC city field, separated by a comma and a space, e.g., Great River, New York. I sent an email to the developers and was told that the next version, 1.5, would have this fix. Until then, I've whipped up an Automator workflow with a bit of bash scripting that calls exiftool that splits the IPTC metadata properly and will work with cities and states with any characters, including spaces, but not commas. Here's the guts to the Split IPTC City And State Automator Script:

# This automator workflow is licensed under the GPL, v2
for f in "$@"
do
        CITYSTATE=`exiftool -City -s -s -s $f`
        CITY=${CITYSTATE%,*}
        STATE=${CITYSTATE#*, }
        exiftool -overwrite_original -City="$CITY" -Province-State="$STATE" $f
done

So my workflow is now:

1. Copy photos from memory card to temporary directory on my harddrive along with GPS log
2. Use HoudahGeo to tag each image with longitude, latitude and altitude, along with the city/state and country
3. Save the GPS log away in case I need it later
4. Run the Automator script on the images to fix the city/state issue (installing it as a Finder plugin is recommended)
5. Import the images into Aperture

Image (And File Handling) In Drupal 6 And Beyond

In the beginning (2002), there was Image, and everyone could create images as nodes and all was good, if a bit simplistic. (There was even IPTC and EXIF metadata support). After a little bit of time, you could even attach images to nodes. By 2006, images could be attached to nodes. (By now, Flexinode had been around for a while and CCK had been around for a bit, too.) CCK became the predominant way of creating content types, as opposed to writing a new module for each individual content type. ImageField, a CCK add-on, (released in July 2006) allowed images to be handled by CCK. This, combined with other CCK fields let you do all sorts of neat things like set up an online store with one field being the name of the object your are selling, another field being the description and another three or four fields for uploading images of the product. Or you could be an online newspaper and have anywhere from zero to several images per article. Each page (whether online store or newspaper) could be themed to layout the information appropriately with ImageCache creating derivative (read: resized and/or cropped) images.

Fast forward to 2008 and there's primarily two ways to get images in your Drupal site, with Lullabot's Image vs. ImageField and ImageCache being the definitive comparison between the two. If you were fine with images as nodes and had simple needs (gallery, photoblog, etc.) you probably went with (or continued using from back in 2002) Image. On the other hand, if you were creating tons of content types thanks to CCK, you probably jumped ship to ImageField.

Now, there's talk about merging Image with ImageField (and ImageCache), with a script to migrate from Image to ImageField. But it was also pointed out that one field to handle all uploaded files, images or not, should be the way to go and that this would be the end of ImageField. FileField, combined with FileField Image would handle everyone's imge handling needs (as well as other file types as well).

While some people think images need special handling (and they are right to a degree and FileField Image takes care of this) there is also the consideration that other file types need special handling, such as videos. Just like images have a need for derivative images, so do videos (original high resolution, low resolution, stored as a flash file and a thumbnail screencap to display in the page). Having one unified way of uploading files would mean less code to maintain and there might even be a reasonable chance of getting file (and potentially image) handling in core, the CCK way.

(For these reasons, I've decided to postpone a D6 release of MAQUM.)

¶ Free Application To Manually Geotag Your Photos In Aperture

¶ Frasier Spears Goes Into Detail On Using Keywords With Aperture

¶ Aperture 2 Handles Lens Metadata

¶ Adding TV Shows On DVD To iTunes