Navigating Furkot Routes
Hi Guido,
As @wilkohd said, I am having the same exact issue. I assume the reason for so many waypoints was to prevent rerouting when calculating. Here is one of the routes I used that had this issue:
And of a screenshot of how it looks on import directly from the app:
I would just like to add outside of this navigation issue, I am very pleased with how well this app works especially with the integration with Furkot!
Thanks,
I fully understand, but unfortunately can't solve it technically at this point.
This is fixable manually during import though. I'll explain more below.
So, there are two things going on here:
- Scenic's map framework (HERE maps) has a 'feature' where it gives turn instructions for upcoming vias and stops. For stops you typically want that, for vias you don't. This 'feature' can not be turned off so I worked around it partially, like so: Whenever a turn instruction for a via point is coming up, I ignore it, and show the next turn instruction. The framework only gives me the next two upcoming turn instructions though, so I can not ignore all of them if there are two via points in a row (without actual turn in between), because I wouldn't have a turn instruction to show at all.
For most routes this 'workaround' works fine. Because manually created routes don't have that many via points. They only have the necessary ones to force the route to take certain roads. Meaning, if I ignore a 'via point' instruction, the next instruction is mostly a real turn instruction.
- This route however is (1) created by Furkot which supplies many via points (613 for just the Day 1 part), and (2) contains quite some very long stretches on the same road, without a turn. This combination of many via points and long stretches on the same road, makes it so that there are multiple via points between two real turn instructions. And that's where the via point instruction will show up on the screen.
Scenic does reduce the number of via points (in this case from 613 to 122), but this doesn't solve the problem entirely. This reducing of via points is done by an algorithm, which takes out via points in a 'smart' way. The thing is that this 'smart' way has to work for both very curvy routes through compact city centers in Europe, as well as through long stretched routes like the one here (and there are many more variaties of routes). As a result, .. for this route, it doesn't take out enough via points. I could create the same route manually with far less via points.
I'll see if I can improve the algorithm in the future, but meanwhile you have two options:
- Accept the via point turn instructions or
- Manually remove via points during import. Actually this is quite simple and, with some practice you can do this very fast. It took me less than 5 minutes to do this for your Day 1 route. Here is the result in Scenic: https://scenicapp.space/viewRoute.php?rid=rdoRVeUH As you can see it only has 25 via points, and the route is still the same.
So, how did I do this? Well... in this case, because it had so many via points, I decided to remove all via points first (under the 'more' button there is a 'remove all vias' button):
This left me with a blue track and a magenta route. The blue track is the exact track that Furkot gave. The magenta line is the route that Scenic calculates between the vias and stops. As you can see, they are not the same (because I removed all the vias)
So, then I just started adding via points to make the magenta route follow the blue track.
Here is another post on this if you like more info:https://scenic.app/forum/topic/imported-routes-from-kurviger-are-always-recalculated/#postid-4138
Also check out the tutorial video, accessible through the top left 'info' button.
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
