On 1/5/2016 5:20 PM, Chuck Norcutt wrote:
Is there a "standard" place where GPS data is supposed to reside in
the EXIF? Is the "standard" honored by all apps?
It appears you misunderstand how EXIF is designed. It's open-ended, just
a stack of lines with tag names* with their values. So yes, there are a
lot of standard entries, but anyone, from you to a camera maker, can put
in anything you like, as well, using an unused tag name.
To read an EXIF file, one goes through line by line, using and/or
converting to usual usage for display the ones you understand. From
there, some applications just ignore the rest, and some show them all,
with no interpretation. This latter is why there are so many mysterious
seeming entries in the Camera Maker section when viewed in something
like ExifToolGUI.
There are folks spending time trying to decipher this stuff. A great
deal of the understandable info in the Maker sections is a result of
such efforts.
Now, back to "standard place" My S100, with built-in GPS and Raw files,
put the GPS info in EXIF for the JPEGs and as separate .xmp (sidecar)
files. Both GeoSetter and LR, when used to add GPS data from track logs,
also add them in .xmp files. So there may be a "standard" to do that
with proprietary Raw formats, for fear of altering the originals in
correctly.
As to what is "honored" by all apps, it's sort of pot luck. FastStone,
for example, ignores .xmp EXIF, so location only shows for JPEGs, but
not for Raw files or PSDs, even though the data is there.
But really, ti all works pretty well for the main stuff we are
interested in.
Mysterious Entry Moose
* OK, there are section headers, too.