Kurviger.de | Application | Blog | Frequently Asked Questions (FAQ) | Legal Notice | Privacy Policy

App: Improve rerouting settings

Thanks for the detailed description.

Note that allowing via points and shaping points to have the same weight in rerouting,
then nearest / next waypoint (also in strict) will be any of both: a via or shaping point.

Navigation panels will show distance and time to next any of via or shaping points.
And top-left nav panel will show direction / distance to any of via or shaping points.

There cannot be half solutions in rerouting vs UI, any change will affect all of them.

1 Like

So the most sane (and expected) options seem to be(?):

  • Nearest waypoint
  • Strict navigation
1 Like

Ich brauche nur den

“nĂ€chsten unbesuchten Wegpunkt”

wenn ich mich verfahren habe.

Nearest or next, one of them.

[DE] Das sind die Optionen die wir z.Z haben:
Siehe meine ErklÀrung oben
[EN] These are the options we currently have:
See my explanation above

Vielleicht verwirrt ja auch die “etwas unprĂ€zise” Übersetzung ins Deutsche:

  • Nearest route point = NĂ€chstgelegener (oder nahester) Routenpunkt
  • Nearest waypoint = NĂ€chstgelegener (oder nahester) Wegpunkt
  • Next waypoint = NĂ€chster (oder folgender) Wegpunkt

“Nearest waypoint” is calculated after exit, so it’s the nearest of next ones, seems the logical choice.

1 Like

Dann ist das wohl OK so :slight_smile:
Denn der nÀchstgelegene Wegpunkt könnte auch der sein, den ich eben verlassen habe.
Ich möchte vermeiden, dass ich zu einem schon erreichten Punkt zurĂŒckgefĂŒhrt werde oder, z.B. bei Umleitungen, in einer Schleife stecken bleibe.

Ich nutze nur “Folgender Wegpunkt” :sweat_smile:
I only use “Next waypoint” :sweat_smile:

@linux-user summarized nicely all options above.

The main difference between “Next waypoint” and “Nearest waypoint” is that “Next waypoint” leads back to last omitted waypoint, like “Strict navigation” but more flexible, so it’s already covered there.

While “Nearest waypoint” leads to the nearest of all “next” waypoints, seems what most navigators offer and so what most users expect.

We should also think about the history, and why we got all these rerouting options.

  1. At the beginning we had only “nearest waypoint” - the flexible version
    (well and nearest point on route)
    Then users complained that waypoints may be automatically skipped; see Rerouting changes the planned route

  2. As a solution we got “Next waypoint” (formerly called next unvisited waypoint)
    Then users discovered, that you still can create situations where waypoints are skipped

  3. So we got “strict navigation” - the strict version.

For users to understand the intention of this rerouting options and also for easy documentation we shoud only keep a strict and a flexible version.

Wir sollten auch ĂŒber die Geschichte nachdenken, und darĂŒber, warum wir all diese rerouting Optionen bekommen haben.

  1. Am Anfang hatten wir nur den “nĂ€chstgelegenen Wegpunkt” - die flexible Version
    (naja, und nÀchstgelegener Punkt auf der Route)
    Dann beschwerten sich Benutzer, dass Wegpunkte automatisch ĂŒbersprungen werden könnten; siehe Rerouting changes the planned route

  2. Als Lösung erhielten wir “NĂ€chster Wegpunkt” (frĂŒher “nĂ€chster unbesuchter Wegpunkt” genannt)
    Dann entdeckten Benutzer, dass man immer noch Situationen schaffen kann, in denen Wegpunkte ĂŒbersprungen werden

  3. So haben wir also die “Strikte Navigation” bekommen - die strikte Version.

Damit die Benutzer die Intention dieser rerouting Optionen verstehen und auch aus GrĂŒnden der einfachen Dokumentation sollten wir nur eine strikte und eine flexible Version beibehalten.

Übersetzt mit www.DeepL.com/Translator (kostenlose Version)

 und kleinen Korrekturen von mir :wink:


Thanks, some options were added to help until the proper ones are implemented.

(2) indeed seems like the (temporary) step towards proper implementation of (3).

That reduces complexity also in app maintenance, my concern for the future

We should have in mind that since “Next waypoint” is currently the default, most users “report” to use that option. Important is if they tested all options and understand the differences and what they need.


I will test the strict mode today on a roundtrip with crossing sections. The other flexible options are also useful in other situations, for me less on a complex roundtrip if you want to catch all planned curvy roads. In any case I find it excellent that this flexibility is offered and realized.

Available in Kurviger 1.13.6 (Beta).


is it possible that there are currently only two options for route recalculation?

next waypoint and strict navigation

I have now tried several times to drive a round trip with a detour. As soon as the recalculation starts the whole tour is gone, from 280 km it is only 14 km to the finish. My route has only 2 waypoints, one where the entrance stands and once refueling after about 120 km

It doesn’t matter if online or offline (BRouter).

Am I doing something wrong in the settings ?



Can you post a route sample and where exactly your rerouting happens?

If want to follow strictly the route, then can select strict navigation option.

Or if select the other option, what exactly expect as result after rerouting?


the file
Rundtour 10_Mai 2020_2.kurviger (30.7 KB)

Screenshot on smartphone (I use it to optimize)

After take the wrong exit from the roundabout


Thanks for the example.

What rerouting mode you had selected, “Nearest waypoint”?
Round trips are handled better with “Strict navigation” option.

Or mean to replace “Nearest waypoint” with “Next waypoint”?


I’ve been riding with IGo for a long time. The main reason to use the kurviger Pro is the fact that it now has different waypoint variants, similar to Garmin.

Forming points, which define the route but don’t have to be driven to, and waypoints which have to be driven to in any case, because break, refueling etc. are stored, no matter if you took a detour or a wrong turn. But in principle the navigation must always try to follow the planned route as far as possible.