I want to add GPS Data to Disneyland PhotoPass Pictures

[GeorgeIoak]

Hi. I've just downloaded this tool and done some initial testing but I would think what I want to do has already been done so I thought I'd check for help before I struggled through this.

Oddly enough the photos from the Disneyland photographers have all sorts of EXIF data but unfortunately are missing any GPS data. We have tons of pictures and my daughter likes to view them on her Echo Show. Just adding the location of Anaheim might be enough for us to use the location filter feature of Amazon Photos but since in almost every case that we have a PhotoPass picture we also have a picture from our cell phone I was thinking you could

• Cycle through the photos
• If the photo is missing GPS data check the time stamp
• Find the next photo with the closest time stamp
• Copy GPS data from the photo which has GPS data
• Paste the GPS data into the photo missing GPS data

Even though I think this could be done (I can do this on either an iMac or Windows PC) somewhat easily I'm not a very good programmer. If nobody has done something like this or I'm wrong and this is a bit complicated then what's the easiest way to extract the GPS data from one photo and insert it into a set of other photos?

Thanks in advance!

[StarGeek]

It's late and I'm heading to bed as I read this, but doing it the way you mention would probably require some sort of scripting.

But what I think would be possible would be to create a Geotrack from the files that do have have GPS data and use that to fill in positions in the files that don't.  Take a look at Inverse geotagging. 

Also, tomorrow someone with a clearer head might be able to give more details/solutions.

[GeorgeIoak]

Thanks for pointing me to that reference page. I created a gpx.fmt file using the example code on that page and then ran the following command:

Code Select Expand

exiftool -r -if '$gpsdatetime' -fileOrder gpsdatetime -p gpx.fmt /Volumes/Pictures/Disneyland2019 > out.gpx

and I see the following in the terminal window:

Code Select Expand

iMac-2:Disneyland2019 george$ pwd
/Volumes/Pictures/Disneyland2019
iMac-2:Disneyland2019 george$ exiftool -r -if '$gpsdatetime' -fileOrder gpsdatetime -p gpx.fmt /Volumes/Pictures/Disneyland2019 > out.gpx
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 13.54.55.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 13.54.56.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 13.55.02.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 13.55.10.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 13.55.19.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 15.18.40.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 15.21.47.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 15.22.33.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 16.02.21.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 16.02.23.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 16.02.27.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 19.49.05.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 19.49.21.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 20.01.14.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 20.06.27.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 20.47.09.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-24 20.47.20.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 09.07.57.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 09.08.00.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 09.08.16.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 10.05.01.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 11.21.29.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 11.21.31.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-25 20.24.20.jpg
Warning: Bad IFD1 directory - /Volumes/Pictures/Disneyland2019/2019-08-26 10.01.30.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 17.41.25.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 17.41.27.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 17.41.29.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 19.05.01.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 19.10.30.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 19.10.37-1.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-26 19.10.37.jpg
Warning: Bad IFD1 directory - /Volumes/Pictures/Disneyland2019/2019-08-27 20.19.46.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.03.53-1.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.03.58-1.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.04.08.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.04.29-1.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.04.31-1.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 09.04.32.jpg
Warning: PrintConv ExposureCompensation: Argument "undef" isn't numeric in multiplication (*) - /Volumes/Pictures/Disneyland2019/2019-08-28 11.31.24.jpg
    1 directories scanned
  214 files failed condition
  327 image files read

So it appears that it is reading through all of the files in this folder and it created the attached geotagging file. I'm not sure why some of the pictures from our cell phones have that "undef" error in them. I took a look at one of them and perhaps it's because the ExposureCompensation value is 0 and that's not handled properly? Here's the info from the last picture it reported an error on:

Code Select Expand

