29.Jul.2015

Jul 29, 2015

Yesterday I visited a nearby store to have a look at the latest Garmin products for running and cycling. I wasn’t actively looking to buy anything, but it was a good chance to catch up on the state-of-the-art in this area. Which brings me to a topic I think is worth knowing about if you’re contemplating buying this sort of product.

I have mentioned this issue before, but will elaborate a little now. When I began my world run I was using a Garmin 610 watch to record all my data, downloading it this web site each evening. The watch did exhibit intermittent problems during the downloading of data, but otherwise it performed well in the early days. However, after a few months of sweat running on to the recharging terminals, the watch eventually failed completely. I wasn’t willing to risk the same thing happening again, so I bought a Garmin 800 cycling device instead, holding it in my hand while I ran. Yes, believe it or not, I actually held the gadget while I ran a further 16,000 km.

The 800 worked without apparent issue, at least in regard to downloading data and recharging, doing so both quickly and reliably. It still does. However, I did notice during the world run that, whenever, I had a secondary source of measuring how far I had run, the 800 always seemed to be showing a lesser distance. Initially I assumed the secondary sources (Google Maps, i-Phone apps, highway markers, car odometer etc) were overestimating the distance. But when the same thing continued to happen, I started to question the situation – could all these other ways of measuring the distance always be wrong? The more obvious answer was that the Garmin was underestimating how far I had run. And it wasn’t trivial, often up to 5% or more of what other sources were indicating.

In recent times I’ve been running with the same device. However, there are some sections of courses near home that I have very accurately measured in the past. When I cycle these sections, the Garmin 800 is generally very accurate (one must always accept small discrepancies of 10 metres here and there). However, when I run exactly the same course, it is always short, usually between 3% and even up to 10%, although I estimate the average shortfall is about 5%.

Admittedly, the 800 is designed as a cycling computer, and it performs quite accurately when operated in clear view of the satellites and at typical cycling speeds. But it doesn’t perform accurately when held in my hand and operated at running speeds. I’m not sure if my hand is blocking the signal from the satellites, or if the internal system is calibrated for a faster speed, or a combination of both? Either way, I can live with this, as there are dedicated Garmin running watches which, I assume, are accurate. However, it’s something readers should be aware of, if you’re thinking of using a cycling device for running, and you require a high level of accuracy.

I don’t worry too much about it while training – it just means I’ve run further than I thought. But there is a major implication here for my world run. If the device was underestimating the daily distance I had run by, say, 5% over the final 16,000 km, this means I actually ran about 800 km more than was required. That’s more than two weeks of extra running. It’s too late now, but it is something I will certainly take a lot more seriously if I ever do another big journey run.

The world run photo for the day was taken as I crossed the border from Wyoming into Nebraska. I assume this was once some sort of border or quarantine post, but it’s clearly a long time since it’s been used.

 

417

 

On This Day

 

Jul 29, 2012

Distance today = 57.71 km; Total distance = 9912.93 km; Location = Festus, Missouri – 38 12.740′ N, 90 23.764′ W; Start time = 0827 Finish time = 1755

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

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

I ran, not just my longest day for quite some time, but also my hilliest. The landscape south of St Louis is completely different to what I’ve been running through recently. It is hilly and full of forests. I did not see a single farm or crop all day.

I forgot to mention in yesterday’s report that I’m now in the state of Missouri – my 13th US state of the run so far. I also passed 8,000 km run in the US today.

When I awoke, it was raining steadily, although quite lightly. The region really needs rain. Half way through the day the sun came back out. I reckon the locals would have preferred a few more days of rain.

I don’t know if it was the hills, but I ended up with a really sore muscle up high on my right hip. I don’t think it’ll be a problem, but I’ll have to be careful with it.

Finally, it was another great win for the South Sydney Rabbitohs on the weekend. As the old saying goes “When the Bunnies are doing well, the universe is in tune”.

 

Jul 29, 2013

Distance for today = 57.75 km; Total distance = 23,939.72 km; Location = Laura, SA – 33 10.859’ S, 138 18.103′ E; Start time = 0817, Finish time = 1735

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

I was a bit tired today, probably due to yesterday’s big climb. There was also a headwind. However, I still managed nearly 58 km, so things can’t be too bad.

The countryside continues to be spectacular. I am also running through towns now. After going 1,100 km without passing through a town, today I passed through four towns before reaching my destination in the town of Laura. Melrose is particularly quaint, and a mecca for mountain biking.

In Wirrabara, we met Carmel’s brother, Bernie, and his wife, Leslie. They are staying with us in Laura. We’re also expecting more visitors later this evening – more on that tomorrow, so stay tuned.