Cycling UK Forum

I have a Garmin Edge Touring and use Garmin Connect (the modern one, since I've never used the older version) to plan routes, sync data etc.

If I try to plan a route in Garmin Connect using the OpenStreetMap option, it's essentially impossible. It has decided that pavements are ok to cycle on, so planning a route even along a boring, straight road is horrible because it keeps darting off to the footpath. This is even if the "keep to roads" option is ticked.

An example, noting that there are no cycle paths there, shared use or otherwise:



And if I try to fix it, it just gets worse:



Is this a Garmin thing, or an OSM thing? Perhaps it's my local area? I have edited a few roads around mine to ensure that the footpaths are marked as "cycling prohibited" but it would take forever to fix all the roads in my area. (It seems most of them are marked as footpaths and not pavements or sidewalks, which won't help.)

As far as I can see, planning a route in cycle.travel doesn't have this problem, but then I've never managed the correct Voodoo incantations to get the gpx / tcx file into my Garmin.

If I plan the route using Google Maps it's much better. But then when I load the route in my Garmin, it takes forever to calculate the route (presumably so it can translate into its internal OSM map) and even then makes an occasional dart off to an unnecessary footpath.

So am I doomed? What better ways of getting a decent route into Garmin Connect / Garmin?

Can you let me know where the 'Goldsworthy Road' in your map is and I'll try to recreate.

I find google maps fine on Connect. BUT be aware that when you upload to your unit that the unit does the route calculation based upon the points you entered - say there's two choices of route between points A and B - if you don't click in an extra point at the planning stage to commit to one route or the other then the unit may calculate to go a way you didn't want to go. Also important to have all the route planning preferences off on the unit - like avoid main roads or ferrys etc or the unit will throw up some odd choices.

Stick with it though - they are not easy to use consumer devices but once you know what they are up to they work well.

Thanks. Goldsworth Road is in Woking.

There are many things wrong with Garmin Connect and the Garmin itself, but it's the lack of transparency that's one of the real killers. I would never have known that my carefully planned route might be ignored by the unit because it's trying to be "clever".

I've tended to default to having more waypoints than fewer, but it's a pain to do and feels like unnecessary work. At least now I know it's worthwhile - thanks.

mark a. wrote:Thanks. Goldsworth Road is in Woking.

There are many things wrong with Garmin Connect and the Garmin itself, but it's the lack of transparency that's one of the real killers. I would never have known that my carefully planned route might be ignored by the unit because it's trying to be "clever".

I've tended to default to having more waypoints than fewer, but it's a pain to do and feels like unnecessary work. At least now I know it's worthwhile - thanks.

That bit of road is OK in bikeroutetoaster with OSM mapping, so looks like Garmin website is problem.

wirral_cyclist wrote:That bit of road is OK in bikeroutetoaster with OSM mapping, so looks like Garmin website is problem.

Oh that's useful to know, thanks. It's these sorts of things that make one think about switching to bikeroutetoaster, ridewithgps or similar.

Does that for me too! But not when I switch to Google maps, that seems to work fine - so use that for planning - you can switch between maps as you edit. I've had no issues planning on google maps and running OSM maps on the unit - like you picked up - use plenty of points to stop the unit calculating its own way.

BTW found Goldsworthy road and tested on that. Google doesn't have the extra layer of footpaths so doesn't get led astray like the OSM map.

The OSM access tags are correct. A routing engine shouldn't route cycles up highways tagged as "footways". I assume there's a setting in the routing options on the Garmin site to route you as a pedestrian, cycle, car etc. It seems to think you are a pedestrian at the moment and is routing you accordingly. The "lock on road" option just keeps the marker on the nearest road rather than oscillating about due to inconsistencies in the gps signal. For this purpose a footpath being followed is a road so changing that setting won't help.

I can't find a setting in the Garmin Connect online service to ignore that layer - so I'd use Google maps if you are using the Garmin connect tool. Alternatively plan ridewithgps and import your routes into connect - but try a test first not all routes seem to go into connect.

Ok thanks. I'll use the Google Maps version for now, with extra waypoints, and see how that goes. One of my friends uses ride with gps so perhaps I'll give that a try at some point.