exiftool '2019-08-28 11.31.24.jpg'
ExifTool Version Number         : 11.65
File Name                       : 2019-08-28 11.31.24.jpg
Directory                       : .
File Size                       : 2.5 MB
File Modification Date/Time     : 2019:08:28 11:31:24-07:00
File Access Date/Time           : 2019:08:31 11:44:30-07:00
File Inode Change Date/Time     : 2019:09:02 07:36:57-07:00
File Permissions                : rwx------
File Type                       : JPEG
File Type Extension             : jpg
MIME Type                       : image/jpeg
Exif Byte Order                 : Big-endian (Motorola, MM)
Make                            : samsung
Camera Model Name               : SM-G975U
Orientation                     : Horizontal (normal)
X Resolution                    : 72
Y Resolution                    : 72
Resolution Unit                 : inches
Software                        : G975USQU2ASGC
Modify Date                     : 2019:08:28 11:31:24
Y Cb Cr Positioning             : Centered
Exposure Time                   : 1/40
F Number                        : 2.4
Exposure Program                : Program AE
ISO                             : 200
Exif Version                    : 0220
Date/Time Original              : 2019:08:28 11:31:24
Create Date                     : 2019:08:28 11:31:24
Components Configuration        : Y, Cb, Cr, -
Shutter Speed Value             : 1/40
Aperture Value                  : 2.4
Brightness Value                : 1.75
Exposure Compensation           : 0
Max Aperture Value              : 1.5
Metering Mode                   : Spot
Flash                           : No Flash
Focal Length                    : 4.3 mm
Sub Sec Time                    : 528288
Sub Sec Time Original           : 528288
Sub Sec Time Digitized          : 528288
Flashpix Version                : 0100
Color Space                     : sRGB
Exif Image Width                : 3024
Exif Image Height               : 3024
Interoperability Index          : R98 - DCF basic file (sRGB)
Interoperability Version        : 0100
Sensing Method                  : Not defined
Scene Type                      : Directly photographed
Exposure Mode                   : Auto
White Balance                   : Auto
Focal Length In 35mm Format     : 26 mm
Scene Capture Type              : Standard
GPS Latitude Ref                : North
GPS Longitude Ref               : West
GPS Altitude Ref                : Above Sea Level
GPS Time Stamp                  : 18:02:21
GPS Processing Method           : GPS
GPS Date Stamp                  : 2019:08:28
Compression                     : JPEG (old-style)
Thumbnail Offset                : 1122
Thumbnail Length                : 56014
Image Width                     : 3024
Image Height                    : 3024
Encoding Process                : Baseline DCT, Huffman coding
Bits Per Sample                 : 8
Color Components                : 3
Y Cb Cr Sub Sampling            : YCbCr4:2:0 (2 2)
Time Stamp                      : 2019:08:28 11:31:24-07:00
Aperture                        : 2.4
Image Size                      : 3024x3024
Megapixels                      : 9.1
Scale Factor To 35 mm Equivalent: 6.0
Shutter Speed                   : 1/40
Create Date                     : 2019:08:28 11:31:24.528288
Date/Time Original              : 2019:08:28 11:31:24.528288
Modify Date                     : 2019:08:28 11:31:24.528288
Thumbnail Image                 : (Binary data 56014 bytes, use -b option to extract)
GPS Altitude                    : 45.4 m Above Sea Level
GPS Date/Time                   : 2019:08:28 18:02:21Z
GPS Latitude                    : 33 deg 48' 56.12" N
GPS Longitude                   : 117 deg 55' 8.98" W
Circle Of Confusion             : 0.005 mm
Field Of View                   : 69.4 deg
Focal Length                    : 4.3 mm (35 mm equivalent: 26.0 mm)
GPS Position                    : 33 deg 48' 56.12" N, 117 deg 55' 8.98" W
Hyperfocal Distance             : 1.55 m
Light Value                     : 6.8


Perhaps a good night's rest has created an idea on what to do next?! I have years of these Disneyland photos so getting GPS data added to them so they show up on the slideshow would be great. I can't imagine I'm the only one who's run across this so hopefully this can help others once a solution is found.

[StarGeek]

So it appears that it is reading through all of the files in this folder and it created the attached geotagging file.

The track looks good.  A long one spread across about a week.

I'm not sure why some of the pictures from our cell phones have that "undef" error in them.

