Next year I’ll be walking part of the Camino de Santiago. See A long walk needs a bit of a training plan for more on that.
To help with my training I downloaded and installed the Runkeeper app on my iPhone and use it to track several kinds of activity: dog walks, walks by myself, time on the treadmill and cycling.
I have to keep the dog walks separate from my ‘alone’ walks because one kind involves dawdling and backtracking and long pauses for peeing and sniffing, while the other is straightforward movement.
Often while I do one of these activities I’ll take one or more photos from within the app, and that’s revealed a glitch I’ve reported to Runkeeper. The problem is that when those photos arrive on my Mac, which they do automatically via Dropbox’s Camera Uploads feature, their timestamp is off by 13 hours.
See the selected file in the screenshot , and the photos near it which were apparently taken in the middle of the night, unlike the movie that I shot only a few minutes after the ‘zebra’ photo using a different app and which has the correct timestamp. For some reason the photos were recorded with UK time, rather than NZ time, even though the Runkeeper activity itself records the correct time.
Unfortunately that incorrect metadata carries over to Aperture as well.
Runkeeper support says:
This is a super specific edge case we haven’t heard of before, thank you for pointing it out!
Luckily my tolerance of timezone difficulties was considerably enhanced a few months ago when I watched this most excellent 10 minute video:
The Problem with Time & Timezones — Computerphile.
Beware though: timezones will make your head hurt!
Oh, and apart from this timezone glitch and possibly a difficulty with the in-app camera that I have yet to confirm where the image doesn’t show on the screen while lining up the shot, Runkeeper itself is excellent, and I’m really enjoying tracking my various walks and bike rides. If you’re doing outdoorsy things you may like to give it a try.