Hi all, unfortunately Kurviger still can’t manage correctly if a round trip contains crosswise routing. Even if the setting in routing mode is next unvisited waypoint, this doesn’t work. [Screenshot_20200419-165020_Kurviger Pro] Here is the planned route #1 Runde Südpfalz.kurviger (28.4 KB) and here the track Südpfalz Track.gpx (575.6 KB) Normally Kurviger should guide from wp4 to wp5, but as soon as it reaches the cross-over, it guides to wp17, thinking I am on the way back. [grafik] Instead of guiding from wp4 to wp5 (green arrow), it guides to wp17 → 1st problem [InkedScreenshot_20200419-103040_Kurviger Pro_LI] When starting to turn around and driving to wp5 (= wp13 in the track), it suddenly deletes all wps from wp5 to and including wp16, which means my complete route is lost → 2nd problem I had to stop and re-import the planned route… but it doesn’t brings me back to wp5, because it has “forgotten” that I had already visited all wps till wp4 -->3rd problem I should have deleted all previous wps? A mess without proper spectacles. The consequence was that it routes me to a new destination (maybe it thinks wp1 would be my next wp) and I lost my complete path. Green Arrow was the planned route. [grafik] Further on the route after I have found again the way by manually deleting wps (which was alone very bad because 5 bikes behind me were waiting until I sort out the app problems), it completely ignores a big beautiful round [Screenshot_20200419-172546_Kurviger Pro] Instead of guiding from wp6 to wp7, it directly took the way to wp10, completely ignoring wp7,8 and 9. This is really not what I am expecting when the setting is “routing to next unvisited waypoint”. It simply doesn’t work. Kurviger should simply KEEP the sequence… also when the route contains crosswise waypoints… after wp4 there is wp5 and not wp17!! And after wp6 the next wp is wp7 and not wp10!! And it should keep knowing the already passed wps when I have to reload the planned route because Kurviger unattendetly deletes wps. I hope you can sort this out.

[imagen] Tom: How long will it take for such an option? There is no ETA for any feature, when there is free time and will, then could be implemented.

Ok, then I have to further wait… hopefully not too long… (just thinking loud)… at least good to know that the problem is understood and there could be a solution. Of course for such an option 4 - strictly follow wps in sequence, the manual (in no way automatic) deletion via the context menu should also work, but I think that’s normal… just want to mention it in case if not. PS: also of course such an option also recognize when I have for example don’t set the wp exactly to the street… this can of course be automatically corrected (meaning if I have set it 10 meters or so besides the street), then it can be treated as passed… but I think this is already handled very well in Kurviger.

[imagen] Tom: There is a difference between simulation and live routing Sure, but I doubt that this was the reason here. [imagen] Tom: Even if I had missed it, with routing option “next unvisited waypoint” it should recognize that I have missed the direction to wp5 and send me back to wp5 instead of further route to wp17. Wouldn’t you agree? No, you left the route shortly before WP17, to me it would make that Kurviger would reroute you to WP17. You skipped Waypoints 5-16. If you had done this intentionally you would complain that Kurviger is not rerouting you to WP17. [imagen] Tom: This doesn’t help either because it would “assume” that I am on the return and further route to wp17 instead of telling that I am wrong and first have to pass wp5 How would Kurviger know that? It can’t guess your intentions. The default behavior is to allow skipping parts of the route, which is awesome and extremely flexible. That’s the intended behavior, the other option is the strict routing where you have to visit every waypoint or even every part of the route. [imagen] Tom: In fact Kurviger is the only app which I know which ignores that, skips all interim waypoints and drives to the distination. Unless you configure Kurviger to that, that usually doesn’t happen. There are very few roundtrip scenarios where this can happen. [imagen] Tom: I would expect the routing engine to guide me back to wp7 instead of heading to wp10. That’s what should happen. As noted previously, I can’t reproduce the behavior you describe, so I have no idea why it behaved that way.

[imagen] boldtrn: No, you left the route shortly before WP17, to me it would make that Kurviger would reroute you to WP17. You skipped Waypoints 5-16. If you had done this intentionally you would complain that Kurviger is not rerouting you to WP17. probably this happened… probably Kurviger guided to turn left and I took the magenta left instead of the green left [grafik] But no, I wouldn’t complain if Kurviger would not route to wp17, not with the “next unvisited waypoint” mode, since I thought this would already be the strictly follow wps in sequence mode… obviously it is not (just learned 15 minutes ago). [imagen] boldtrn: How would Kurviger know that? It can’t guess your intentions. The default behavior is to allow skipping parts of the route, which is awesome and extremely flexible. by knowing that I have activated option 3 and not 1 and 2 [imagen] boldtrn: That’s the intended behavior, the other option is the strict routing where you have to visit every waypoint or even every part of the route. You are talking as if this option already exists. I understand devemux86 that it’s not. [imagen] boldtrn: Unless you configure Kurviger to that, that usually doesn’t happen. Don’t understand this. How can I already now configure Kurviger to not skip wps? [imagen] boldtrn: That’s what should happen. But it doesn’t, see track picture. According to my planned route Kurviger should have taken the direction of the green arrow [grafik] this was the planned route. Kurviger completely skipped wp7,8 and 9 without telling to turn right. [grafik] [imagen] boldtrn: I can’t reproduce the behavior you describe, so I have no idea why it behaved that way. Nevertheless the problem exists. I guess devemux86 has at least understood the problem. Can you please get in touch with him? Ok, you say you and I understand that you want that flexible mode of skipping wps. Fine, but for me this is an only disappointment if Kurviger automatically skips wps. If this is option 3, I have no other chance than to accept it and ask for an option 4 - strictly follow waypoints in sequence (just including manual skipping of waypoints via context menu - exists already).

