Imported routes from Kurviger are always recalculated
It should work. Are you using the 'Send to Scenic' button in Kurviger?
If you are and you still get this result, could you send me the Kurviger URL of one of your routes, so I can try myself?
Quote from Guido on 25.10.2021, 13:44Could you send me the Kurviger URL of one of your routes, so I can try myself?
Hello Guido,
I have the same problem and after reading
https://scenic.app/forum/topic/not-happy-w-imports-from-kurviger-de-completely-different-result/
and
https://scenic.app/forum/topic/not-happy-with-imports-from-kurviger-de-different-result-part-2/
I thought that this is a known problem.
If you would like so see even more examples, here is Kurviger route:
https://kurv.gr/X2GLZ
I have chosen "fastest route" on purpose because I don't want to have senseless detours.
This is what Scenic looks like after importing my route:
This is a complete mess. There are 12 shaping points which I have not placed, some of them in cities I don't want to drive to (e.g. the vias 13, 14, 15, 18, 20 in the Scenic screenshot). The shaping point 1 has changed to a stop (Zwischenziel). The route lenght has changed from 66.8 km to 86 km.
What is wrong here? I oftenly make very detailed plans of my routes and I just want to have the exact route in the Scenic app. What should I do?
Best regards,
Spoony
You are right. This is a mess indeed. My apologies.
I spend some time analyzing this case and found the bug. An App update is required to resolve it.
Scenic 3 ( https://scenic.app/help/scenic-3-info/ ) is almost ready to be released. I will make sure to add this fix as soon as possible.
Meanwhile, as a workaround, if you make sure the start and end point are more than 50 meters apart, you will get the same route in Scenic.
Sometimes you will need to change routing mode to short, or add an extra via point, but that would be the maximum you need to do. With this workaround the blue line in Scenic will always match the Kurviger route 1-to-1.
Here's your route, with the end point shifted a bit: https://kurv.gr/bdaRS
And here's what it looks like after importing (and changing routing mode to short):
Scenic will always replace Kurviger shaping points with its own shaping points. This is necessary because Scenic needs more shaping points to make the route follow the roads you intended (because Scenic uses other map data and another routing algorithm than Kurviger).
Kurviger via points will always be migrated to Scenic stops 1-to-1.
Hope this helps / explains.
Apologies to you and all others who were affected by this. If you have any further questions, please let me know. Happy to help!
Best regards,
Guido
I imported the route and indeed saw slight deviations between the blue route (the exact track of the Kurviger route) and the magenta (calculated by Scenic) route. These however can be corrected manually.
I realize this can look a bit daunting at first, but once you understand why this is happening and how it can be corrected, you'll find it's pretty easy and fast. Correcting this route took me less than 5 minutes.
The first thing you'll notice is that Scenic replaces the Kurviger shaping points with its own via points, and that there are many more via points. Scenic via points are basically Scenic's version of Kurviger's shaping points. They are only used to force the route to take certain roads. Why does Scenic add so much via points? Because Scenic has a different routing algorithm then Kurviger. By adding more via points it tries to ensure the same roads are used.
If shaping points are used in Kurviger with that in mind (only to force routing to take certain roads), Scenic replacing them and adding some is not an issue. Stops however are important, and Scenic copies them over from Kurviger.
So, the 9 Kurviger Stops (points 2, 4, 5, 7, 9, 10, 11, 12, 15 in Kurviger) are translated by Scenic to Stops 1 through 9.
So far so good.
Now, you'll notice in Scenic that the blue line is exactly the route as it was designed in Kurviger. The magenta line is the route that Scenic calculates between the vias and stops. Typically they should overlap, but sometimes adding, or moving a via point is required to get them matching. This is because of the difference in routing algorithm as explained above. More detailed on why this is, you can find here if you like: https://scenic.app/help/strange-loops-while-importing/
So, manually correcting is sometimes necessary. Especially with curvy routes not taking the 'obvious' fastest or shorter route, this is necessary.
So, let's do that for this route. I do this by zooming in and dragging the map along the route.
The first discrepancy that we find is around vias 16-18. Scenic takes the main road, while Kurviger intended to take the smaller road.
We correct this by slightly moving vias 16 and 18 like so:
Next discrepancy is before via 19:
We correct this by adding a new via where the crosshair is (using the 'Via X') button:
There are a few more like these that can be corrected similarly.
There is one map error in this route, at Dooley / Dorchester Junction:
This, unfortunately can not be corrected, because Scenic, unlike Kurviger, believes you can not go, or are not allowed to go on the 'blue' road. Or Scenic might think there is no road there at all. This is a map error on Kurviger side or on Scenic side. I don't know the region, so I can't know for sure. If it's a Scenic map error, you can report this directly to Scenic's map provider HERE map: https://scenic.app/help/roads-not-on-the-map-errors-in-the-map-data/
For this route I left the magenta line like this, and made a few more corrections further down the route.
I found one other strange anomaly where Scenic seems to have the better route compared to Kurviger. I guess Kurviger's algorithm wants you to get that extra 'curve' here around 'Roses Hill'
Scenic keeps you on Patrick Henry Highway there, which I assumed is what you'd want, so I did not change that.
So, here is your route, completely corrected, except for the one map-error point mentioned above: https://scenicapp.space/route/RLrhJUNQ You can import it to your Scenic account through this link.
Now, a few more points to note:
- For this route, it would probably have been better to change the routing mode to short, before starting the manual corrections. With that, probably less manual corrections would have been required. Perhaps this is an improvement point for Scenic as well (to set routing mode to short when importing a route like this). I'll take another look at that and make changes in an update if that proves to be better.
- Kurviger's algorithm is just that. An algorithm. It analyses the curves in the roads and tries to give you curves. Sometimes this might not be what you want. For example in urban situations, it might send you downtown because it's curvier, but give you more traffic lights and junctions. So, it's always good to double-check what route Kurviger (and Scenic for that matter) generate.
- This route is rather long. I assume it's a multi-day trip? While it is possible to navigate this route with Scenic, I recommend to make one route per day. It's easier and more manageable to make one route per day. It will recalculate faster if you deviate from the route. Also assuming you'd want to stop Scenic during an overnight stop, you could just start the next route on the next day.
- If you are unsure about how to use the power planner in Scenic, a new tutorial video was just released: https://scenic.app/help/power-planner-tutorial/
Hope this helps/explains. If not or if you have other questions please let me know. Happy to help.
Best regards and ride safe,
Guido
