First point is often ignored
-
I have noticed that the app often ignores the first point (start) of my route.
Somebody knows why this happens?My test route koffie:
https://www.myrouteapp.com/route/open/11537715
And the first point really is the nearest point. The app ignores via point 1 and sends me straight to point 2.
Video:
https://drive.google.com/file/d/12bXJEgzH-a3edMcOQiXpraazWNlp2hOw/view?usp=drivesdk
-
If you turn Off start from the nearest point of the track, what happens. What is the situation Between your starting point and Viapoint 1. Is that by any chance a oneway street
-
Users quite often complain about continuously being sent back to the start (which won't ever be auto skipped as it's a viapoint)
If you are within so many meters of the start, it will just select the next point as your starting point. In this specific case the fastest route to 2 is just not over 1
Disabling the setting mentioned by @Marinus-van-Deudekom will result in being sent past waypoint 1.
-
With nearest point disabled the app indeed sends me to the first point first.
I am navigating as track. Isn't it such that then any point or turn on the track could be the nearest? In this case, shouldn't the nearest point to navigate to be the first turn right after the start on the original track ?
I see what you mean with complains about being send back to the start.
But how this is solved makes the app a bit unpredictable, unless the user is a mra expert.This illustrates that: If the start wasn't the start but the second point in the route then the app would happily see that point as the nearest point.
lang koffie route:
https://www.myrouteapp.com/route/open/11539093lang koffie video:
https://drive.google.com/file/d/12zJBj8rGmbmfMXf-N9uMAHl8UqdMjr_n/view?usp=drivesdkI am using 4.4.0
