Go Back  Bike Forums > Bike Forums > Road Cycling
Reload this Page >

Avg MPH question

Search
Notices
Road Cycling “It is by riding a bicycle that you learn the contours of a country best, since you have to sweat up the hills and coast down them. Thus you remember them as they actually are, while in a motor car only a high hill impresses you, and you have no such accurate remembrance of country you have driven through as you gain by riding a bicycle.” -- Ernest Hemingway

Avg MPH question

Thread Tools
 
Search this Thread
 
Old 05-11-15, 02:38 PM
  #76  
Senior Member
 
Andy Somnifac's Avatar
 
Join Date: Aug 2009
Posts: 1,297

Bikes: Too many.

Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 92 Post(s)
Liked 174 Times in 86 Posts
Average Speed = Distance * Donuts Eaten
__________________


Andy Somnifac is offline  
Old 05-11-15, 02:50 PM
  #77  
Senior Member
 
wphamilton's Avatar
 
Join Date: Apr 2011
Location: Alpharetta, GA
Posts: 15,280

Bikes: Nashbar Road

Mentioned: 71 Post(s)
Tagged: 0 Thread(s)
Quoted: 2934 Post(s)
Liked 341 Times in 228 Posts
Donuts are good.

But I still say we should standardize on Googles. That is, how long Google Maps expects over how long it takes us. Say, Google says my commute is 42 minutes and I do it in 24, my average speed would be 1.75 Googles.
wphamilton is offline  
Old 05-11-15, 04:07 PM
  #78  
Middle-Aged Member
 
MikeyBoyAz's Avatar
 
Join Date: Apr 2011
Location: Mesa, AZ
Posts: 2,276

Bikes: Bianchi Infinito CV 2014, TREK HIFI 2011, Argon18 E-116 2013

Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 24 Post(s)
Likes: 0
Liked 0 Times in 0 Posts
Originally Posted by wphamilton
Donuts are good.

But I still say we should standardize on Googles. That is, how long Google Maps expects over how long it takes us. Say, Google says my commute is 42 minutes and I do it in 24, my average speed would be 1.75 Googles.
I'm highly disappointed by Google's calculation of cycling trip time. It quotes down at like 12mph with no regard to traffic or climbs etc. They need to raise the bar and improve resolution to include minutia in their calculations; else what's the point of Google even providing such a service.
MikeyBoyAz is offline  
Old 05-12-15, 07:38 AM
  #79  
Senior Member
 
GravelMN's Avatar
 
Join Date: May 2014
Location: Rural Minnesota
Posts: 1,604
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 75 Post(s)
Likes: 0
Liked 2 Times in 2 Posts
Originally Posted by JetBadger
In your example, the rider travels 10 miles at 10mph (60 minutes) and another 10 at 20mph (30 min)... this means the rider traveled a total distance of 20 miles / 1.5 Hours for an average speed of ~13.34 mph. I would be surprised if there were a bike computer to calculate this as 15 mph average speed. I think the "simple logic" applied above is simply false logic but that may be what you are trying to convey here.
Yes, that was what I was trying to convey, though not as clearly as I intended. The phrase "simple logic" or the word "most" should not have been used. What I meant by "simple logic" was the faulty logic that if I rode half the distance at 10 mph and the other half at 20 mph, that the two distances would have equal weight and the average should be the median of 15 mph. As you pointed out, the correct logic would be that only the total distance and total time are relevant and you rode at 10 mph for 2/3 of the total time thus having a greater effect on the average speed. I didn't expect that any bike computers would use faulty logic to come up with 15 mph in the example, but it would be easy for someone to use the "simple" but inaccurate method to come up with 15 mph and then be discouraged when their computer revealed the correct 13.3 mph.

This can be disheartening when you have had a great average speed over a relatively long ride only to have the life sucked out of that average by hitting a steep grade, strong headwind, or a bonk during just a few miles at the end.

Last edited by GravelMN; 05-12-15 at 08:05 AM.
GravelMN is offline  
Old 05-12-15, 07:53 AM
  #80  
Senior Member
 
wphamilton's Avatar
 
Join Date: Apr 2011
Location: Alpharetta, GA
Posts: 15,280

Bikes: Nashbar Road

Mentioned: 71 Post(s)
Tagged: 0 Thread(s)
Quoted: 2934 Post(s)
Liked 341 Times in 228 Posts
Originally Posted by MikeyBoyAz
I'm highly disappointed by Google's calculation of cycling trip time. It quotes down at like 12mph with no regard to traffic or climbs etc. They need to raise the bar and improve resolution to include minutia in their calculations; else what's the point of Google even providing such a service.
With Google who knows, but I have the impression that they do consider elevation changes and lights at least. When I check a local road, North Point Pkwy for example, it's slower uphill than downhill.

I'd like to see them take into account traffic, like they do with driving time, and also weather. And then scale it to the individual. They have the data - Google has a better idea of where I've been, and how long it took, than I do.
wphamilton is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
AFD13
Clydesdales/Athenas (200+ lb / 91+ kg)
50
07-15-15 06:43 AM
jppe
Fifty Plus (50+)
27
02-09-14 05:17 PM
IAMAMRA
Clydesdales/Athenas (200+ lb / 91+ kg)
53
10-03-13 12:39 PM
CalPastor
Clydesdales/Athenas (200+ lb / 91+ kg)
15
05-23-11 05:22 PM
fly:yes/land:no
Professional Cycling For the Fans
6
06-27-10 11:46 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service -

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.