I am looking for a way to automatically skip a waypoint while driving. I have a route from A to C via B. B is a little bit off the main route from A to C. When I, while driving, decide to NOT stop at B I would like the App to behave as if I have skipped B. The app Beeline works thats way. Can this be done with Kurvinger? Thanks.
When planning, make B as a “shaping point” (black marker) instead of “via point” (blue marker), then I think it should work the way you wish.
2 Likes
[DE] Du kannst es auch während der Navigation machen indem du auf die Einstellungen tippst (3 Punkte-Button) und dann auf “Überspringen”. Dann wird der jeweils nächste Punkt übersprungen. Ggf musst du noch auf Neuberechnen tippen.
[EN] You can also do this during navigation by tapping on the settings (3 dots button) and then on “Skip”. The next point will then be skipped. You may have to tap on Recalculate.
1 Like
Yes that works. Thanks.
It does however have a side effect : these point don’t show up in the info box with estimated arrival time and distance.
I have kind of solved it by adding some extra artificial intermediate points on the main road but ideally one should not have to do that.
1 Like
Yes but i was looking for a way to not use my fingers.
Could you clarify why you are interested in arrival times at random points? If the point has meaning to you then you would want to visit it.
We allow driving by Via Points so you don’t need to stop at the Via Point, but you need to come close to it in order to continue riding the rest of the route.
1 Like
I think in @Herman example, “B” is not a random point. It is an optional stop, (e.g., a coffee shop), where you do not necessarely need to stop, but would like to know that it is there if you feel tired and decide to have a break.
How close is “close”?
I have initially used named shaping points instead of via points to mark my optional stops on the route. This did not quite do the job, because they are not shown/announced when navigating. I missed 90% of them.
My second strategy was to make the optional stops as via points, but move them to the junction where I would need to leave the route and navigate to the optional stop, should I choose to visit it. This had the advantage of the stop being announced, however I failed to remember always where exactly I had to turn to visit them, which caused a bit of confusion in our group (some ppl already got off the bike, but the actual stop was a bit further away).
My third try was to place the optional via points on the side road, but then if it wasn’t close enough to the main route, they would not be “collected” an I had to do manual skip (also not a big deal). It would be helpful to know though, how close do I have to come to the via point, so that it counts as a visit and try to use it for better placement of optional stops.
@t00thl355 explains it very well. B in my case is an optional stop and while driving I might decide to stop there or not. I have solved it by having all my optional stops as shapepoints but to have an additional viapoint before the exit to the optional stop. The stop then is announced and i can follow the navigation instructions if i want to.
1 Like
That seems to be a good workaround.
Idea for Kurviger:
Would it be possible to announce named shaping points in navigation?
1 Like
I agree with @linux-user. This workaround sounds reasonsble.
There was already more or less the same proposal and usecase in December 2023.
As I remember the common sense was that shaping points should not be announced, not be shown in the announcement box, should be skipped autimatically, not be zoomed, …
Not because there is a god given rule, how shaping points must behave, more as this behaviour is known from other navigation software.
Finally the functionality was released in beta 3.3.0 in March 2024!
It seems to me it is not as easy to just add a label and one some line of code. Navigation is affected, Zoom-behaviour, perhaps the list of shown turn instructions (as a shaping point with a text should in some kind behave like a via-point), probably more.
Perhaps it is an use case as in Planned Feature / proposal [Audio Point](https://forum.kurviger.com/t/wunsch-audio-point/14271) from @Hobbyfahrer?
“If you are hungry, follow the route. Otherwise turn right right and follow destination to Stuttgart”.
1 Like
I “feel” that this would be a work around for a sideeffect of another workaround. In stead i would prefer see that via points get a flag to indicate that they are optional. This meaning that if I am on the route to viapoint C again (after skipping viapoint B) that the app does not try to navigate me to B.
Audio points are a great idea.
And please don’t misunderstand my post above.
I have always been and still I am a fan of that shaping points can be announced. At some point I understood that beyond Kurviger, a behavior is expected for each waypoint type (including gpx data exchange). This can be documented without much if’ and but’s.
Audio point is already something like a new waypoint type in addition to the existing ones. Does Garmin already offer something in its extensions? The requirement doesn’t seem that unusual to me.
May it could be an option, via points could be switch between mandatory and not.
It’s < 1km and > 100m - we haven’t documented it so that we can change and finetune this 
. The idea is that if you for example pick a VP and you are only on the parking area and not directly at the VP, this still counts as visited.
Unfortunately not.
Yes exactly, that will introduce a lot of complexity. But it’s not just programmer hassle (we can handle that), it is something we need to explain and document as well. I am not sure if this will make things just too complicated and in the end either nobody uses it or it gets used wrongly and leads to frustration.
Yes, that might be a good workaround 
1 Like