This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

One way streets

Hi guys,

I took my Edge 810 out the other day having done a quick route on my computer using Garmin Connect. I started riding and all was fine, until I got to a roundabout (didn't take very long). The route was the exact opposite direction to the direction of the traffic, i.e. it wanted me to hit the cars coming towards me.

I then had a look at the map on Garmin Connect when I got back and realised it really does have a habit of doing this. When recalculating as well, it often chooses to go the wrong way down one way streets.

Is this a London/Europe thing or is this a bug with the software etc.? It seems REALLY unacceptable on a near £500 device with all the bits and bobs.

Freddie

0 JaVaWa over 11 years ago

It's not an Edge thing; it's just that Garmin Connect uses pedestrian mode when creating routes, which means that it takes the shortest route and doesn't take one way streets in account. There is no setting to change that.
That is: when you use Google Maps. Try OpenStreetMap; you may get better results.

0 FREDDIESHOREDITCH over 11 years ago

I just tried with OSM, with no luck I'm afraid. RideWithGPS does it fine without going the wrong way. It's just when the course goes on my Garmin, it seems to like to deviate from it.

For example, there's a route I have that goes down Old Street coming from Hackney, and I want to go right on the Old Street roundabout, as I have put in RideWithGPS. When it comes onto the Garmin, it wants to go right at the street before the roundabout and go around the reeking to get onto City Road. This isn't necessary, it's much faster on the roundabout. Any ideas why this might be?