# App: Navigation improvements **URL:** \ **Category:** Implemented features\ **Tags:** implemented\ **Created:** [August 18, 2021, 8:29am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628 "2021-08-18T08:29:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![rumbrummer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/rumbrummer/32/113_2.png) [@rumbrummer](https://forum.kurviger.com/u/rumbrummer)\ **Post date:** [August 18, 2021, 8:29am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/1 "2021-08-18T08:29:12Z")
> [@Rundtour wird nicht wie geplant zu Ende gefahren](https://forum.kurviger.com/t/rundtour-wird-nicht-wie-geplant-zu-ende-gefahren/6608/16): > > It is already explained in the other topic (round trips): I read that before writing my previous proposal, of course - but I do not fully understand the background. But there was a similar topic with round trips on older Garmin devices: Bad GPS coverage or deviation from route @ start lead to direct routing to destination (skipping nearly the whole route). Garmin has (from my point of view) solved this with introduction of Via points and Shapingpoints: You have to reach each Via point, before the switch to next route leg is done (a leg is the part from one Via point to next Via point) - a manual switch by skipping next ViaPoint is possible. So using some Via points in loops of the route avoids problems in round trips, trips having loops, an “8” (crossing itself multiple) and so on. Recalculation of route during navigation means staying on same route leg - as long as you reach next Via point. Consistent to that starting a route you can choose at which Via point to enter the route. But I am aware of that implementing such a strategy in Kurviger App might be a huge effort, because it touches basic navigation strategy … ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [August 18, 2021, 8:38am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/2 "2021-08-18T08:38:21Z")
These seem to be interesting ideas, there may be navigation improvements in the future. ---
**Author:** ![Tom](https://forum.kurviger.com/user_avatar/forum.kurviger.com/tom/32/168_2.png) [@Tom](https://forum.kurviger.com/u/Tom)\ **Post date:** [August 18, 2021, 9:52am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/3 "2021-08-18T09:52:16Z")
Asking for a wp number to start a tour when reloading a tour sounds nice. I only drive with option “strict navigation”, because I want to have control which wps to skip. The only problem there is when I want to skip several wps at once, then the calculation is not interrupted. I have to wait until the calculation after the first wp skipping was finished. With poor bandwith and no automatic switch to Brouter this can take a long time. Don’t know if this is possible: I find it better to cancel calculation when a further wp is skipped and directly start with new calculation considering that possibly 2 or more wps have been skipped already within a short time. ---
**Author:** ![0709](https://forum.kurviger.com/user_avatar/forum.kurviger.com/0709/32/4699_2.png) [@0709](https://forum.kurviger.com/u/0709)\ **Post date:** [August 19, 2021, 6:40am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/4 "2021-08-19T06:40:59Z")
> [@Rundtour wird nicht wie geplant zu Ende gefahren](https://forum.kurviger.com/t/rundtour-wird-nicht-wie-geplant-zu-ende-gefahren/6608/19): > > I will think about possible improvements, you can write ideas in the topic Briefly. - **No (auto)recalculation:** That Kurviger can’t start navigation even when correctly positioned onto the last track segment toward the target Via Finish Point is _remarkable_. - **(Auto)recalculation (due to off track or by a manual trigger):** If resulting in an unexpectedly bad route trajectory proposal pse to be able to reject by offering an ‘ **undo** ’ function. _The very similar Locus (gpx) track navigation mode uses a gpx track with attached turn instructions & Via Points. At any “on track” position a navigation (re)start is possible without refusal nor hassle._ _By the way._ _The big advantage (as with the similar Locus gpx track mode) is that track navigation is immediately ready to operate without any (re)calculation as the necessary turn instructions and Via Points are already attached in the file. It is only when you subsequently change the trajectory, for whatever reasons, that you need a (re)calculation. Without route change, the file method is stable and independent of any mobile router machine(s) or routable map. A pure (Locus) track navigation can even be done without a map (or a blank) present. (Ideal for off road trajectory designs)_ ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [September 7, 2021, 2:17pm UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/5 "2021-09-07T14:17:58Z")
> [@rumbrummer](#): > > You have to reach each Via point, before the switch to next route leg is done (a leg is the part from one Via point to next Via point) - a manual switch by skipping next ViaPoint is possible. This is already available with “Strict navigation” option. Kurviger allows to _start_ the strict navigation anywhere, _then_ you must pass the waypoints in the correct order. * * * > [@Route verpasst nach erneutem Laden der Route](https://forum.kurviger.com/t/route-verpasst-nach-erneutem-laden-der-route/5269/14): > > Navigation currently cannot start on the last route leg (after the last waypoint). > > This is to help with complaints that navigation ends when it starts in round trips, > because start and end points are near, so the exit and entry paths are the same. Perhaps this could only be active in “Strict navigation”. ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [September 14, 2021, 9:49am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/6 "2021-09-14T09:49:49Z")
> [@Route verpasst nach erneutem Laden der Route](https://forum.kurviger.com/t/route-verpasst-nach-erneutem-laden-der-route/5269/14): > > > [@Route verpasst nach erneutem Laden der Route](https://forum.kurviger.com/t/route-verpasst-nach-erneutem-laden-der-route/5269/14): > > > > Navigation currently cannot start on the last route leg (after the last waypoint). > > > > > This is to help with complaints that navigation ends when it starts in round trips, > > > because start and end points are near, so the exit and entry paths are the same. > > Perhaps this could only be active in “Strict navigation”. - The restriction only applies to “Strict Navigation”. Available in [Kurviger 2.1.7 (Beta)](https://forum.kurviger.com/t/kurviger-2-1-2-beta/6848). ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [October 6, 2021, 11:27am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/7 "2021-10-06T11:27:43Z")
4 posts were split to a new topic: [App: Strict route following](https://forum.kurviger.com/t/app-strict-route-following/6989) ---
**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\ **Post date:** [October 31, 2021, 2:26pm UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/8 "2021-10-31T14:26:24Z")
Implemented in [Kurviger 2.1.11](https://forum.kurviger.com/t/kurviger-2-1-8/7071). ---
**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\ **Post date:** [October 9, 2024, 10:28am UTC](https://forum.kurviger.com/t/app-navigation-improvements/6628/9 "2024-10-09T10:28:15Z")