It's only a warning and probably can be safely ignored.  It can be dealt with separately later if you wish. Your full output for "2019-08-28 11.31.24.jpg" shows the GPS timestamp for that appears in the GPS Track.

It does bring up something odd though.  I assume that the filename is supposed to be the time the picture was taken.  11:31:24 in the morning on August 28.  The timezone would be -07:00.  But the GPS timestamp is 2019:08:28 18:02:21Z, which is UTC (+00:00).  So the hour is correct at 7 hours ahead.  But the minutes are off by 29 minutes.  Dang, the DateTimeOriginal is 2019:08:28 11:31:24, same as the filename.  That's just very odd.  It might be something that needs to be addressed.

I took a look at one of them and perhaps it's because the ExposureCompensation value is 0 and that's not handled properly?

I did a quick test and a value of 0 is a valid value of ExposureCompensation, so there's probably something else weird in the file, but I wouldn't worry about it, as I don't think it should affect the geotagging.

The next step would be regular geotagging.  Top of the same page I linked before.  I'd suggest picking one image that doesn't have GPS coordinates that occurs within the time frame of the Geotrack to test with.  Fair warning, this isn't my area of expertise, so this will probably take some trial and error.

The basic command would be
exiftool -geotag=out.log TestFile.jpg

I'm assuming that you're still in West Coast US time zone (-07:00), so there shouldn't need to be reason to adjust for a different time zone.

Now, the difference between the GPS times and the image's DateTimeOriginal might cause problems.  It's up to you to decide if it's enough to worry about, since the gps location should still be close enough end up in the slide show.  If you want to deal with it, you can add -geosync=-00:29:03 to correct for the difference.

[GeorgeIoak]

I hadn't noticed that the time stamps are off, that is odd. I've always assumed that the file name is the actual time the photo was taken. 30 minutes of walking around Disneyland could throw the location off by a fair amount but I think for initial testing we ignore that for now.

I'm a little confused in the example to add geotag info to a file. The example uses a file named out.log which in my case should be the out.gpx that was created earlier. The out.gpx has all the locations found in the folder of pictures so how does the -geotag command choose which information to add to TestFile.jpg?

[StarGeek]

I'm a little confused in the example to add geotag info to a file. The example uses a file named out.log which in my case should be the out.gpx that was created earlier. The out.gpx has all the locations found in the folder of pictures so how does the -geotag command choose which information to add to TestFile.jpg?

Sorry, yes out.gpx, not out.log.  I was copy/pasting and only corrected part of it.

I believe that the geotag command takes the time from the image file, looks for where it might be in relation to the timing in the geotrack, and computes a position from that.  For example, assume your geotrack (looks at map of Disneyland) has you at Space Mountain at 12 noon and then at It's a Small World at 12:30.  The picture you take at 12:15 doesn't have gps data.  Exiftool will use the positions of Space Mountain and It's a Small World, compute the spot halfway between the two and use that position to GPS tag the 12:15 image.

Obviously, that's not 100% accurate and there may be times it would end up someplace weird, but it gets the approximate area.

The above command would be run just to test to see if it was working correctly because as I said, this isn't my area of expertise.  Before you run the command on a full directory, you would probably want to add a check to make sure it didn't process files that already had gps data.  Something like
-if "not $GPSLatitude"

[GeorgeIoak]

I got an error on running the command:

Code Select Expand

iMac-2:Disneyland2019 george$ exiftool -geotag=out.gfx "0afe7fdd-cbd7-43bd-9304-68564e886b91_copy.jpg"
Warning: Error opening GPS file 'out.gfx' in File:Geotag (ValueConvInv)
Warning: GPS track is empty in File:Geotime (ValueConvInv) - 0afe7fdd-cbd7-43bd-9304-68564e886b91_copy.jpg
Warning: No writable tags set from 0afe7fdd-cbd7-43bd-9304-68564e886b91_copy.jpg
    0 image files updated
    1 image files unchanged


I'm not quite sure what to make of this error. Is it because it doesn't like out.gfx or is it not able to write the tags to the file?

[StarGeek]

