I’m releasing the updated module for Gallery2 under the name of GalleryTweet. It was prompted by a few people mentioning they couldn’t get my earlier hack to work – so I thought I’d build something that was (slightly) more robust, and might stand to work on installations other than my own.

You might want to skip my ramblings and jump straight to the download, so here’s a link for you folks:

• Download GalleryTweet module
  

1. Install by unzipping to the root of your Gallery2 installation, and activate through the plugins panel.
   
2. Once logged in, edit your Twitter settings through the left navigation
   
3. You should enter your twitter username / password, and the format you’d like to send your Tweets out with.
   
4. Now while you’re browsing the Gallery, Tweet about any images using the link below the thumbnail

Please drop me a message on Twitter @kevinblake if you’ve found the plugin useful, can’t get it work, or have any other feedback.  That download link again, in case you missed it the first time:

• Download GalleryTweet module

Happy Tweeting!

This post is no longer being maintained due to budget constraints - please check the project page for the latest information: http://codex.gallery2.org/Gallery2:Modules:gallerytweet

The Hudson River picture wouldn’t have been possible without the non-affiliated TwitPic – which never truly got the recognition it deserved.  Without it, the infamous picture would have only been a 140 character description, and nobody will have noticed or cared.  Still, that’s the nature of buzzwords I guess.  If they don’t cause a buzz, they’re just words.

Anyway, TwitPic is yet another disparate service like Flickr, Panoramio or Facebook that’s had me tempted away from uploading some of my photos to Gallery2 / Blakepics.  With Facebook, I’ve integrated my own application there; Panoramio and Flickr, stolen the best parts of each.

And now with a hack to the tagging module in Gallery 2 I can emulate all I want from TwitPic as well, and tuck another service onto the shelf at the back at the cupboard.  So as usual, I thought I’d share.

What it is…

• Tweet any photos on Gallery just by adding the tag ‘twitter’ to your photo.
• Automatically takes the photos title as your Tweet text.
• Processes all URLs through TinyURL, giving you a warm and fuzzy Tiny URL

What it isn’t…

• A seamless Gallery2 module.  There’s some hacking to do.
• Multi-user.  If you share your Gallery, there’s some more work to do.

If you make improvements in these areas or any others – please let me know

Requirements

• Gallery 2
• Tagging module
• Twitter account

Things you need to do

1. Download my Twitter Tags class
2. Unzip to the root of your Gallery installation
3. Edit /modules/tags/classes/TwitterTag.class with your twitter username/pass, and Gallery URL.
4. Edit /modules/tags/classes/TagsHelper.class
   1. Add this just above the line ‘class TagsHelper’
      GalleryCoreApi::requireOnce('modules/tags/classes/TwitterTag.class');
   2. Then just above
      return TagsHelper::assignTagById($itemId, $tagId);
      Add
      TwitterTag::Tweet($itemId, $tagId);
5. Tag any photos you want to appear on Twitter with ‘twitter’.

Fortunately, BBC News have now deemed New Years Resolutions to be bad for your health.  So like bread, second-hand smoke, guilt and vitamins, I’ve given them up.

But I thought to myself, “I’ve been captioning loads of photos every week”.  I did.  “I bet it’s the rest of those free-loaders not pulling their weight”.  So I’ve given the Caption Status page on Blakepics a much-needed overhaul.  If you’re logged in, you’ll now see how you’re doing with captioning your own photos – and even if you’re not, you can see a member list with how many photos everyone’s captioned, as well as click-through to a list of them all.

Turns out I was wrong.  A lot of those free-loaders are doing a better job than me.  In fact, whilst 25.01% of total photos are captioned – 25.04% of my own photos are captioned.  Since most of them on there are mine, I guess I shouldn’t be surprised.

So it seems as though I can’t prove everything with statistics.  Not if that something is how successful my 2008 Resolution has been.

Happy New Year Everyone!

Automatically add geonames.org tags to Gallery

As always, an imminent holiday has inspired me to update the entire system behind geotagging my photos.  Likewise, needing to plan said holiday has given me the opportunity to procrastinate and do something else instead.

Wishlist

• A repository I can drop files created by the Genie BGT-31 GPS tracker.
• Automatically convert the tracks into GPX format.
• Automatically stamp any photos within Blakepics with their longitude / latitude values into the EXIF information.
• Use that EXIF information to populate the database for the Gallery2 maps module.
• Use geonames to get some basic tags, and automatically add those to the tags database.

