03.May.2012

May 3, 2012

Distance today = 47.27 km; Total distance = 5960.38 km; Location = Fort Collins – 40 31.325′ N, 105 03.155′ W; Start time = 0918, Finish time = 1608

http://connect.garmin.com/activity/174454693

http://connect.garmin.com/activity/174235487

http://connect.garmin.com/activity/174235445

I decided to run a more convoluted route through the countryside today, to escape the freeway and urban sprawl. I’m glad I did, as I found some nice quiet backroads. However, I was only partially successful, as there was still plenty of traffic on many of the roads this afternoon.

It was a sunny day in the high 20s C, but the lack of humidity made it quite pleasant to run in. Tomorrow is predicted to be 30C. I am wondering what it’s going to be like in a couple of months time when summer really hits.

I saw my first large snake roadkill today. It was about five feet (1.5 m) long, and had light and dark brown markings. The head was squashed, so it was hard to tell which species it was, but I know it wasn’t a rattlesnake.

Now, you may have noticed the three Garmin data links above. You may also recall that twice in the past few weeks the Garmin data has refused to upload. This is a big issue to me, as I place great importance on a full and accurate documentation of every step of my run around the world. This Garmin data allows anyone to zoom in and see the fine detail of where I’ve run that day, even to the extent of seeing which side of the road I’m on. It also shows my speed at every moment of the day and my elevation. There’s no way anyone can cheat when they’re providing this level of documentation.

Well, the Amazing Jimbo has solved The Mystery of the Non-Uploading Data. He found a file repair program on the Garmin web site and managed to upload the data that was sitting in the system. What a genius! We’re not sure exactly why it refuses to upload sometimes – it is not unique to me – but may be related to the battery life of the watch at the time of uploading. While it’s a bit of a mystery, at least we know how to fix it now if it happens again. I have also inserted the relevant links retrospectively into the blogs where they were missing.