Advertise on Bikeforums.net



User Tag List

Results 1 to 19 of 19
  1. #1
    working on progress treebound's Avatar
    Join Date
    Apr 2005
    Location
    Wisconsin
    My Bikes
    yes
    Posts
    2,742
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    How accurate is GoogleMaps for your commute

    Just curious, if you go to maps.google.com and get directions for your bike commute, how accurate is the elapsed time that google estimates for the trip versus your actual time? You can pull the suggested route around to follow your actual route, you might have to turn on the bike route options for the map overlays.

    For one route I'm looking at, google maps is saying 14.6 miles and 1:25 for the time, which is somewhere around 10-11mph average allowing for stop signs/lights. Seems low, but maybe not. I guess I should go check out the "how fast" threads, but I was just curious specifically about the Google Maps bike routing function. Granted it is all relative, and different people ride at different speeds, and I don't know if the utility calculates in hills and such.

    I was going to try using the Poll option, but can't get it to work on this computer. So how about giving your actual time/distance and then what Google Maps comes up with. I'm going to try and get out for a non-commute ride this weekend and see how close it is.
    = = = = = = = = = = = = = = = = = = = = = =
    Life happens, don't be a spectator.

  2. #2
    Old, but not really wise CptjohnC's Avatar
    Join Date
    Jul 2010
    Location
    Fairfax, VA commuting to Washington DC
    My Bikes
    2010 Kona Dew Drop (the daily driver),'07 Specialized Roubaix (the sports car), '99 ish Kona NuNu MTB (the SUV), Schwinn High Plains (circa 1992?) (the beater)
    Posts
    811
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The google maps times seem to be set based on the more casual recreational or commuting cyclist. Mine says it would take 1 hour, 48 minutes, covering 18.9 miles. My actual distance this morning was 18.97 which I covered in under 73 minutes. My norm is closer to 83 minute for that distance, but still far shy of the 108 minutes Google wants it to take me.

    I pass plenty of folks for whom those estimates would be accurate. And plenty pass me who would scoff if I posted my estimated times. Unlike cars which, regardless of their performance potential, all go pretty much the same speed because of road conditions, bike speeds are determined far more by their rider. The google times may be accurate for you, or may not.

  3. #3
    Senior Member
    Join Date
    May 2012
    Posts
    74
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Google maps probably has intentionally slow estimates so that people plotting a trip for the first time needing to get somewhere on time don't underestimate the time it will take, which is probably a wise move. This site probably has better specific estimates since you can set estimated flat and climbing speeds, among other things: http://www.bikeroutetoaster.com/

  4. #4
    Senior Member
    Join Date
    Apr 2010
    Posts
    782
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    In my experience, I take the Googl Maps Bike times & figure my time will be around 2/3 of whatever they post. It has always been pretty accurate.
    Last edited by MK313; 07-13-12 at 07:52 AM.

  5. #5
    Senior Member
    Join Date
    May 2012
    Location
    North Attleboro, MA
    My Bikes
    2011 Steamroller; 1998 Cannondale F-400; 1981 Motobecane Jubilee Sport
    Posts
    231
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Unless you are familiar with the route google.maps is suggesting, I suggest doing an actual ride. Google.maps is famous for inventing roads. The last time that I used it on my phone for navigation, it tried to send me down a private road that was closed to public traffic, and I wound up having to circumnavigate through the bad part of da hood. Not fun.

    Time wise? It's actually fairly accurate for some routes I know are correctly mapped. The number of major intersections that need to be crossed and traffic lights and traffic on narrow roads tends to limit my speed.
    2011 Surly Steamroller; 1998 Cannondale F-400; 1981 Motobecane Jubilee Sport
    Car free since 1998. Big Oil hates me.
    Quote Originally Posted by Bill Nye, The Science Guy
    Bicycling is a big part of the future. It has to be. There's something wrong with a society that drives a car to workout in a gym.

  6. #6
    Senior Member
    Join Date
    May 2011
    Posts
    198
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Google maps tells me my commute should be 2 hours and 5 minutes. I did it this morning in 1 hour and 21 minutes. My slowest time for the commute (bad weather, headwinds etc.) has never been as slow as 2 hours and 5 minutes.

  7. #7
    working on progress treebound's Avatar
    Join Date
    Apr 2005
    Location
    Wisconsin
    My Bikes
    yes
    Posts
    2,742
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Interesting, thanks, and it looks so far like 2/3rds of Google time might be a good adjusted guesstimate.

    I'll check out the toaster site and see what it shows. Thanks for the link.
    = = = = = = = = = = = = = = = = = = = = = =
    Life happens, don't be a spectator.

  8. #8
    Senior Member locolobo13's Avatar
    Join Date
    Oct 2011
    Location
    Phx, AZ
    My Bikes
    Trek Mtn Bike
    Posts
    684
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Never use google maps for times. Instead I use it to scout potential routes and distances. Just looked and it gives a longer time than my computer says. But my computer doesn't account for time at the lights.

  9. #9
    ****** squegeeboo's Avatar
    Join Date
    Dec 2006
    Location
    Rochester, NY
    My Bikes
    Specalized Tri-Cross
    Posts
    875
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Eh, it's always slow for me, I bike between 15-20mph based on weather, google maps estimates 11ish. But my real issue with it is the bike 'safe' routes it picks for me. I normally end up doing a car route, but turning on the 'no highways' option, otherwise it'll add 20/30% extra distance while it tries to route me around 'unsafe' roads or over to out of the way bike paths.
    In the words of Einstein
    "And now I think I'll take a bath"

  10. #10
    Bicycle Commuter Bluish Green's Avatar
    Join Date
    May 2012
    Location
    Springfield, IL
    Posts
    716
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I checked google maps against my daily commute. Once I dragged the map line to the streets I actually take (I ride an extra half mile to get a wider street with less turning traffic conflicts), the distance and time were very accurate. My bike computer tells me I average 11.0 to 11.5 mph for most of my commutes, and that is rolling speed (not including time stopped), so when I add in a couple of minutes at some of the 10 traffic lights I ride through, the google time estimate is pretty accurate for me. Higher speed riders will get there earlier, obviously.

    Just be sure to take the suggested route as a starting point and look for safer nearby alternate streets as alternates.

  11. #11
    Junior Member
    Join Date
    Jul 2012
    Posts
    24
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I find that Google maps estimates it time based on a casual riding pace. It recently took me 3 hours and 19 minutes to make a commute that Google estimate to be 3 hours and 31 minutes. In no way was I going at any sort of race pace. This route consisted of rolling hills.

  12. #12
    Bicycle Commuter Bluish Green's Avatar
    Join Date
    May 2012
    Location
    Springfield, IL
    Posts
    716
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by cycronin View Post
    Google maps probably has intentionally slow estimates so that people plotting a trip for the first time needing to get somewhere on time don't underestimate the time it will take, which is probably a wise move. This site probably has better specific estimates since you can set estimated flat and climbing speeds, among other things: http://www.bikeroutetoaster.com/
    Thanks for the link to the bikeroutetoaster site, I really like it. Very useful for scouting routes using both street maps and aerial photo maps, and for getting elevation information on the route I usually take. I hadn't seen that site before; it is a new favorite. Thanks!

  13. #13
    Senior Member Notso_fastLane's Avatar
    Join Date
    Dec 2011
    Location
    Everett, WA
    My Bikes
    Kona MTN bike, Bent TW Elegance
    Posts
    630
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    On my short commute, it's actually pretty close, and it must have something in the routine to take hills into account, because when I hit the 'reverse route', the time drops by 3 mins (downhill). The predicted time is close, but most of the delays I hit seem to be lights along the way. Also, my downhill speed is much better than it predicts, maybe because I'm commuting on a recumbent.

  14. #14
    Newbie
    Join Date
    Jun 2012
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Mine is pretty close. It is more governed by stoplights than ride time.

  15. #15
    Team Water Andy_K's Avatar
    Join Date
    Jan 2008
    Location
    Beaverton, OR
    My Bikes
    2013 Kona Jake, 2008 Kona Major Jake, 2013 Kona Jake the Snake, 1999 Kona Muni Mula, 2012 Ridley Excalibur, 2008 Surly Long Haul Trucker
    Posts
    6,642
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Wildly inaccurate, but it really depends on the nature of the roads.

    The route I rode today went through a lot of suburban residental neighborhoods with many stops signs and traffic signals (15-20 stops over 10 miles). Google maps estimated it at 53 minutes. I did it in 40 minutes, plus however long I was stopped, which I'd guess at 5 minutes. So that's within about 15%.

    The route I rode yesterday went along mostly rural roads with little traffic and just a few stops. Google maps estimated it at 68 minutes. I did it in 42 minutes, plus however long I was stopped, which I'd say was less than 3 minutes. So that's right on the earlier quoted 2/3 error.

    It also depends on wind and how much effort I put into the ride.

  16. #16
    GATC
    Join Date
    Jul 2006
    Location
    south Puget Sound
    Posts
    6,551
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Wow their estimate is about 130% of my typical time for the route they suggested.

  17. #17
    Senior Member degnaw's Avatar
    Join Date
    Mar 2008
    Location
    Longmont, CO
    Posts
    1,575
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Clearly, this thread is biased because the typical hardcore bikeforums member rides much more often, and thus faster, than the typical overweight American.

    FWIW, google maps says my route is 15.6 miles/1hr 20min, while my cyclocomputer says 16.0 miles/~55min.

  18. #18
    Senior Member
    Join Date
    Jun 2010
    Location
    Fairfax, VA
    Posts
    146
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    We all have a sense of how long our commutes should take after we do them a couple times, even if we choose to take a new detour; time estimates are of limited use to us. I think google maps might be tuned to give estimates for bike tourers because it is probably a lot more important to them. You're far more likely to do only 10-12 mph on a loaded touring bike and doing day after day of 50-150 miles.

  19. #19
    Senior Member Ira B's Avatar
    Join Date
    Aug 2010
    Location
    Coupeville, WA
    My Bikes
    84 Raleigh Technium- 89 Shogun Mt. Bike-96 Miyata 914
    Posts
    880
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Works out very close for me.
    Yep, THAT Ira

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •