CJ wrote:Thanks for a very informative reply Andrew. I hadn't realised that the more sophisticated "outdoor" style GPS units could also work like a motoring "satnav".
I often hear of cyclists using Tom Tom or the like to plan cycing routes, but wonder what sort of cycling routes they get. I guess that the kind of cyclist who is happy with these routes will be a confirmed roadie, who wouldn't use a cycletrack even if it was going his way and tolerates the traffic on main roads in preference to the often inferior surfaces of minor roads. I guess that I, as one who delights in exploring the least trafficked backroads and byways, would not be as happy with these routes, but I don't really know.
Can anyone who uses satnav tell us as to what sort of cycle route they actually get, and what they do to get it? Presuamably you can say "no motorways", but can you also limit trunk and A-road usage? And having said "no motorways", would a route from Bristol to Chepstow involve a 60-mile detour via Gloucester, because the software doesn't know there is a bikepath over the Severn bridge? Presumably the resulting route also takes no account of hills - or does it?
Tom-Tom says it has a "bike" mode, but what does it do? Do they mean motorbike? Or does it mean they have added cycle tracks to their roads database, if not in the UK then perhaps in the Netherlands at least?
As far as I can make out, the "bike" mode will just mean that any planned routes will avoid using motorways and any other roads that have bike bans. As far as I know, TomTom, Garmin etc all source their road mapping data from Navteq, and will have much the same limitations. One also shouldn't place too much reliance in the quality of bike-related data.
Using it in bike mode in a car, it tried to direct me off the M5 at every junction until I changed it at the services. It plans a route up through Gloucester rather than over the Severn Bridge. Navigating through central Bruges, it obeyed all the car one-way streets, although many/most of them allow 2-way passage for bikes and mopeds.
Calculated routes also ignore hills, the mapping data doesn't have much in the way of tracks or cycle lanes.
When routing over the Severn Bridge, I just put a waypoint each side of the bridge and ignored the instructions to go off up the A48. I believe that putting a waypoint in the middle of the bridge will work too.
The routing options are:
. Mode = Car/bike/Truck/Pedestrian etc
. Avoid = U-turns/Toll Roads/Highways/Unpaved Roads/Carpool Lanes
I haven't worked out exactly what it means by "Highways" yet. It certainly includes motorways and major A-roads. The trouble with setting it to avoid them is that it will put in a 10-mile detour to avoid 200m of A40.
I generally leave mine in car mode, and just avoid U-turns. When navigating, I set it to just use the shortest distance between waypoints, and use my skill and judgement to position the waypoints so the route goes where I want it to go. Planning the route overall, I do myself on a large-scale map.
Avoiding U-turns means that if you go off-route, or conciously vary the route, if just comes up with a new route to the next waypoint rather than nagging you to turn round.
I generally find that you only need one waypoint every 8-10 miles or so, and that having so few waypoints means that it is practical to enter the route directly on the GPS (rather than via a PC). This allows you to change the route during a ride, or plan the return leg at lunchtime. It's also handy on holiday without a PC, as you can enter the day's route during breakfast.
Using the routefinding without having planned any sort of route isn't something I've done much of. I usually only use it for directing me to destinations in unfamiliar towns, and will often not ask to be navigated until I reach the edge of town.