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

Non-existent U-turns...

I plan my routes on RideWithGPS (using Safari and Chrome on a MacBook Pro) and then export the route as a KML file and a FIT file. I load the KML file into Google Earth to make sure that the route is okay. I then load the FIT file into my Garmin Edge 1030 Plus (which has the latest 6.40 software).

During the ride, my Garmin Edge will occasionally tell me that a U-turn is coming up, even though there are no U-turns anywhere in that route. When I reach the point where the U-turn is supposed to be, the Garmin Edge tells me to just continue. A few kilometres later, it does it again.

When I get home, I double-check the route on RideWithGPS and the Google Earth for the exact points where the Garmin Edge was telling me to make a U-turn and neither application shows a U-turn anywhere.

Does anyone know why the Garmin Edge does this?

Top Replies

All Replies

  • I can't see that your process of using the KML format and Google Earth adds any value assuming you are using the OSM overlay for planning the route

    It’s not much use for drawing the route but it can be useful for figuring out what roads to use. 

    RWGPS also provides satellite view and street view, which gives you most of the benefits of Google Earth without using a separate program. (You probably know that but the OP might not.)

  • This will transfer the route from RWGPS to your Garmin account, where the route will be rebuilt by Garmin for your specific unit. 

    ??? The Garmin Connect website isn’t “rebuilding” the route. 

  • I don't have any examples because it happens only very rarely and yes I do look closely if it happens and I don't usually see anything amiss in the OSM maps or my routes created in RwGPS using OSM maps.

  • The OSM maps are created by many humans , just like us, of varying skill and diligence so it is always likely that some errors, mis-connections and other issues creep in and then Garmins highly skilled programming trys to create a route conforming to all the routing rules set by the user and come up with a route & directions, no wonder a few issues happen, I just follow the route line and don't ask the Garmin for too much intelligence .

  • and then Garmins highly skilled programming trys to create a route conforming to all the routing rules set by the user and come up with a route & directions,

    No, it’s not doing that. (Keep in mind that these are very slow computers.)

    The Garmins assume the map is perfect and will deviate from the track to keep following roads. I wish it would skip over these sections with a direct path. 

  • Okay, thank you (and everyone else) for the answers.  The next time I plan a route, I will use RideWithGPS OSM maps.  I will also have to go back to all my previous RideWithGPS routes, change the map style, and then re-adjust every segment.

    I understand what you're saying about the route not being precisely on the road (in fact, I can see that also on Google Earth) but I did not think it matters very much, and I'm puzzled that the device would think I need to make a full U-turn just because my route is slightly off the road (I would have expected a small left or right turn to get back on the road).

    In regards to keeping my eye on the map: the U-turn was 20km away (at the 95km mark) so it wouldn't have been visible on the map while riding at the 75km mark.  I had leaned to ignore these U-turns over the last two years, but I wanted to find the root cause of the problem.  I think it's clear now.