| SvennoJ said: Today I learned Google has some funny idead about bike routes. I already noticed earlier that it has no problem sending you the wrong way down oneway streets and sometimes refuse to take roads that are perfectly legal to follow, instead it likes to make detours like this: |
I had a similar issue near me...
There is a nice mostly tarmac canal towpath route I wanted to try, I hadn't been on it before as to get to it I have to go about 2 miles by a relatively narrow and busy A-road which leads to a multi-lane roundabout there to serve the motorway. (which doesn't even have pedestrian paths)
After looking it up on GMaps it gave me a route along another river/canal towpath which would take me under the motorway and into the back streets on the other side. As usual I checked street view and noticed at the far end where it joins the back streets there was a "no cycling" sign followed by "private land". From what I could tell it was only the last few hundred metres though so I while I assumed it would likely be a dirt track I figured it would still be better to cycle it for a mile then if need to walk a couple hundred metres than use the roundabout.
Once on it though it is actually blocked off at the very begining by a building certainly older than GMaps. No idea who allowed that route onto Google unless they have taken them from some very old OS maps.
---
I managed to find an alternate road route around which isn't too bad on the way there (maybe an extra 10-15 minutes) but there is a long steep climb for when I am returning home.







