Showing posts with label GPS watches. Show all posts
Showing posts with label GPS watches. Show all posts

Wednesday, June 1, 2016

Resisting the cult of the new


About a year and a half ago, my wife gave me a Garmin Forerunner 220 for my birthday. Before that, I had just relied on Runkeeper on my smartphone (which necessitated getting a new smartphone when my Galaxy Nexus's GPS started to become erratic and unreliable). Once I experienced the advantages of a GPS watch -- much faster GPS lock, more accurate tracking -- I was sold. I've been super-satisfied with the 220.

Today, I took my dad to Road Runner Sports to look at GPS watches. For his purposes, Runkeeper would be perfectly adequate, but he doesn't want to run with a phone. We looked at the Forerunner 25, 230, and 235, and then I came home to do some research -- i.e., reading DC Rainmaker's reviews. It didn't take long to determine that the 25 would be the most cost-effective option for my dad. (He mostly runs laps at a non-standard track at the local elementary school.) I don't think he would use the fancier features on the 230/235.

However, as I read DC Rainmaker's review of those higher-end watches, I started thinking, hey, those sound like pretty cool features.... I use my Galaxy S5's step counting app, but it would be nice not to be tethered constantly to it, which the 230 or 235 would allow with their activity trackers. (That recent study about cellphones and cancer seems pretty questionable, as this column argues, but it wouldn't hurt to be cautious.) And the 235 has a heart rate monitor based on the wrist pulse, meaning no need for an uncomfortable chest strap.

I began to toy with the idea of offering my 220 to my dad (clearing all the settings, of course), and then getting a 235 for myself.

"Hey, wasn't that a present from Mommy?" my pre-teen son asked.

"Um, yeah," I answered sheepishly.

My wife was non-plussed. (She's so awesome!) "Go ahead and get it if you like," she said.

I got maybe 75 percent of the way toward pulling the trigger by ordering from Amazon, but I read some more reviews/comparisons. The third post in this thread from Let's Run included the following suggestion:

The GPS function of the 230 and 235 are both spot on, so tracking your run is fine. between the two I would get the 230. Less S*** to fail on you. better yet, save money, buy a Forerunner 220 (best running watch by Garmin currently in my opinion)
That threw some cold water on my idea. I did some more reading and it seems that the optical reader in the 235 is pretty new technology, and hence good but not great at picking up the HR. It would make more sense to wait for Garmin to work out all the kinks before adopting it.

The thrill of getting something new faded, and I told my dad that I thought the Forerunner 25 was the best choice for him. If/when my 220 dies, I'll upgrade, but until then, I'll stick with old reliable.


Sunday, June 15, 2014

When 5K races aren't 5K....


Once you start running races, if not even before then, the kilometers to miles conversion gets pretty easy to do in your head. I think it's because the most popular road races are 5Ks and 10Ks,but here in the United States, we still use the English imperial system of measurement, so 5K = 3.11 miles and 10K = 6.21 miles.

I don't have the best kick in the world, but sometime before those last 0.11 miles in a 5K, I like to go all out and empty the fuel tank. That leaves me dependent on either having a reasonably accurately measured race course, or knowing in advance that the course is going to be a non-standard distance.

For some reason, I've had a string of races lately that have been off. There was a 10K in March that checked in at 6.43 miles, a 5K in April that came out to 3.18 miles, and then most recently, a 5K that fell short at 2.93 miles. Now it's possible that the GPS on my smartphone was slightly off, as even GPS watches aren't perfect, but I'm inclined to think that the errors in those races were the actual distances, not my phone, because the race times I turned in (and in some cases, those of other racers that I talked to) were consistent with the courses having been mismeasured.

Assuming that my smartphone GPS was accurate, we're talking about mismeasured course distances of 3.5%, 2.3%, and 5.8(!)%. Those seem like pretty significant inaccuracies. The last one was the strangest one of all, as there was a short out-and-back segment in the middle of the race, where it seems like it would have been trivially easy to tack on an extra 0.09 miles to make the distance right.

Now, I'm not an elite runner, and these aren't qualifying races for any bucket-type events, so in the long run, it's not a big deal. But I found the last race in particular a bit annoying because I was pacing myself based on the expected distance, and the end of the race was hidden around a corner, so I basically finished with a very short kick, not to mention a sub-20:00 "5K" time - a goal that I'm chasing right now - that isn't real. I was comped this race, so I can't really complain, but if I'd paid the entry fee, I think I'd be a bit more annoyed - although I guess it would mean that if the organizers use the same route next year and I run it again, I'll be prepared to speed up at 2.7 miles instead of 2.9.

Thursday, April 24, 2014

Smartphones versus fitness wearables?

I have a running watch that's waterproof and can track up to 40 different intervals, but it doesn't have GPS. I've periodically thought about getting a Garmin, but inevitably, I ask myself, why? If I run on a treadmill, I know exactly how far and how long I went, and if I run on a track, I don't need GPS. On all other road runs, I carry my smartphone and use RunKeeper.

So I guess it's not surprising at all to read about the impending demise of Nike's Fuelband and the troubles ahead for other fitness wearables. I mean, I'm not exactly in the vanguard of tech gadget adoption, but I am one of those semi-obsessed runners who has about as much running clothing as non-running clothing. To the extent I'm somewhat representative of a swath of fairly dedicated runners, the fact that I'm not rushing to get any of these devices is not a good sign.

To be sure, I'm not saying that the smartphone/RunKeeper combination is a perfect substitute for a GPS watch or a fitness tracker. I have RunKeeper set up to give the most frequent audio cues about time/distance/average pace, which is every 1/4 mile and every 5 minutes. In a 5K race, that means I get 12 updates from the mileage and (at my pace) four more from the time. That's not bad, but if I want to check my average pace at some other point, I'd have to get pass my screen lock, which isn't trivial when you're running at near maxVO2. I could see how a watch or fitness tracker would offer some incremental advantage there.

But enough to be worth buying one . . . when that money could be used toward more race entry fees, or tech shirts, or shoes?