I can happily report all of the above is happily running on a schedule on the Blakepics server.   Whilst I realise a lot of these options aren’t particularly available on a shared hosting server, I’m going to talk about them anyway.

A small disclaimer

Be under no illusion, a lot of these scripts are hacked together with no thought given to scalability, stability, or re-use.  They’d be a lot better off as a proper Gallery2 module to be honest – and hopefully someone will beat me to it in making that a reality.  However, for the time being – this is all provided as-is

NMEA repository

The repository is quite simple with an SFTP server running (sshd for example), and FileZilla on the client

Convert the tracks to GPX

1. Install the rather excellent gpsbabel.
   yum install gpsbabel
2. Run this convert-to-gpx.pl.txt perl script to combine all your nmea tracks to create a single gpx file.

Stamp the photos

1. Get the gpsPhoto perl script.  You might find you need to install some perl modules:
   perl -eshell -MCPAN
install modulename
2. Use this geocode-photos.pl.txt script to find any matching photos from your Gallery, and tag them.  Note that I limit them to only photos I’ve uploaded myself, as I don’t want to go messing around with other peoples (and they were probably not at the same location anyway)

Fill the Gallery2 maps module with the EXIF data

There’s a maintenance task to use the EXIF data to power the maps module of Gallery2, so using Roel Broersma’s excellent script to run the maintenance tasks, these can be scheduled with the extra line:

wget --quiet --output-document=/dev/null --cookies=on --load-cookies $TMP_PATH/myg2cookies "$G2_URL/main.php?g2_controller=core.AdminMaintenance&g2_form%5Baction%5D%5BrunTask%5D=1&g2_taskId=PopulateGPSEXIFInfos&g2_authToken=$AUTHTOKEN"

Give some meaning to your location data with geonames

Geonames provides a reverse-lookup to get some more human readable descriptions of your photos.  So I use this to put in the country, region and town data into my Gallery.  You can go a bit further and get details of nearby landmarks from Wikipedia to add if you like, but i don’t find it too useful for my purposes.

1. You’ll need some more perl modules
   perl -eshell -MCPAN
install Image::ExifTool;
install Image::ExifTool::Location;
install Geo::GeoNames;
install Data::Dumper;
2. Get my write-geoname-tags.pl.txt perl script, which is actually a combination of all the previous scripts.  This will query the web service, and update your tags.

It all sounds very complicated…

Well, yes.  My aim isn’t to create the easiest system to set-up, it’s to create the easiest system to use.  Uploading a single NMEA track list now causes all of the above to happen automatically.  That said, I recognise that it’s not for the faint-hearted.

So why not try one of these easier solutions:

• GPS Babel GUI (Windows / Linux command-line tools available)
• GPicSync (Linux / Windows)
• GPS Correlate (Linux only)
• Flickr (all)

What next?

Add all of these scripts mentioned above to a cron task, and forget all about it.  You can probably combine the whole lot into a single job (I wanted to keep them separate, so some could be run nightly, and others weekly or monthly).

Hopefully this is the humble beginnings of a more efficient and elegant solution.  For now I’m at least getting a lot more data into and out of my photos

Do let me know if you make any improvements, or have any ideas for viable new features – I’d be interested to hear from you.

Anyway, I’ve written another of those Gallery2 modules to show some stats on how the 2008 captioning is going. It’s more for my own curiosity and to stop me copying huge reams of SQL into Query Browser. But you never know, you might look at it and say “oh” as well. So, if that sounds like fun you can click Caption Status either here or on the Blakepics left nav.

It’s become a bit of a theme this year, and after my last posts on the subject – we got to talking about captioning photos. Many of my photos exist on the basis of seeing something shiny, and then taking a picture. I often have no idea what said shiny thing was – but quite often make the effort usually on Google, or Rough Guides to discover its secrets afterwards.

I encourage any account holders to tag as many photos as they want on Blakepics. But mine is a very small community, and Flickr shadows it with even its tiniest fingernail. So, why should you have to tag your own photos? Aren’t there plenty of other people out there that would do that for you?

And I got thinking about the recaptcha project. They use scans of words to present the user with captchas that will help their digitization of old texts. These “unknowns” are combined with”known” text, and the answers compared against previous users results.

So, why not the same for photos? A known photo could be presented to the user “Dog”, “Cat”, “Llama”, or even a traditional captcha. Combine that with an unknown photo, and invite users to give it a caption. According to recaptcha, there are 60 million captchas being solved every day – it’s about time we put all that to good use.

