First point is often ignored
-
Put the first point some distance say 1km away from where you are. The GPS system know where you are when you start and will navigate you through the first waypoint. This is good practice no matter what GPS system you are using.
@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
Maybe a stupid reaction.
I only watched your first video. But something you can check.
If you draw a straight line from your postion to (way)point 1 and a straight line from your to the postion where the route is picked up.
Which line is the shortest?@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.
-
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.
