Google Maps GPSCoordinates Decimal Places

Started by gheppell, September 23, 2025, 11:34:35 PM

Previous topic - Next topic

gheppell

Hello.

I have provided imatch with my Google Maps API, such that I can geotag my files, old videos in particular.  

I have noticed that when geotagging, more often than not, the coordinates returned are to 6 or more decimal places.

After a painstaking process of not being able to view geo info when files are uploaded to Google Photos, I have determined that Google Photos won't return a map location unless the coordinates have been limited to 5 decimal places or less.  Is there a way to limit the decimal places when I use imatch to geotag?  I have been shortening the info to 5 decimal places manually, but of course, this is a painstaking and time-consuming way to do it.  

Secondly, Google Photos also requires that the quicktime/userdata/gpscoordinates field be populated with latitude and longitude info to display a location map.  I have figured out an odd way using the ECP to write to this field.  Strangely, I use   -quicktime:userdata:gpscoordinates<${composite:GPSPosition}.  I have tried multiple other ways within imatch itself to write to this field but absolutely nothing has worked.  I have cut/paste, used templates pulling from various other fields, and used autofill.  In every case, although I might see the data in the field momentarily, once I hit write back and the file updates, the information disappears.

Any ideas?

Thanks.

Mario

#1
I have never heart about any of this.

When IMatch works with the Google Maps API, the coordinates returned by the API have at least six decimal digits. And IMatch maintains this precision. For all Map service providers.

When IMatch uses Google reverse geocoding, the returned coordinates and bounds have at least six decimal . And IMatch maintains this precision. For all Map service providers.

QuoteGoogle Photos won't return a map location unless the coordinates have been limited to 5 decimal places or less.

This is just laughable and probably just a bug on their end. What did Google support tell you?

QuoteSecondly, Google Photos also requires that the quicktime/userdata/gpscoordinates field be populated with latitude and longitude info to display a location map. 
QuickTime is a proprietary Apple metadata format used by some video files. Not images.
IMatch/ExifTool update GPS coordinates in QuickTime (somewhere in the Keys section) with the GPS coordinates IMatch manages in the database. It also updates the official EXIF GPS record and XMP coordinates during write-back.

I've just made a test with iPhone 12 images, and it works as I wrote. The QuickTime GPS coordinates are synchronized with the EXIF/XMP coordinates.