KingstonWheelers.com

[Steve Irwin]

Looks like an interesting route, with plenty of climbing as well as distance! Even on the "less hilly" return leg you still went up that hill in Rusper that is part of the East Surrey Hardriders TT course, and probably plenty of others as well.

I think, though, that I must calculate average speed differently to most people. I was surprised when 18.3mph was mentioned as we only averaged 19.8mph on Dan's training ride, and that was only 40 miles with some very strong riding on the front. This was my file from Dan's ride:
http://connect.garmin.com/activity/41730860

Now, how I calculate the ave speed is I take the distance and time for the out and back legs, so from my ride I have:
42.82km 1:25:59
22.64km 37:03
total 65.46km 2:03:02 = 19.8mph

From Dominic's file I get:
85.921km 3:12:26
87.997km 3:03:45
total 173.918km 6:16:11
17.2mph

From Dan C's file:
85.698km 3:12:41
89.298km 3:08:23
total 174.996km 6:21:04
17.1mph

Dominic's return leg is a bit shorter because he didn't go all the way back to Surbiton, so I'll call it 17.1mph. 17.1mph makes a lot more sense compared to Dan's 40 mile training ride at 19.8mph, so it shows how much scope for confusion there is when trying to use average speeds as a guide to the standard on club runs.

Don't get me wrong, I think 17.1mph is actually a very impressive average speed for a ride over that distance and terrain. Having seen the data I'm not sure I'll be brave enough to join you if you do it again, it looks like a very tough ride.

[Dominic]

Fair enough - but its all pretty academic.
On the way down we had a puncture and a comfort break. Plus Brighton was a traffic light nightmare - so I am not sure how relevant including those times is - if you do you are encouraging fast riding in heavy traffic which I do not believe is sensible. The frequency and length of the stops on LBL means it is hard to compare with a Dan's route which has but onbe or two stops.

The second lap on my ride was taken from when we left the town and traffic lights etc. It has and elapsed time of 02:36:50 at an average speed of 18.3mph for 47.86ml. This included a few stops (the stop to make a decision about staying together and the one at Leatherhead were reasonably long). The 'moving time average' speed was higher obviously - 19.0mph

I don't think anyone in the group would have thought it comparable with Dan's 40 miler stops or not.

[maryka]

What does Garmin Connect calculate as "moving time"? If you click the "average" box above speed and select moving time, Dominic's file says 18.4mph and Dan's says 17.4mph.

I only stop my Garmin on a ride if it's going to be for longer than 5 min (puncture, cafe, etc.) When I get home I let SportTracks handle the stopped time thing, and to be consistent I have it set to consider anything slower than 5km/h or 3mph as stopped time -- making moving time anything but standing around waiting for people, or waiting a long traffic light.

Just curious because I see all these average speeds listed for rides that are way higher than mine and I always think to myself, "do you really ride that much faster when I'm not there?"
_________________
Blogging
Twittering

[RichA]

http://connect.garmin.com/help/faq#details

Garmin Connect provides three Time measurements on the Details page:

Time

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.

Moving Time

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.

Elapsed Time

Garmin Connect calculates the Elapsed Time by the amount of time elapsed from the actual Start and Finish time of an activity. This is helpful for customers with a Garmin device that have AutoPause turned on or hit the Stop and Start button in the middle of an activity. For those who don't have AutoPause or have that feature turned off on their device, Elapsed time should be very close or equal to Time.
_________________
Rich. Twitter. Blog.

[Dominic]

Dan C turned off at Leatherhead. I continued to Esher, so the rides that include past Leatherhead are not comparable.

I never stop my Garmin. I have included comments on the stopped time as they were the 'big' stops that you may not get on a standard club run.

I think that we have shown that 'average speed' is open to interpretation and can be misleading though.

(I still like the 3-lap idea)

[Matt T]

So gutted I missed this - the damn mother in law owes me big time...

I spent all saturday trying to explain to her that I needed to leave Cheltenham at 7pm to get back for my ride on sunday morning. Then in a restaurant at 11pm (in Cheltenham) she said to me "so Matt - where are you cycling tomorrow?"

AAAAAAAARRRRRRRRRRGGGGGGGHHHHHHH!!!!!!!!!!!!

Mark -please please please please organise another one soon. I promise to bring Flatman for your entertainment!

[Mark Dempster]

[Paul B]

Whatever the average speed, i was pretty cream crackered by end. I needed a little lie down when i got home.

[Dan Coulcher]

[Peter M]

Really enjoyed the ride on Sunday and felt suprisingly fresh on the way home! That was my first centry ride too.
It was a great group too and it was nice to meet some new faces.

My garmin stated 18.4mph average from epsom and back with a total of 102miles

Looking forward to the run to Kent

thanks again

Pete