Is exiftool compatible to gpscorrelate?

Started by Archive, May 12, 2010, 08:54:21 AM

Previous topic - Next topic

Archive

[Originally posted by charliekk on 2008-05-30 12:22:28-07]

Hi,

is there a known issue/incompatibility when trying to use exiftool on JPEG's which have been geo-tagged using "gpscorrelate"? I'm unable to use such files as the source for "-TagsFromFile" operations.

Or even better: Is there an exiftool-based way to completely replace "gpscorrelate"?

Regards, Charlie

Archive

[Originally posted by exiftool on 2008-05-30 12:35:40-07]

Hi Charlie,

I can't help with your second question because I don't know what gpscorrelate
does, but i should be able to figure
out what is going wrong with your -tagsfromfile command if you
give me a few more details.  Please post your command and any errors
warnings (cut the text from your terminal session and paste here inside
Code:
...
), and a link to a sample image if possible.

- Phil

Archive

[Originally posted by charliekk on 2008-05-30 12:58:01-07]

"gpscorrelate" takes a list of position/timestamp pairs (provided as a .GPX-file created for example by some GPS logger device) and a JPEG as input and uses the JPEG/EXIF "DateTimeOriginal" to find the right geographic location in the GPX. Then it adds the right GPS data into the JPEG. Really nice...

Right now when I ran a test to provide you the info you asked for, I saw that the destination file WAS updated, but with error messages:

Code:
exiftool -TagsFromFile DSC_2156.JPG x.JPG
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
Use of uninitialized value in numeric eq (==) at /usr/lib/perl5/site_perl/5.8.8/Image/ExifTool/Nikon.pm line 3848, <EXIFTOOL_FILE> chunk 2.
    1 image files updated

The source file DSC_2156.JPG is an out-of-the-cam JPEG processed with gpscorrelate". I uploaded it to rapidshare (uahhh!!), as I have no better way to share it:-)

http://rapidshare.com/files/118826178/DSC_2156.JPG.html" target="_blank">http://rapidshare.com/files/118826178/DSC_2156.JPG.html

Archive

[Originally posted by exiftool on 2008-05-30 13:04:29-07]

Try updating to the latest version.  I think you are seeing the result
of a bug that was fixed by version 7.28.

- Phil

Archive

[Originally posted by charliekk on 2008-05-30 13:13:23-07]

I did upgrade from 7.25 to 7.29 and magically it works now:-)

Thank you very much!!

Archive

[Originally posted by exiftool on 2008-05-30 13:16:06-07]

And I forgot to answer your other question:  ExifTool by itself will not
reqd a GPX track log, so alone it can't replace gpscorrelate, but there
are a couple of utilities linked from the exiftool home page that
will do this using exiftool as the engine to write the image.

- Phil

Archive

[Originally posted by charliekk on 2008-05-30 13:19:28-07]

Yes, I see, "gpsPhoto" seems to do the trick. I will try to use this, it might avoid confusion caused by the different backend engine in gpscorrelate.

Archive

[Originally posted by exiftool on 2008-05-30 13:23:43-07]

Great.  I just checked and it was version 7.26 that solved the Nikon problem,
not 7.28.   Sorry for any inconvenience.  I plan to release a new production
version soon to address the important bug fixes like this that were made
since the last production release (7.25).

- Phil