Exiftool can't find out.gfx.  Try using the full path to out.gfx.  Or drag it into the current directory ("iMac-2:Disneyland2019 george" ??).

I just tested your attached track on a file with the timestamp "2019:08:28 11:31:24" (from your file 2019-08-28 11.31.24.jpg) and it tagged the file as follows

Code Select Expand

C:\>exiftool -P -overwrite_original -geotag="Y:\!temp\yy\out.gpx" y:\!temp\Test4.jpg
    1 image files updated

C:\>exiftool -g1 -a -s -gps* y:\!temp\Test4.jpg
---- GPS ----
GPSVersionID                    : 2.3.0.0
GPSLatitudeRef                  : North
GPSLatitude                     : 33 deg 48' 43.69"
GPSLongitudeRef                 : West
GPSLongitude                    : 117 deg 54' 59.79"
GPSAltitudeRef                  : Above Sea Level
GPSAltitude                     : 7 m
GPSTimeStamp                    : 18:31:24
GPSDateStamp                    : 2019:08:28
---- Composite ----
GPSAltitude                     : 7 m Above Sea Level
GPSDateTime                     : 2019:08:28 18:31:24Z
GPSLatitude                     : 33 deg 48' 43.69" N
GPSLongitude                    : 117 deg 54' 59.79" W
GPSPosition                     : 33 deg 48' 43.69" N, 117 deg 54' 59.79" W

That location (Google map link) appears to be the Star Wars Launch Bay.

[GeorgeIoak]

Well it would probably help if I used the correct file name! I had out.gfx when it should have been out.px:

Code Select Expand

iMac-2:Disneyland2019 george$ exiftool -geotag=out.gpx "0afe7fdd-cbd7-43bd-9304-68564e886b91_copy.jpg"
    1 image files updated

After running that I do see that GPS data was written into the file:

Code Select Expand

iMac-2:Disneyland2019 george$ exiftool -s -GPS:all 0afe7fdd-cbd7-43bd-9304-68564e886b91_copy.jpg
GPSVersionID                    : 2.3.0.0
GPSLatitudeRef                  : North
GPSLongitudeRef                 : West
GPSAltitudeRef                  : Above Sea Level
GPSTimeStamp                    : 00:41:00
GPSDateStamp                    : 2019:08:27


So I'll have to experiment a bit and check this GPS location (it should be in California Adventure in front of Toy Story Mania). I have the original pictures in a zip file so I don't need to create a copy and I should add the flag to not run this on files that already have GPS tags.

This is a great start so thanks again for helping.

[GeorgeIoak]

I've done some experimenting and made some good progress. I was able to rename the PhotoPass file names to be in the same format as the cell phone file names. Photopass file names are just long strings with no date or time embedded (or at least not in a directly readable format)

I saw that the default time offset that GEO Tagging would use was 1800 seconds (30min) for GeoMaxExtSecs and GeoMaxIntSecs

Code Select Expand

iMac-2:Disneyland2019 george$ exiftool -if 'not $GPSLatitude' -geotag=out.gpx *.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.22.46_PP.JPG
Warning: No writable tags set from 2019-08-25 15.22.46_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.22.47_PP.JPG
Warning: No writable tags set from 2019-08-25 15.22.47_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.22.54_PP.JPG
Warning: No writable tags set from 2019-08-25 15.22.54_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.22.55_PP.JPG
Warning: No writable tags set from 2019-08-25 15.22.55_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.06_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.06_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.12_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.12_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.15_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.15_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.21_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.21_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.26_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.26_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.28_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.28_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 15.23.29_PP.JPG
Warning: No writable tags set from 2019-08-25 15.23.29_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.19.51_PP.JPG
Warning: No writable tags set from 2019-08-25 16.19.51_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.19.53_PP.JPG
Warning: No writable tags set from 2019-08-25 16.19.53_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.19.55_PP.JPG
Warning: No writable tags set from 2019-08-25 16.19.55_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.20.13_PP.JPG
Warning: No writable tags set from 2019-08-25 16.20.13_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.20.14_PP.JPG
Warning: No writable tags set from 2019-08-25 16.20.14_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.20.16_PP.JPG
Warning: No writable tags set from 2019-08-25 16.20.16_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.20.20_PP.JPG
Warning: No writable tags set from 2019-08-25 16.20.20_PP.JPG
Warning: Time is too far from nearest GPS fix in File:Geotime (ValueConvInv) - 2019-08-25 16.20.22_PP.JPG
Warning: No writable tags set from 2019-08-25 16.20.22_PP.JPG
    2 files failed condition
   88 image files updated
   19 image files unchanged


