Do any cyclometers have a feature that cures this problem?:
I ride in New York City. I am often forced to ride at under 5 miles per hour, and it's almost always because I am coming to a red light, weaving between stopped cars, avoiding pedestrians, etc. On a typical 8-mile commute to my office, I can cruise at 22mph for half the ride along a nice bike path -- but the rest of the ride is spent dealing with traffic and pedestrians. As a result, my average speed ends up plummeting to around 14mph. It's so disheartening!
The problem seems to be that the computer keeps ticking the clock as long as it thinks your wheels are spinning at all. But whenever I'm riding at 5 mph, I don't think it even counts as biking. It's bullsh!t time, really. I'm just moving my bike through bullsh!t to get back to the part where I get to really ride again. Why should time spent doing non-biking destroy my average?
Even when I'm exhausted and climbing the biggest hills around here, I never go below, say, 8 mph. I wish my computer could be smart enough to know that any time spent biking at speeds under around 5 mph should NOT be counted towards calculating my average speed.
So the TOTAL DISTANCE reading should be calculated constantly, no matter how fast I'm riding.
But the AVERAGE should be calculated based on a TIME and an ALTERNATIVE DISTANCE reading that only accumulate when I'm in excess of a minimum speed that I think fairly represents the speed below which I am not "really" biking.
Are there any computers smart enough to do this?