Sorry, the algorithm can get confused by loopbacks etc. I have actually coded around it but decided to start simple and never incorporated that code.Hi - new user here. I am a member of CityStrides community, where people try to run as many streets as possible in a certain city or geographical area. Which means many of my routes try to cover as many streets as possible and get quite complicated - out-and-backs and loopbacks are common. Navigation on such routes is always a bit of an issue. I used to just check a map on my phone from time to time but recently tried WayOutDoors and its turn-by-turn navigation with audio alerts is a big improvement. But one problem that I noticed is waypoint alerts on loopback routes. If my route goes through the same street twice, and there is a turn I want to take the second time but not the first time, the alert is triggered both times. My guess is it is triggered based on proximity and not on the waypoint order. Not a huge problem but it means that I cannot rely on audio alerts 100% and occasionally have to check the map, which is not that convenient when you are running. Is there a way around this - either through app settings or some other clever solution?
A few people have mentioned it so it's on my to-do list for when I next revisit the navigation aspect of the app, but that won't be for a while. Sorry about that.
In the meantime please could you send the route file for one of your complex routes to info@workoutdoors.net then I can use that to test the code when I do add it. Thanks.