Inconsistent format of GPS Co-ordinates

Started by PandDLong, November 22, 2024, 07:00:40 AM

Previous topic - Next topic

PandDLong

I noticed that if I compare between created and shown GPS co-ordinates to test if they are the same, I get many "false negatives" - ie. they are the same but the comparison says they are different.

The problem seems to be that the formatting varies from photo to photo - sometimes there is a space between the minutes and seconds and sometimes there isn't.  Here is an example from the IPTC::EXT Location Created and Location Shown Latitude.  They are the same but a comparison using the variable functions will say they are different.



Perhaps this is an ExifTool issue?

A couple more examples showing the inconsistency.  No space for both and then one with both having a space.


My variables in VarToy were



As further testing, I found the same inconsistency with File.MD.GPSLatitude, File.MD.GPSLongitude, and the Location Created and Shown Longitudes. 
Interestingly in my quick review for any given image the adding of a space or not was consistent across all the GPS co-ordinates (but as per the initial example, may vary between Created and Shown/Dest).

The workaround is to only compare using the raw format.


A minor issue, with a workaround, but once I found it, wanted to share as FYI.


Michael

PS. I embedded the screenshots in the text but they disappeared on posting. And 'insert image' seems to only be for a weblink.  So I put them in the attachment list instead.

Mario

#1
The formatted coordinates come from ExifTool. IMatch uses only the raw/numerical (floating point) format.
Does your "comparison" use the formatted or numerical value? How to you compare what and where?
Always include sample images so we have the actual data to look at.

Note that the formatted values (degrees) are updated during write-back and the following reload of the metadata.

Not sure what the problem is with your embedding of images in the post. Works for me every time.
Don't just drag images from somewhere into your posts, this won't work. Attach the files, then click and use "insert".
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

PandDLong


Okay then, this is an inconsistency with ExifTool.  I was using the formatted values.  Will use the raw values from this point on.

This should be closed/archived for iMatch.

Thanks for the tip on how to insert images into the text.  In my original post, I did manage to attach the files but didn't realize the purpose of the 'insert' function (although the icon should have given me the clue I needed).

Tags I was using.

Screenshot 2024-11-21 220749.png

Inconsistency examples  

Screenshot 2024-11-21 220541.png

Screenshot 2024-11-21 220523.png

Screenshot 2024-11-21 220620.png


Michael




Mario

#3
You refer to the extra blank as inconsistency?
When does this happen?
Does the blank get added/removed when you write back?
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook

Mario

I think I've found a situation were the extra blank was potentially committed and fixed it.

That being said, this issue resolves itself after write-back, since IMatch writes decimal coordinates to ExifTool, and ExifTool then returns decimal and formatted coordinates when IMatch reloads the metadata after write-back.
-- Mario
IMatch Developer
Forum Administrator
http://www.photools.com  -  Contact & Support - Follow me on 𝕏 - Like photools.com on Facebook