[imagen] Tom: by knowing that I have activated option 3 and not 1 and 2 No, don’t just think about this specific scenario. Think about other scenarios as well. For example you have to go off the route because of a road blockage. You have a waypoint on the road blockage. Now you get back to the route and did not visit this waypoint. Should Kurviger try to route you back to that waypoint? Certainly not. [imagen] Tom: You are talking as if this option already exists. I understand devemux86 that it’s not. It’s not implemented yet. [imagen] Tom: Don’t understand this. How can I already now configure Kurviger to not skip wps? I think that option was removed, you could recalculate the route to the destination. [imagen] Tom: Nevertheless the problem exists. I guess devemux86 has at least understood the problem. Can you please get in touch with him? I understand your problem description. But I can’t reproduce it. So I can only guess why Kurviger didn’t tell you to turn. At that point you already started to change your planned route.

[imagen] boldtrn: For example you have to go off the route because of a road blockage. You have a waypoint on the road blockage. Now you get back to the route and did not visit this waypoint. Should Kurviger try to route you back to that waypoint? Certainly not. It will with strict route following, there cannot exist and should not wait any flexibility there.

[imagen] boldtrn: No, don’t just think about this specific scenario. Think about other scenarios as well. For example you have to go off the route because of a road blockage. You have a waypoint on the road blockage. Now you get back to the route and did not visit this waypoint. Should Kurviger try to route you back to that waypoint? Certainly not. Of course if I talk of an option 4 I would like to also have the manual options via the context menu available as told. I there is a road block, I still can use avoid roadblock and if I need to skip 1, 2 or more wps, I would like do this manually, not automatically. [InkedScreenshot_20200420-140641_Kurviger Pro_LI] [imagen] boldtrn: I understand your problem description. But I can’t reproduce it. So I can only guess why Kurviger didn’t tell you to turn. At that point you already started to change your planned route. I was not starting to change the route, I just missed the right left turn from 2 which are close together and this is exactly what I expect a navigation system to correct for me by telling to return and guide me to the path back of the planned route. [imagen] boldtrn: I can’t reproduce the behavior you describe, so I have no idea why it behaved that way. I guess you are talking of the change between wp4 and wp5, but what with skipping wp 7,8 and 9? There is no reason for doing this.

[imagen] devemux86: It will with strict route following, there cannot exist and should not wait any flexibility there. Not automatic, but hopefully still manually by using the context menu.

@devemux86 since this is really important for me, can you confirm that even with an option 4 - strict follow route the manual context options will still work? What I like for example much better as in Navigon is that the wps are numbered. In Navigon Cruiser for example you can also set many wps and they are strictly followed. It always guides me to my planned unvisited waypoint [Screenshot_20200420-141834_Cruiser 1] and if I want to skip a wp I can on the run, not needing to stop, just wipe to the left [Screenshot_20200420-141729_Cruiser 1] and use “Aktuelles Ziel überspringen” (skip next waypoint) and directly get a new calculation. If I want to skip more wps, I just use this quick link again. If I want to check the result I just use “show complete route” and can see that it was correct and follow my way. It’s a matter of seconds, not needing to go into submenus or to stop driving. Navigon Cruiser has other issues for examples it get stuck sometimes when using overlaying apps. Kurviger is stable and doesn’t get stuck with overlaying apps… big benefit. If this option 4 - strictly follow route (with manual skipping wps option via context menu would come into Kurviger I am the happiest motorcycle driver in the world. :innocent: :wink:

[imagen] Tom: can you confirm that even with an option 4 - strict follow route the manual context options will still work? Cannot make promises for unimplemented features, we’ll see in the future what is possible.

Rerouting issues

Discussion App

linux-user 20 Abril, 2020 13:09 26

That is obvious to me.
If you re-import the route, the app cannot know that you had already visited some of the WPs.

I had a similar issue, while testing “next unvisited WP” feature.
That’s why I suggested to change the behavior at navigation start.