Or perhaps CAPTCHA might just become another word for blackmail. Sure, you can login to your account – but you have to do something for me first. I just like the way Captchaner, sounds (Captcha, Captioner – see what I did there?). Maybe one day we’ll see this on all of our logins.

So, first step – Gallery2 has an AddViaEmail module. Install that, signup for a Google Mail account and get yourself a really obscure email address. Once you’ve got the AddViaEmail installed and configured (yep, it supports Google’s SSL pop3 servers), you can send emails to that address and have them automagically added to a specific album on your Gallery2 server.

You could stop here if you like – most mobile phones come with email software nowadays. So you can write an email, attach your images, and off they go. But I find email on the little keypads really annoying. And there’s all that typing, clicking, and making sure you get things right to worry about. You’re not exactly cutting edge, with email … are you? Besides, we’ve only made use of three different vaguely related services. That’s not what the web of the future is all about. I’ve heard about it in fairy tales.

So, get yourself a Shozu account. They provide a really cool backup / Share-It service and comes complete with a Symbian application which you can install on your brand new ultra-shiny Nokia N95. For example. If you use this, you can get yourself some single-click access to uploading your photos. Actually, it’s a 3-click minimum. But it’s better than typing email addresses or searching for contacts. They provide a bunch of other ways of sharing your photos, such as uploading to the BBC for consideration as part of their stories. Or more usefully to a WordPress blog or Facebook to humiliate your mates before they’ve got home from the pub and had a chance to de-tag all your new compromising photos.

But alas, AddViaEmail and Shozu don’t play very nicely. So, here are some changes to make to your php script (don’t be scared, it won’t bite).

/modules/addviaemail/classes/AddViaEmailHelper.class – Fix problems with the mime type…
list ($ret, $item) = GalleryCoreApi::addItemToAlbum($pathToSaveFile . $filename,$filename, $filename, $summary, '', $mimeType, $targetDestination);
->
list ($ret, $item) = GalleryCoreApi::addItemToAlbum($pathToSaveFile . $filename,$filename, $filename, $summary, '', 'image/jpeg', $targetDestination);
You’ll also need to disable the subject line spam checker as Shozu will send your email with the subject line as the name of the image.

So just remove this:

$header_info->subject == $subjectToMatch &&

The spam checker is actually quite a cool function, so one of these days I’ll come back an regular expression that. But quite likely, I probably won’t post it here. So work it out for yourself

See, and that’s all there is to it. I can now upload loads of photos direct through my phone (as I did with the image at the top of the page), and you could too.

Why?

I have thousands of photos on Blakepics, and Facebook comes along and wants me to upload them all over again. Well, sure, I can do that – or, it makes a lot more sense to combine the power of the two systems.

What?

Wanting to keep this initial trial run extremely simple – I’ve gone for just adding a link below my profile picture. That way I can keep very clear of the Gallery API for the time being effectively reducing my problems by half

How?

1. User adds the Blakepics application on Facebook
2. Setting the Callback URL on Facebook, a request is made to Blakepics.com
3. Blakepics.com makes use of the Facebook API to check the currently logged in user
   // the facebook client library
include_once('../modules/facebooktaggedalbums/api/client/facebook.php');
include_once('../modules/facebooktaggedalbums/api/client/facebookapi_php5_restlib.php');
// some basic library functions
include_once('../modules/facebooktaggedalbums/api/lib.php');
// this defines some of your basic setup
include_once('../modules/facebooktaggedalbums/api/config.php');
$facebook = new Facebook($api_key, $secret);
$facebook->require_frame();
$user = $facebook->require_login();

4. Using this user ID, Blakepics requests the first and last name of that user from Facebook
   $user_info = $facebook->api_client->users_getInfo ($user, 'first_name,last_name');

5. Generate a URL that links to the tagged album, e.g. http://www.blakepics.com/key/kevin+blake. Using the rather cool FBML (FaceBook Markup Language), the link can be sent to Facebook with the instruction that this should be applied as a profile action (fb:profile-action).
   $fbml="<fb:profile-action url=\"http://www.blakepics.com/key/" . $user_info[0]['first_name'] . "+".$user_info[0]['last_name']."\">View more Photos of me at Blakepics</fb:profile-action>";
$facebook->api_client->profile_setFBML($fbml, $user);

6. And display a message back to the user, to let them know what’s happened
   print "Blakepics profile link has been added";


