Hello again! I found a couple times on the past few rides the algorithm takes me on a short (100-300m) diversion before finally joining up to the (larger) road i need to ride. (Between the 22-23km mark on the attached route) I understand the aim is to avoid major roads if possible, but maybe you can tweak it such that, if the route only skips, say, 300m or less of the main road (maybe even 500m), you could just route us onto the road directly. It's easy enough to deal with on the fly, but, as the distances are so short, I rarely notice them before I get to the decision point.
Comments
Thanks – that’s a useful example. The way the routeplanner works doesn’t really lend itself to that sort of routing decision I’m afraid: effectively, at the planning stage, it doesn’t have any memory of where you’ve been previously, so it can’t figure out that you’ve gone off then back onto the same road. But I’ll keep this filed away as an example that could perhaps be fine-tuned in the future.
It’s easier in much of Western Europe because we have real traffic data that helps cycle.travel know which main roads are busy and which ones are ok to cycle on. That data isn’t readily available for Eastern Europe but I live in hope!