MotoTex
0
I've used Routes for 98% of my travels and haven't had any problems significant enough to justify the effort of using Tracks exclusively. There have been instances where I have used Tracks, like the ET400/500 rides, singletrack trails, etc. where a map was more appropriate.
When riding locally, to lunches, pie runs, etc. the navigation data providing time / distance to the next turn, street name detail at turns, time or distance remaining on the route and other related info is useful for me to reference at a glance. I don't use the turn by turn via Bluetooth notification to the helmet com at all.
After getting past the learning curve in Basecamp I can easily create routes that go where I want them by placing the Start and End points, then use the "Insert" tool to drag the route onto the roads I want to ride between those points. This tool isn't displayed by default and can be added to the toolbar for quick access, or, selected from the Tools drop-down menu.
When riding locally, to lunches, pie runs, etc. the navigation data providing time / distance to the next turn, street name detail at turns, time or distance remaining on the route and other related info is useful for me to reference at a glance. I don't use the turn by turn via Bluetooth notification to the helmet com at all.
After getting past the learning curve in Basecamp I can easily create routes that go where I want them by placing the Start and End points, then use the "Insert" tool to drag the route onto the roads I want to ride between those points. This tool isn't displayed by default and can be added to the toolbar for quick access, or, selected from the Tools drop-down menu.
Last edited: