Camera clock field note
How to correct camera clock offset before GPX matching
Separate timezone from camera drift, test the correction against known moments and avoid shifting a whole photo set on a hidden assumption.
1. Separate timezone from offset
Timezone answers which civil clock the camera displayed. Offset answers how far that displayed clock was fast or slow. Treat them as two explicit inputs instead of collapsing both into one unexplained number.
2. Look for embedded UTC offset evidence
Some cameras write OffsetTimeOriginal beside DateTimeOriginal. Preserve it as evidence. If it is absent, choose the relevant IANA timezone rather than defaulting to the Mac's current setting.
3. Find a known photo moment
Use a photo taken at a recognizable track event: departure, a summit stop or another moment you can identify. Compare its interpreted capture instant with the GPX timeline and measure the difference.
4. Apply one bounded correction
If the camera was 2 minutes 15 seconds slow, add that amount to its timestamps for the preview. Do not change source metadata while experimenting, and keep the allowed correction within a defensible range.
5. Check the whole set
A plausible anchor can still hide a wrong timezone or a clock change during the trip. Inspect early, middle and late photos. Sudden divergence may mean daylight-saving confusion, multiple cameras or a clock adjusted mid-shoot.
6. Keep the model in the receipt
Record the selected timezone, signed correction and adjusted capture instant per photo. A later reviewer should be able to reconstruct why a coordinate was offered.
A compact model
adjusted instant = EXIF local time interpreted in timezone + signed camera correction
An embedded EXIF UTC offset can provide the interpretation for that photo, but the workflow should still expose the chosen trip timezone rather than running with an invisible default.