Routes have an order, the points will be selected in the order they're shown
in the route. Depending on what your route is this is the most likely cause.
You'll want to do a show route and make sure points are in the correct
order. You also want to make sure the route is actually selected in
databases/routes.
You can check on the progress with the show next route point button. You can
check what the next point is, the origin, and the destination. The next
point isn't switched to until the current point has at least been
approached. The routing logic tries to determine what the origin and
destination are, and your current point along the route. You have to be
moving for this to work propperly and it helps to have a good signal.
Sometimes these calculations can go wrong so you may have to manually select
a point along the route to get things back on track. You'll also have to do
this if you are going to go off the route and approach points in a different
order.
On Mon, 6 Aug 2018, Mike Hanson wrote:
I converted a checkpoints file to a routes file. I tried to walk
using it and Loadstone did not shift from one route point to another
when I tried to get it to show the closest route point. I had it set
to both when I had to choose forward, reverse or both. I didn't set a
destination. What is happening?
Mike Hanson
_______________________________________________
Loadstone mailing list
[email protected]
http://lists.loadstone-gps.com/listinfo/loadstone
_______________________________________________
Loadstone mailing list
[email protected]
http://lists.loadstone-gps.com/listinfo/loadstone
