Big T wrote:Beware when using Cyclestreets. I find it gives some very odd results. I've just asked it for a route from Nottingham to the centre of Birmingham. The "Quick" route (55 miles), takes me straight down the A42, which no cyclist in their right mind would ever ride on (it becomes the M42 at Tamworth and carries the same traffic but without a hard shoulder). The balanced and quiet routes are 13 miles further and meander about all over the place. The logical route is to use the old A453, which used to be the main road, but is now bypassed by the A42/M42. It's lightly trafficked and fairly direct but Cyclestreets completely ignores it.
+1 for that. I find that Cyclestreets works fine in towns, where main roads have 40mph limits and actually are the preferred route for "fast" riders, where the off-road alternatives are surfaced in decent gravel at worst, so "quiet" is okay for all of those who want to avoid traffic, and where a slightly straightened out version of "quiet" is reasonably "balanced". In the rural context however: "fast" becomes a euphemism for death-wish, "quiet" means mudlark, and balanced still includes far too much rough-stuff for anything short of a mountain-bike.
The Cyclestreets algorithm, in a nutshell, seems incapable of detecting and prioritising the country lanes - which are a national treasure that provide the major component of any genuinely balanced and well-planned rural cycle route! Instead, whenever Cyclestreets finds itself in the sticks, it makes a beeline for the nearest NCN and slavishly follows it (regardless of its defects as a "balanced" route) until getting within striking distance of one's destination.
