
Use multiple dated Geosync anchors when the difference between a camera clock and GPS time changes during the shoot. ExifTool can calculate a piecewise-linear drift correction from those anchors. One constant offset cannot fit a clock that is ten seconds fast in the morning and thirty seconds fast later.
Establish drift rather than two unrelated errors
Choose independent, trustworthy camera-to-GPS time observations near the relevant period's ends. Record dates and explicit time-zone offsets, not just clock faces. Keep each camera separate.
If someone reset the camera clock between observations, do not model that discontinuity as gradual drift. Split the affected periods and investigate the reset. A change in travel time zone can also be an interpretation issue rather than clock-rate drift.
The ExifTool geotagging documentation describes multiple synchronization points and piecewise-linear interpolation or extrapolation. Without dates on either timestamp in an anchor, that point supports only constant synchronization, not drift correction.
Express both clocks in every anchor
The following is a hypothetical syntax example for a disposable sample, not measured clock data:
exiftool -geotag track.gpx "-geosync=2026:10:23 09:00:00Z@2026:10:23 10:00:10+01:00" "-geosync=2026:10:23 17:00:00Z@2026:10:23 18:00:30+01:00" sample.jpg
Each value places GPS time before @ and camera time after it. Replace every example value and path with the actual authorized inputs. This command writes location metadata; preserve originals and test copies first.
In this invented example, the explicit offsets separate a time-zone representation from the growing clock error. Do not omit them because the computer happens to be in the same region today.
Check an interior point before widening the operation
Inspect a third known event between the anchors. The proposed check asks whether the changing calibration agrees with evidence that was not used to define both endpoints.
Also inspect records outside the anchor period. Extrapolating a clock trend beyond observed evidence can produce plausible-looking but unjustified locations. Limit the batch to the period supported by the calibration.
Geosync adjusts the time used for location matching; it should not be described as automatically repairing the photographs' original capture timestamps. Rewriting a known camera offset is a separate task.
Keep the calibration record
Retain the track identity, dated anchors, camera identity, checked sample and unresolved interval. Compare actual written GPS fields as well as a map display. None of these checks proves that an unverified image was taken at a particular place.
For a simple constant discrepancy, ordinary tracklog offset matching may be the appropriate scope. Use the multi-anchor mechanism because the evidence demonstrates drift, not merely because more parameters appear more precise.
Related tasks
- Correct a Camera Clock Offset in Lightroom Classic
- Lightroom GPX Auto-Tagging Misses Photos: Check the Tracklog Time Offset
Sources and scope
- Geotagging with ExifTool: Dated synchronization anchors enable piecewise-linear clock-drift correction. Interpolation and nearest-fix extrapolation have separate time limits. A GPS log CSV requires coordinate and timestamp columns, distinct from a metadata import CSV.
Official-documentation synthesis researched on 23 October 2026 (Asia/Shanghai). Public search returned readable official deep-page body text; direct ExifTool application and PDF/XMP reference fetches encountered HTTP 403. No command, image edit, GPS matching, protocol integration or filesystem-attribute test was executed. All sample paths, dates, values and acceptance exercises are illustrative. Source-defined boundaries and installed-version/file-format limitations remain part of the procedure.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.