The best way to avoid accidental detours when plotting routes is to click away from junctions when plotting. This should also ensure that no directions are missed. Zooming in close will also help to plot accurately.
"The text is correct, but no arrow shown" A test by www.plotaroute.com/route/970464
In WEB design DIR'NS find text without turnarrow, located nearby road type change @ distance 9,3 km. (GraphHopper router engine ?)
But at export tcx a PointType "Straight" and text in Notes is attached.
I know. A similar problem was also reported in the Locus forum (By other router). Precise correct route design (RWGPS tips) solved that issue. Should be nice if Kerry (or Peter) could share one such a problematic routedesign by Plotaroute link or by an exported file. (tcx/fit/gpx)
Kerry wrote: "- the text does not match the arrow. Usually the arrow is correct, but the text is wrong (ie Turn Left and the arrow shows turn right)
- The text is correct, but no arrow shown at all"
I see this a lot too.
A possible cause is: When building a route you may have tapped near to a (critical) junction. And thereby missed (zoomed out) the correct road to be followed ? Plotaroute does not give a warning when tapping near these critical junctions. That issue does often happen with ALL routebuilding software. RWGPS explains the problem here. https://ridewithgps.com/help/incorrect-cue-sheet-entries See tips !
BTW - I found a LOT of incorrect Directions. Perhaps 4 or 5 in 30. I just went through about 10 routes and had to fix every one.- totally wrong direction (ie Turn Left and it should be Turn Right)
- the text does not match the arrow. Usually the arrow is correct, but the text is wrong (ie Turn Left and the arrow shows turn right)- The text is correct, but no arrow shown at all
- some directions missing completely. This is on complete right angle turns. Not very often.- adding a manual turnpoint at the correct location can be impossible. It jumps up and down the track some unknown (to me ) distance. It will not go where I want it to. This is only sometimes, so am guessing it might be something to do with the map?Sometimes if I re-route a section, these errors fix themselves. ie a replot works.I was wondering how I can demonstrate these problems? Can I give you the Route Number and you can check it out from your end? Any other method suit you better?
I have been going through all of my automatically generated (By Foot) routes. There is one issue that crops up a lot. Like 3 or 4 times in a 12 km route. The route takes a small detour down a side road, then comes back and carries on correctly. Usually the only time I notice this is when the TBT cue is incorrect. It is easily fixed - I just re-route that small section and it fixes itself.
DESKTOP TABLET MOBILE
(no app download required)