Copy link to clipboard
Copied
This is reporting a bug in Lightroom classic 13.1 build 202312111226-41a94e8 on Windows 11.
I recently returned from a European river cruise and ran a tracker on my iPhone and Apple Watch to gather tracklogs for the trip. That worked out fine. The program, Geotag Photos 2, created a GPX file and I verified that it matches the GPX schema, with latitude, longitude, and UTC timestamp for each logged point.
There are some serious problems in using this with Lightroom classic, however:
I'm thinking that Lightroom really needs an option to not convert an imported GPX tracklog to local time, but to leave it in UTC time. Having to apply TWO adjustments: back to UTC time, and then to the timezone where the tracklog was recorded is just too confusing for us mere mortals. It's as if Lightroom assumes you only collect tracklogs in your home timezone.
Also, Lightroom does not seem to save the entered tracklog offset anywhere. When I reload the tracklog, everything is reset to local time again. So I'm thinking the only way to reliably store a GPX tracklog for later use in LIghtroom is to convert the UTC times in the tracklog so it's relative to the local timezone -- then I could load it at will to see the track I took when I walked in each city. However, this just seems wrong to me.
I uploaded a sample tracklog. I can't upload a GPX file so I added a .XML extension. Change it back to .GPX or Lightroom can't see it.
There is another annoying bug in GPX file handling, but I'll report that as a separate issue.
The Map module is working with tracklogs as Adobe designed it, though many people (including me) find the design extremely confusing.
(Some background: I filed the original bug reporting that the Tracklog Time Offset command wasn't documented in the Help, and then I had to correct mistakes in the original version of the Help. The tech writers gave up trying to fully document its confusing behavior:
https://helpx.adobe.com/lightroom-classic/help/maps-module.html#timezone_offset_auto_tag)
- Tracklo
...Copy link to clipboard
Copied
The Map module is working with tracklogs as Adobe designed it, though many people (including me) find the design extremely confusing.
(Some background: I filed the original bug reporting that the Tracklog Time Offset command wasn't documented in the Help, and then I had to correct mistakes in the original version of the Help. The tech writers gave up trying to fully document its confusing behavior:
https://helpx.adobe.com/lightroom-classic/help/maps-module.html#timezone_offset_auto_tag)
- Tracklog times (which are recorded in the GPX file in UTC) are always displayed on the map (when you hover) converted to the time zone of the computer running LR. The Tracklog Time Offset command doesn't affect this.
- Map always treats the capture times of photos as in the time zone of the computer running LR. Map (and the rest of LR) ignore any time zones that may have been recorded with the capture times in EXIF (it's only in the last few years that the EXIF standard allowed cameras to record time zones, and LR was never updated to take advantage of that).
- The Tracklog Time Offset is used only by the Auto-Tag command when mapping tracklog times to photo times. But it doesn't change the contents of the GPX file, and it's setting is lost when you load a new GPX file or restart LR.
Seven years ago, when Adobe introduced the full Lightroom Ecosytem (Cloud, Mobile, Desktop), they stated that they would focus their efforts in Lightroom Classic on Develop and image quality. They've stayed true to their word, so I think it's unlikely they would consider Ideas proposing improvements to the design of the Map module.
Copy link to clipboard
Copied
Hi John: thanks for the great reply. You've clarified so much. It's a shame that Adobe isn't interested in the map module because it's quite good -- just, as you said, really confusing. It would solve a lot of problems if Lightroom would just honor the time offset when hovering over the track as presuably that would be the time and location that's applied to any photos.
Since I'd like to archive my GPX tracklog for each travel day in the photos folder, and don't really want to deal with computing the offset every time I load it (although I guess I could put that offset in the filename), and also would like the hover times to be accurate, I guess I'll write a little conversion program to mangle the UTC times in the tracklog for my current timezone, taking the original timezone into account. That should effectively trick Lightroom into processing the tracklog correctly -- at least until I move to a different timezone. Or maybe until daylight savings time takes effect, when the stored times will be off by an hour again. It really makes no sense to use the current timezone.
It seems like I struggle with the tracklogs every time and, as you said, there's no hope that Adobe will fix it. So I'll find a workaround.
Thanks again for taking the time to reply.
Copy link to clipboard
Copied
Can you please explain the proper way to use tracklogs to auto tag pictures? My process works sometimes, but is not working tonight:
1) I verify the tracklog in Google Earth for location and times (local, not my PC time)
2) I Take iPhone pictures to anchor time and location throughout the day, then make sure my camera matches those times (fixing the metadata capture time as required)
3) I load tracklog and set the time offset to correct the time (hovering over the tracklog never matches this so that's a wated feature that I wish Adobe would fix...probably never happen however)
4) I then autotag the images that fall within the time of the tracklog. More often than not this works. I just did it using LrC 14 (last version). Tonight the pictures are not geolocation correctly...hours off. (LrC 15.0 / macOS Sequoia 15.6)
I depend on this to tag vacation pictures. It's never been easy but now it's just broken.
Copy link to clipboard
Copied
It sounds like you're using the correct process. I've found that, given the poor design of the LR feature, the only effective way to troubleshoot this is to share a GPX tracklog, a problem photo, and the approximate location where the photo was taken. You can attach the tracklog here by changing its file extension to .txt, and you can export raw photos as JPEGs to attach here.
Copy link to clipboard
Copied
I use Geotag2 to generate tracklogs in UTC time. I test them by dropping them onto Google Earth to verify they're correct. I set the time zone in Google Earth to make the times match those in my camera (verified by iPhone shots that anchor the time and location at a few spots along the way) to make sure everything aligns as they should.
I then load the tracklog into LrC. First I have to remember that LrC changes the time to my computer local time so I do an offset. Then I autotag the pictures. Sometimes it works fine. Other times...not so much. Right now I'm noticing that when I hover the mouse over the tracklog in the Map window, the time is off by the same amount as the offset...but in the offset dialog box the times are correct. If I remove the offset, the time shown by hovering the mouse doesn't change (i.e. still off by the offset). I've turned off the tracklog and back on again...I've reloaded the tracklog...nothing is fixing this. Sometimes I can look at maps and manually tag the images, but I shouldn't have to...I'm way behind on processing vacation pictures and I'm losing waaaay too much time on this and I'm getting abit frustrated
Anybody know what's going on? I'me using LrC 15.0 on macOS Sequoia 15.6
Find more inspiration, events, and resources on the new Adobe Community
Explore Now