GNOME Bugzilla – Bug 627185
Incomplete EXIF GPS metadata
Last modified: 2012-03-02 04:25:33 UTC
Created attachment 168112 [details] the image properties eog-2.30.1-1.fc13.x86_64 The Longitude GPS information is not formatted at all in EOG, and the Latitude information is completely missing from the display, though gthumb will show it.
Test case image at: http://people.fedoraproject.org/~hadess/IMG_0002.JPG
The infos are there, but as "InteroperabilityIndex" and "InteroperabilityVersion", which IIRC is due to some conflicting tag ids here. Will look if I can find a workaround. Regarding the formatting: We don't do any formatting of the tags ourselves in the details view and rely on libexif for formatting. Maybe we should look into moving to exiv2 as well (bug 512265), although I think there were some caveats as well there.
(In reply to comment #2) > ... > moving to exiv2 as well (bug 512265), ... It's actually bug 515265.
If moving to exiv2 or gexiv2 is on the cards, and will fix my bug, I'd be happy either way. FWIW, gthumb handles this file just fine, so moving there might be the solution.
eog now specifically overrides libexif's formatting for some GPS tags: commit 3e4bc1aad5bf9236705bdb049ed017f374e27552 Author: Felix Riemann <> Date: Sun Jul 17 15:47:28 2011 +0200 Reformat Exif tags for GPS position to be better understandable libexif's formatting of these tags is not nice to read. Reformatted are latitude and longitude values and their reference points. https://bugzilla.gnome.org/show_bug.cgi?id=627185 commit 8574b4ba6e6211b5f1a7e1fade6e02da2b8703fd Author: Felix Riemann <> Date: Sun Jul 17 13:57:33 2011 +0200 Make sure GPS Exif tags are named and ordered correctly Some GPS tag IDs overlap with IDs from other IFDs. Specifically check for the GPS IFD and order the entries accordingly. Also respect the IFD when determining the tag's title. https://bugzilla.gnome.org/show_bug.cgi?id=627185 This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Still not fixed (version 3.2) see bug #671178