strange routes when using curvy
Hello Guido,
Since the last update of Scenic I am experiencing a strange bug.
If I generate a route (select only one final destination) with curvy as the preference, via points are regularly generated that are not on the route (I have to drive back and forth on the same road). It seems to have something to do with rivers
I noticed this after the last update, but not before. I hope you can solve it, so far I am very happy with Scenic.
Thanks in advance,
small correction, even when there are no rivers "nearby"(very difficult in the Netherlands), Scenic does strange things.
The reason why this happens is that Curvy routes are generated. How this works is as follows:
Scenic's core routing engine is provided by HERE maps. They don't have a curvy routing mode. So what Scenic does is this:
- It contacts Kurviger.de, sending your start and end coordinate.
- Kurviger sends back a list of waypoints. These are waypoints you must pass to get a curvy route.
- Scenic then calculates the route between the waypoints, which gives you the curvy route.
Now, because Kurviger and Scenic use different maps and a different routing algorithm, it's possible that the roads that Kurviger wanted you to take between the waypoints, is not the route that Scenic calculates between the waypoints. Take for example your first screenshot:
I suspect Kurviger intended you to take a ferry between 19 and 20. But HERE (Scenic's route calculation) doesn't want you to take the ferry, or doesn't know there is a ferry. So, it finds another way to get you from via 19 to via 20. What you could try in this case, is, after generating the curvy route, change the routing mode to "short". Perhaps this will make Scenic take the ferry.
The other cases are basically the same. Maybe not with a ferry, but perhaps there is a road that HERE/Scenic doesn't want you to take, or Scenic doesn't know a road is there. Again, changing routing mode to short after the curvy generation might help in these cases too.
I know this is not a full solution, but I hope it explains and gives you some options.
Best regards,
Guido
