I'm in a bit of a fix here. I purchased a very capable GPS logger and some software that fit my needs to a 'T' to geotag all of my photos in Aperture, or so I thought.
It turns out that the file formatting for the CSV files that the logger generates are not of the usual structure, looking something like this:
INDEX,TAG,DATE,TIME,LATITUDE N/S,LONGITUDE E/W,HEIGHT,SPEED,HEADING,VOX
1 ,T,090802,143559,45.440078N,012.323685E,126 ,0 ,0 ,
2 ,T,090802,143600,45.440081N,012.323688E,122 ,0 ,0 ,
3 ,T,090802,143601,45.440086N,012.323691E,112 ,0 ,0 ,
4 ,T,090802,143602,45.440089N,012.323694E,107 ,0 ,0 ,
5 ,T,090802,143606,45.440106N,012.323706E,81 ,0 ,0 ,
6 ,T,090802,143607,45.440110N,012.323710E,76 ,0 ,0 ,
which all of the software I've been using to try to extract the data has had issues with.
Here's the full support conversation I've had with the software developer:
Differing Time Zones: What's the Fix? - Houdah Software Forums
As you can tell, he's had me try a number of conversion methods and it's come down to having to manually manipulate the csv files to read correctly. Who wants to do that with 10,000's of GPS points? Not I. The whole point of having this software is to automate geocoding the photos. At this point, I'm seriously considering asking for my money back.
I'm certainly not savvy enough to write my own script to edit each file, so that method is out. Anyone have any ideas on how to go about fixing these files, or even better, know of geocoding software or converters that are smart enough to handle these files?
Top
