Limited number of waypoint?
Quote from miros on 28.04.2021, 03:02Hi Guido. Just made a long post in the feature section, however there’s something that might well be a bug and to which I wouldn’t mind a quick answer, so I’ll highlight it here too.
I am trying to add a complex and long route (a nearly 600 miles stretch of the UK TET), which is enormously laborious as scenic doesn’t really think I should take those narrow lanes and trails. When I get to 199 waypoints in the route, the “via” and “stop” buttons gray out and i can’t add anymore points unless I remove one of the existing ones.
is that an expected behaviour? Didn’t think there was a limitation to such a small number of via points. Is it perhaps the length of the route? Thanks you for your attention, I would love to finish planning this route and share it in the forum.
Hi Guido. Just made a long post in the feature section, however there’s something that might well be a bug and to which I wouldn’t mind a quick answer, so I’ll highlight it here too.
I am trying to add a complex and long route (a nearly 600 miles stretch of the UK TET), which is enormously laborious as scenic doesn’t really think I should take those narrow lanes and trails. When I get to 199 waypoints in the route, the “via” and “stop” buttons gray out and i can’t add anymore points unless I remove one of the existing ones.
is that an expected behaviour? Didn’t think there was a limitation to such a small number of via points. Is it perhaps the length of the route? Thanks you for your attention, I would love to finish planning this route and share it in the forum.
Quote from Guido on 28.04.2021, 05:46Hi Miros,
Indeed there is a limit of 200 via points / stops. I could raise this limit (requires app update), but that could cause problems later on. The more via points, the more performance it takes to do route calculations and navigation. Any more could cause long delays in route recalculation if you detour, use more battery and sometimes even lead to crashes.
What I recommend is following:
- Plan shorter routes. I recommend one route per day. And then store those routes in a folder and name them alphabetically, so you easily find them later.
- Have you tried the ‘short’ routing mode? This sometimes helps a lot because the ‘fast’ routing mode puts very high penalties on small and unpaved roads. Short doest care how long it takes… it only looks at distance. So, with the short routing mode you might require less via points to force the routing.
- Since TET is pretty well known, it’s possible that somebody already did the work for you. Have you tried the ‘find scenic routes’ in the routes tab? Use the filter to search for routes containing ‘TET’ in the name.Hope this helps/explains. If not or if you have other questions please let me know. Happy to help.
Btw thanks for the extended review in your other post. I really appreciate you taking the time for that. I will go through it and respond later today
Best regards and ride safe,
Guido
Hi Miros,
Indeed there is a limit of 200 via points / stops. I could raise this limit (requires app update), but that could cause problems later on. The more via points, the more performance it takes to do route calculations and navigation. Any more could cause long delays in route recalculation if you detour, use more battery and sometimes even lead to crashes.
What I recommend is following:
- Plan shorter routes. I recommend one route per day. And then store those routes in a folder and name them alphabetically, so you easily find them later.
- Have you tried the ‘short’ routing mode? This sometimes helps a lot because the ‘fast’ routing mode puts very high penalties on small and unpaved roads. Short doest care how long it takes… it only looks at distance. So, with the short routing mode you might require less via points to force the routing.
- Since TET is pretty well known, it’s possible that somebody already did the work for you. Have you tried the ‘find scenic routes’ in the routes tab? Use the filter to search for routes containing ‘TET’ in the name.
Hope this helps/explains. If not or if you have other questions please let me know. Happy to help.
Btw thanks for the extended review in your other post. I really appreciate you taking the time for that. I will go through it and respond later today
Best regards and ride safe,
Guido
Quote from miros on 28.04.2021, 08:54Thanks for your answer guido. I’ll try the “short” idea, clearly it could help. I understand the point about computational overhead. One question though. I’ve seen lots of routes with thousands of “support points”, which I assume are the same as via point. How does scenic deals with those (eg when they are imported)
Thanks for your answer guido. I’ll try the “short” idea, clearly it could help. I understand the point about computational overhead. One question though. I’ve seen lots of routes with thousands of “support points”, which I assume are the same as via point. How does scenic deals with those (eg when they are imported)
Quote from Guido on 28.04.2021, 13:25Scenic reduces those in a 'smart' way. If you want to know the details on that... have a look at this support article (and especially the blog article it links to).
Scenic reduces those in a 'smart' way. If you want to know the details on that... have a look at this support article (and especially the blog article it links to).
