Ups, sorry my fault
Available in Kurviger 1.13.4 (Beta).
Tested importing waypoint names for gpx and itn files. Works great.
Shaping Point feature is also great. Works but not tested with togehter with rerouting.
Wunderlinq integration will be tested, when i got it. Currently arrived in germany.
Many thanks from my side and keep up the good work.
From my point of view this is the best routing app on android for bikers.
Wurde das jetzt schon bei der 1.13.4 eingearbeitet?
That is included too in Kurviger 1.13.4 (Beta).
Navigate along the route without shortcuts, i.e. follow the route strictly from one waypoint to another. When go off route, the rerouting tries to resume to the last omitted waypoint.
Available in “Settings | Navigation | Rerouting mode”.
- Various improvements
Strict navigation is a very good improvement. Yesterday i ride a route where the way back crosses the route. Rerouting deletes all waypoints and wants me to navigate back home( last waypoint). I had to stop and reload the route after the crossing.
I am not sure about the other options, if they are all needed.
Keep up the good work.
Ich habe heute die “Strikte Navigation” ausprobiert. Sie macht das was Sie soll, das ist soweit gut. Allerdings gefällt mir “Folgender Wegpunkt” besser. Der Grund ist, ich habe Wegpunkt 1 ausgelassen, bin die Route aber weitergefahren. Habe die App neugestartet, da mein Ton weg war. Mit “Strikter Navigation” wollte er halt immer zu Wegpunkt 1 zurück. Wenn Routen-Neuberechnungsmodus bereinigt werden sollte, wäre ich dafür das “Folgender Modus” und “Strikte Navigation” bleiben. Die anderen beiden Punkte habe ich noch nie benutzt/gebraucht …
I tried strict navigation today. She’s doing what she’s supposed to, which is good so far. I like “Following Waypoint” better, though. The reason is, I left out waypoint one, but continued the route. Restarted the app because my sound was gone. With “Strict Navigation” he always wanted to return to waypoint 1. If route recalculation mode should be cleaned up, I would stay in “Following Mode” and “Strict Navigation”. I have never used the other two points before …
What is the difference between “Next waypoint” and “strict navigation”? For me those two options are not understandable intuitively.
Is “Next waypoint” still “Next unvisited waypoint” (as it was before)? And does “Strict navigation” mean that it additionally considers shaping points?
Navigation (and rerouting) with “Next waypoint” is not strict, can still exit and resume route anywhere skipping intermediate waypoints automatically.
Cannot do that with “Strict navigation”:
“Navigate along the route without shortcuts, i.e. follow the route strictly from one waypoint to another. When go off route, the rerouting tries to resume to the last omitted waypoint.”
“Unvisited” was a false term based on the above description.
Shaping points are considered after next waypoint, like discussed here for all rerouting modes.
Concerning strict navigation I am over the moon. Unfortunately not about the weather, because that prevents me from trying it out right away. It works well when simulating. Even the manual skipping works like expected. I am confident that this will also work well in real operation. The next complex round trip is mine.
Thanks for your explanation. If I’m using “strict navigation” and am forced to leave my route, will I then be navigated to the next omitted waypoint regardless what type it is (regular or shaping wapoint)? Or will I be navigated to omitted regular waypoints only? My question is related to my former posts concerning this function (like here or here). Or from other users (like here).
Shouldn’t it have rerouted to nearest point on route at start of navigation?
Ich bin am Anfang mit “Strikte Navigation” gefahren, auch nach dem “Neustart”. Erst als ich ca. 2 km am WP1 vorbei war und Kurviger immer noch zu WP1 wollte, was in diesem Modus ja richtig ist, habe ich wieder auf “Folgender Wegpunkt” umgeschaltet.Worauf hin Kurviger zum WP2 sprang.
I drove with “Strict Navigation” in the beginning, even after the “Restart”. Only when I had passed SS1 for about 2 km and Kurviger still wanted to go to SS1, which is correct in this mode, I switched back to “Following Waypoint”, whereupon Kurviger jumped to SS2.
Does this description explains that better?
Navigate along the route without shortcuts, i.e. follow the route strictly from one via point to another. When go off route, the rerouting tries to resume to the last omitted via point.
Essentially like discussed and agreed here, the shaping points are considered after the first via point that participates in rerouting.
Do we need all this rerouting options
I think at the end two options should remain:
- a flexible one, which allows automatic skipping of waypoints that are “behind” you.
- a strict one, which doesn’t omit waypoints.
See my comment here
(App: Rerouting options)
(we can also discuss that in the relevant topic)
I am available for changes if there is enough feedback - not many have participated so far.
Are there any DIS-advantages?
If not - me I always prefer more options compared to less.
Ein Mehr an Auswahl kann aber Nutzer abschrecken, wenn es zu viel wird. Zumal ich nicht denke das sich Alle die FAQ oder das Handbuch durchlesen. Ich denke die Meisten werden sich, so wie ich, die App installieren und losfahren wollen. Ohne sich groß Gedanken machen zu müssen welche Einstellungen Jetzt die richtigen wären. Deswegen finde ich Weniger aber Bewährtes persönlich besser.
However, more choice can deter users when it becomes too much. Especially since I don’t think that everybody reads the FAQ or the manual. I think most of them will want to install the app and get started, just like me. Without having to think about which settings are the right ones now. That’s why I personally find less but proven things better.
This we had discussed often in this forum as well.
WHO’s the one to decide, which options are more useful and which are less useful?
Only in very few cases can an agreement be reached.
And then any restriction of options is a loss for at least one part of the target group.
Therefore, it is better to leave the options as they are, if they have already been implemented by the developers, i.e. do not require new efforts.