Today I navigated a track on my motorcycle. I enabled the option 'calculate route between points'. I experienced that OsmAnd tried to send me back to a routepoint. I do not know which one. I followed the track but OsmAnd keeps sending me back. Then I disabled the option 'calculate route between points' and navigated the track in the old-fashioned way. That worked fine.
When I was almost at the half of the track I decided to enable the option 'calculate route between points' again. At first OsmAnd wants me to leave the track but I just folowed the track. Then I passed a routepoint. It was properly announced. The next routepoint also was passed in a normal way. I decided to leave the track and take a shortcut. This would mean that one routepoint would be missed. At first OsmAnd tried to get me back on the track but then it calculated a new way to the track. The missed routepoint was skipped. OsmAnd stopped trying to navigate to this routepoint. This is the perfect behaviour. But why does OsmAnd did not behave this way at the start of the track?? The only reason I can imagine is that the starting point and ending point of the track are the same. Perhaps OsmAnd gets confused by this. I think I try again with a ending point that is not the same as the starting point and with at least 100m between them. -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/13e3a2c6-a75a-4f7c-aea5-2761588329be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
