So, I went on my first GPS adventure after work tonight. I was talking to Roland about doing something for BarCamp Vancouver 2007, and he reminded me that Cyprien had a Bluetooth receiver to borrow. So, we swung by Cyprien's place and I was off to see if I could find the pieces to make this work. Thanks, Cyprien!
I specifically posted earlier about a simple GPS logging device instead of a Bluetooth receiver. Bluetooth receivers allow you to hook up a PDA or your laptop and do various "on the go" GPS activities, usually involving directions and maps. But, I'm looking for something dead simple that a) just works and b) doesn't mean fiddling with / charging / carrying a bunch of other devices.
Cyprien's device is aTomTom Bluetooth receiver and I have a Nokia E61. Next step was to find some logging software -- the Position, Navigator, and Landmark applications on the E61 do communicate easily with Bluetooth receivers...but they don't really do anything. Including logging out of the box seems like a no brainer. In any case, I had already done some research on GPS related applications for Series 60, with the listing of GPS apps at All About Symbian being the most useful.
GETrack ended up being the simplest application specifically for logging. There are other apps that also do some map integration and so on, but GETrack is optimized for capturing tracks, storing them on your smartphone, and then exporting it to a variety of formats and sending them to your laptop. Perfect. You can get a trial download that logs 50 waypoints from Handango, and you can also buy it for about $14 from there.
So, after downloading and installing GETrack and making it sure it could communicate with the TomTom, I grabbed my camera and went for a walk. The TomTom receiver just has a single button and a flashing green light, and it slipped easily into the pocket of my shorts, after which I ignored it. I found myself spending more time fiddling with the software, trying to make sure it was working, figuring out how often I should log (I set it to 10 seconds, but even that might be overkill while walking), and of course watching to make sure I didn't go over 50 waypoints. All while trying to remember to take some pictures that I could geotag later :P
Once I got things settled I put the E61 in my other pocket and just walked. I ended up with three tracks, each maxed out at 50 waypoints for the trial version of GETrack. Once back at home, I sent the tracks in GPX format (you can choose from several formats, including KML for direct display on Google Maps), and then used GPS Photo Linker to load in the tracks, and then loaded in the photos I took. This would be the exact same step to import tracks from a simple GPS logger, the tricky part being that unlike Bluetooth, the interfaces aren't standardized, so you need to find the software to get the tracks off.
Finally, here is my GPS adventure walk on my Flickr map. For starters, I should have perhaps taken more photos. Secondly, I messed up the time codes on my first batch. In essence, the time codes are the most important thing. The best way to make sure you're getting it right is to take a picture close to the beginning of your logging, and another one right at the end. Then, look at the time offsets in GPS Photo Linker and adjust the timezone offset until the GPX track timestamps match up with your first / last photos. This doesn't have to be exact, but it should be close.
I manually fiddled with the last batch, matching up track waypoints with photos, and got great results. A good example is this shot of Death By Chocolate, where the hybrid map mode let's you see that the distinct roof matches the photo I took.
All in all a pretty good experience, but having to research, install, and then get the software working, plus the potential for difficulties in getting the Bluetooth receiver talking to your logging device (most Series 60 phones should work with GETalk) confirms for me that I just want a GPS logger :P
The nice thing for photowalks and other group events, is that only one person needs to be carrying a logger. Sharing the tracks afterwards will allow anyone to easily geotag their photos.
Lastly, GPS Visualizer and Everytrail are two sites I've found where you can upload GPX tracks directly and see them on a map. I'm sure there are others. Whew. That was a complicated tech exercise for such a short adventure :P
Comments
Nice it worked out for you in the end
but I agree that sometimes all the gadgets and communication between them can be bit distracting from the real activity; taking photographs in this case.
I can't wait until devices have built in GPS by default.
You story reminded me that I have several times used my Garming Forerunner while on sightseeing tours and taking photographs. It never occured to me that I could combine the logged data from the Forerunner with the time codes from the photographs to geotag them automatically.
Will do that this weekend :-)
Python for S60 apps
Although I don't own a GPS receiver myself, I know that there are various GPS related Python for S60 applications that might be very useful and hackable to boot.
ha, that's pretty
ha, that's pretty cool--sounds like a lot of work getting it all going, but very geogeeky!
Steve's been playing with GPS/Photos as well...
Steve's been preparing for his New Zealand adventure by playing with GPS/Photo logging as well. Check out his "Maps" section where he's got three maps currently, and will undoubtedly add more.
Yeah, I remembered that
Yeah, I remembered that as I was typing this up. He's definitely been doing the orienteering / logging for quite some time.
BUT
Those maps are all sorta-manually generated and pasted in as HTML pages on the webserver. I'll only do it if it's dead simple. Both the Google My Maps app as well as Flickr itself does this pretty nicely already, and I bet one of those Everytrail websites have a widget you can embed easily into web pages.
And if not, I guess I'll build a module :P
What I Use...
Yup, what I use is dead easy.
It's called RoboGeo (http://www.robogeo.com/home/) if you want to check it out. The only thing I do 'manually', which I don't really have to if I set it up right, is upload my file to the server. I do it this way because then they are my maps, not a generic, non-controllable boxed map. I can have a lot more control over it if I really want to, or I can just let the software do what it want. Of course, there's no doubt that now that I actually bought the software, there will be a 'free' version that's just as easy to use, but for now, as far as full-featured solutions go, I think I made the right decision.
S.