FLATULENTFRIEND wrote:Do you want a bike computer to tell you where to go / where you’ve been or a training tool?
The Garmin 200 will do the former but not so much the later – where HRM and cadence will be of more benefit.
slidecontrol wrote:moving time is your ride less whatever time you spent stopped, even with autopause turned on
if you view my last ride data, http://app.strava.com/rides/2227678 even though I stopped and started the timer at each break we [the bunch] had, my edge still noted the overall differences in ET and moving.
the altitude thing is merely a limitation of gps devices ,not just garmin. if you enable elevation correction GC compares your track to the topo info avaliable on the maps and constructs the elevation profile from that. barometric altimeters are easily fooled by weather
Directly from the FAQ:
Garmin Connect provides three Time measurements on the Details page:
Time is the recording time reported by the device. For Fitness devices, this should equal the Time value reported on the device. For other devices, this should equal the amount of time elapsed from the actual Start and Finish time of an activity.
Avg Speed/Pace is based off the Time value.
Garmin Connect calculates Moving Time by removing the amount of time when the user is stopped. This is helpful for customers who upload activities with a Garmin device that either don't have AutoPause or have AutoPause turned off. For those who have AutoPause turned on or hit the Stop and Start button in the middle of an activity, the Moving Time should be very close or equal to Time.
Avg Moving Speed/Pace is based off the Moving Time value.
Garmin Connect calculates the Elapsed Time by the amount of time elapsed from the actual Start and Finish time of an activity
69 Users browsing this website: banga, Brucie, CrustyMTB, DogsBollocks, DotBot, dwgknz, Exabot [Bot], Google [Bot], Google Adsense [Bot], herbman, moynie, nagem, Nigel Gregory, nyquist, phunk, rachelr, Rik, ryda, sifter, Wobbler, Yahoo [Bot], znomit and 44 guests