First point is often ignored

[MyZ51]

@Mzokk I like this idea, but if cruisers are navigating to a start point, like a large retail outlet using the app from their residence, it will take them to a point 1km away from the meetup location.

I suppose that’s ok if everyone knows to navigate to the starting location, then shut down the route to the meetup location, and start the new route leading cruisers to the via point 1 km away.

Chuck

[Herman Veldhuizen]

@M.-Schrijver I did some more testing related to nearest in another region with more mountains and while being somewhere halfway (not near the start). The app indeed finds a track point (when navigating as a track) or a waypoint (when navigating as a route) based on straight line distance. In both cases the result was not what I expected. Because of the mountain the time to those points was longer than the time to other points. It resulted in a route where part of it had to be driven in both ways. This is unrelated to the topic we are discussing here. So I have logged a ticket for support to look at and I suggest we leave that for now.

[RetiredWingMan]

All this discussion about WP1. I use my brain, when starting a route I always look at what the Navigation software or device is going to do before I start off. Commonly, I will manually skip WP1 before heading out just to eliminate a possible issue. Been fooled too many times when I trusted the s/w or device and ended up in a mess.

[Con Hennekens]

@Herman-Veldhuizen said in First point is often ignored:

I am quite sure that every new user will at some point get surprised by this nearest point issue.

Considering the ZERO (+1) questions about it on the forum I am pretty sure it won't.
I am not saying no improvement is possible, but I do think you are probably overthinking it.

When the accuracy of the gps position is good, could it be a smaller? The problem with misplaced waypoints is not limited to the start.

Whether a WP is hit or not does not depend on the position of the waypoint itself, but on the projected position ON the road. That means that the actual start of the routeline, or the little black dot you see on the road if you place a WP next to it. And YES, this feature IS limited to the start, because that is when you continuously get send back to it when you start a route passed that point a little bit, which often happens on parkinglots and driveways. There were MANY complaints about the app keeping you guided back to the start, so YES there actually was a need to treat the start differently.

Or : can the app somehow check upfront wether the Start is misplaced?

It is not about the start being misplaced, it is about the rider being misplaced at the start.

I am used to the message from tomtom when i start navigating to a destination. It tells me the ETA.

That is not a bad idea, but probably most useful in A2B routes (single destination routes). You could of course take a look at your screen too, before driving off

And if you haven't done it yet, i suggest you try out Beeline one day. It doesn't support the concept of navigating to nearest point but is has an interesting way of skipping to next and previous.

I have found myself in positions where I though some kind of back-button to skip back to the previous waypoint would come in very handy indeed. I find myself being too late pressing the revert button if a WP gets auto-skipped. That is because exactly at those moments I tend to be busy taking a wrong turn . So yes, I would welcome such a feature!

please spare me from your analysis on me. It serves no purpose.

Let's try to be respectful to volunteers who just try to be helpful.