Local camera time is only part of the story

Imagine taking a photo at 9:00 a.m. in California and another at 9:00 a.m. after traveling to New York. The clock readings look identical, but they describe different instants. A UTC offset such as −08:00 or −05:00 supplies the missing time-zone context.

Why international travel makes this harder

Camera clocks usually display local time, but you do not need to change the camera clock when you arrive in a new time zone. The workflow still works as long as the camera remains accurate for the previous location’s local time. No extra time-zone step is required during matching.

How the Shutter Trail workflow handles offsets

  1. The GPX track provides timestamped locations in an unambiguous time format.
  2. The Lightroom plug-in reads each photo’s capture time and embedded UTC offset.
  3. Each photo is converted to a comparable instant before the nearest track point is selected.
  4. The workflow accounts for cameras that remain on a previous location’s local time.

Example: After flying from California to New York, your camera can remain on California time. As long as that clock is still accurate for California, the photos can still align with the New York GPS trail.

Review ambiguous matches

No automated workflow should hide uncertainty. Review unmatched photos, matches far from a track point, and images captured around daylight-saving or international time-zone changes before applying locations.

Get the free Lightroom plug-in Download free