And that’s it really. Obviously there’s a lot more that can be done, but the simple application works and is on its way to approval from the Facebook team. All being well, you should be able to add your own links to tagged albums very shortly.

We’ve always had keywords, the meta content for your pages to help search engines out in finding your content. But that just doesn’t cut it any more. Nowadays you have be tagged or labelled, dynamic, geographically aware, mash-up your own content with a multitude of other sites, bleed ajax from your eyeballs, stay mobile, accessible, interactive, and generally ensure that no two-visits to your site are ever exactly the same. If you’re not achieving that quite frankly – you’re terribly 1.0, and I’m afraid – nobody.

So imagine my excitement when I heard the news that Gallery the leviathan behind Blakepics was going to be making more use of the beloved photo keywords, not just for search – but in a Flick-esque, semantic, ever-evolving keyword extravaganza. If this was excitement, then I was feeling it. After a long wait, and drooling over alphas, betas and release candidates – the dream has been made a reality, and the wait is finally over.

So, I now have the ability to supplement my standard albums with dynamic ones. Photos of Christmas in London can now be a part of both the Christmas and London “albums”. Dynamic albums showing off all the llamas, no matter where I saw them, or holidays, europe, america, mobile phone pictures. This has also introduced the keyword “cloud” at the bottom of every page, which not only gives a way of seeing the albums, but which keywords are the most popular.

It’s not the only addition / improvement of course – but it’s one I’ve been looking forward to for a very long time

In fact, it’s far less sinister than all of that, to track my holidays, places I’ve been, and more importantly – the photos I take whilst I’m there. Geotagging, or geocoding has received quite a lot of press lately, since Flickr have introduced it into their service.

I took the Track Stick into London at the weekend, for a trial run before Croatia later this month. The concept is quite simple. The GPS device records your co-ordinates alongside the time and date. The camera records the time and date when you took the photo. Once you’re back home on your PC, you can use these two pieces of information to automatically add co-ordinates into each of your photos’ EXIF headers (metadata). From there, it gets really fun

• View your photos on a map like Google Earth.
• Search for your photos based on location.
• Find other photos that were taken in a similar area.
• Automatically create descriptions of your photos based on how other people describe theirs of the same place.
• Use all of those photos to construct 3D models of your holiday.

Okay, the technology isn’t all there, yet. But the important thing is to start gathering this data and to certainly make what use of it you can. So, that’s what I’ve done

How to tag your photos

1. You’re going to need a GPX track file, like the one here. The bare minimum you need is the latitude, longitude and date/time. Sadly, my Track Stick won’t output this by default. So I had to create a small script to make one from the CSV format it does supply. If you’re in a similar position, you can download my quick hacked together perl script to create your own. I may improve on this in the future, but for now it works.
2. Secondly, I used a small application called WMMX Location Stamper.
3. Click on Photos -> Add Photos, and select all the photos you want to tag.
4. Click on Tracks -> Add Tracks…, and load the file you’ve created as above (or obtained elsewhere if you’re not using a Track Stick).
5. Click the Apply Tracks button on the bottom, and you’re done – geotagged photos.

Viewing your photos in Google Earth

Using Picasa2, you can save your photos in a Google Earth file and share your entire journey with your friends and family.

1. Just load your photos into Picasa2 (File -> Add folder to Picasa)
2. Select the photos you have just added
3. Click Tools -> GeoTag -> Export to Google Earth
4. Select a location, where you want to save your file.

• If you’ve got a copy of Google Earth, you can view the pictures I took in London (Right-click, Save As…)

Gallery2 / Blakepics

Finally, all of these photos can tie into Gallery2 (which is what I’ll be doing) using the existing Google Maps Module, or watch this space on Tadek’s blog, for a really promising looking module to view locations on single images.

Useful Resources

I came across a number of other useful little applications out there, which while weren’t directly useful to me – might be very helpful to you, so here they are

• WMMX Location Stamper – Stamp your photos with GPS information. Totally Free.
• Google Earth – The best way to view your photos afterwards
• Grazer - Another GPS stamping application
• GPS Visualizer – A great online tool to sort our your GPX files, and much more.
• Photo Studio – John Hawkins’ explanation of geotagging with Photo Studio.
• GPS Babel – Converts your GPS track files between loads of different formats (though wouldn’t play nicely with the track stick – let me know if you have more luck!)
• Robo Geo – nice tagging tool, but it’s a pay-for software and doesn’t really do the job any better than the rest of them.