I see this in the GEO Tag file we created:

Code Select Expand

<trkpt lat="33.8046978888889" lon="-117.921657972222">
  <ele>3.599</ele>
  <time>2019-08-25T16:13:31Z</time>
</trkpt>
<trkpt lat="33.80503525" lon="-117.921183888889">
  <ele>79.915</ele>
  <time>2019-08-25T16:21:23Z</time>
</trkpt>


So that should be within the window for the 16.19 and 16.20 pictures. The 15.22 and 15.23 pictures do appear to be out of the window since in the file I only find these tags:

Code Select Expand

<trkpt lat="33.8141999722222" lon="-117.920688972222">
  <ele>0</ele>
  <time>2019-08-25T03:47:18Z</time>
</trkpt>
<trkpt lat="33.8046761944444" lon="-117.921640972222">
  <ele>3.699</ele>
  <time>2019-08-25T15:55:45Z</time>
</trkpt>
<trkpt lat="33.8033009722222" lon="-117.919224972222">
  <ele>0</ele>
  <time>2019-08-25T16:07:53Z</time>
</trkpt>


Can you see why the 16.19 and 16.22 failed to be tagged?

[StarGeek]

The thing to remember is that the geotrack file time stamps are in UTC.  So 2019-08-25T16:21:23Z would be 2019-08-25 09:21:23 West coast time (-07:00).  And a time in the image file of 2019-08-25 16.19.55 would need a geotrack time of 2019-08-25 23.19.55.

[GeorgeIoak]

Whoops, that makes sense then. So in my file I see this:

Code Select Expand

<trkpt lat="33.807135" lon="-117.919523972222">
  <ele>-6.51</ele>
  <time>2019-08-25T18:21:19Z</time>
</trkpt>
<trkpt lat="33.8047043333333" lon="-117.921624888889">
  <ele>-2.513</ele>
  <time>2019-08-26T00:16:10Z</time>
</trkpt>
<trkpt lat="33.8047043333333" lon="-117.921624888889">
  <ele>-2.513</ele>
  <time>2019-08-26T00:16:10Z</time>
</trkpt>


So I've got some tags somewhat close to the time and definitely better than nothing. I'm a little confused if I need to increase both GeoMaxExtSecs and GeoMaxIntSecs. I assume the format would be to pass
-GeoMaxExtSecs=2700 onto the line where I'm writing in the GPS data?

[StarGeek]

See here for the options and how to set them.

The easiest would be to use the -api option, so you would add this to your command
-api GeoMaxExtSecs=2700

[GeorgeIoak]

Thanks again for all the hand holding. I was able to use that to add information into the remaining files. If I want to get a more accurate GPS tag by looking at the picture and finding it's GPS coordinates on Google Maps do I need to change any fields besides something like this:

Code Select Expand

exiftool -GPSLatitude=33.807694 -GPSLongitude=-117.919222 '2019-08-25 15.2'*

I wasn't sure if I needed to change any other values besides the Latitude and Longitude

[StarGeek]

You also need to change the GPSLatitudeRef and GPSLongitudeRef.  The GPSLatitude and GPSLongitude are unsigned, so the additional tags need to be written.

The easiest way, IMO is to just write the same values  to the Reference tags.  Exiftool will figure it out and write the correct values.
exiftool -GPSLatitude=33.807694 -GPSLatitudeRef=33.807694 -GPSLongitude=-117.919222 -GPSLongitudeRef=-117.919222 '2019-08-25 15.2'*