UPDATE: I am considering the possibility that the bad data and problems I’ve had with RunKeeper are actually caused by my iPhone 4. I was reminded that when I click the built-in Maps application, it almost always shows my location incorrectly.

—– Original Post —–

After the swimming party earlier today, we decided to meet up with Mark and Kristen to ride the Alpine loop. It was the perfect day for it. The weather was nice and cool, slightly overcast with a gentle breeze. The top of the Alpine Loop is still closed to cars, so there was no traffic to deal with. It really was ideal.

Like usual, I decided to have Runkeeper track my ride. It has messed up many times in the past, but most of it’s problems haven’t been that bad. Only one or two have been really ugly. Today was the worst Runkeeper problem I’ve had. For some unknown reason, half way through my ride up American Fork Canyon, Runkeeper stopped recording data. I know there is no cellular coverage up there, but that really shouldn’t matter for collecting GPS data.

https://runkeeper.com/user/jtalbot/activity/39924225

Take a look at that map. Do you really think I magically bounced home from part way up the canyon? No. We rode all the way over the top, down through Sundance, down Provo Canyon, up through Orem, Lindon, and Pleasant Grove, and then back home. My bike computer said 41 miles, so I’m pretty upset that Runkeeper just stopped collecting data a third of the way through the ride. It may be time to find a new tool.

At least Charmaine’s Runkeeper didn’t mess up. Here’s her map. Compare and contrast it to mine. What a joke.

https://runkeeper.com/user/charmainetalbot/activity/39924164

Despite all that, it was a great ride. We took our time and really enjoyed the scenery. I think there’s a picture of us at the summit trailhead floating around on someone’s phone. If I find it, I’ll upload it.