Tread - I sort of like it

[Oop North John]

I have enabled the storage of routes so my XT2 and Tread talk to each other. This does cause problems for shaping points, certainly ones imported via a gpx file. But, I work around this by only having waypoints in routes imported from Basecamp, and then maybe adding shaping points in Tread.

One benefit of route planning in Tread is that it seems to mainly follow the routing algorithms of the XT2, so mainly what is planned in Tread ends up in the XT2. And, it avoids RUT issues.

Another benefit of route planning in Tread is that you can enable different layers, for example satellite view, so that you can easily see if Garmin's idea of where something is, is where I'm guessing Google Earth thinks it is. Hopefully they'll include Street View in an upgrade at some point.

I like how I can plan on the phone when away from home on a tour without having to carry a laptop, and I know that there are on-line routing programmes, but Basecamp is free, and seems to work for me.

I don't like how you find POI's where you have to search on a possibility to find it, and the display of waypoints / town names is "frustrating".

[Regain]

@Oop North John I've also been playing a bit more with Tread in my time off. What I find quite frustrating is amending a route. I realise you must first select the segment then delete or add route points accordingly but I seem to get my routes in a real tangle attempting it. I then find I have to delete points working backwards from the end point and starting again from where I want to amend. Do you have any tips or guidance on doing that better please?

Also, like you, I use Tread to check my route built on an unmentionable other piece of planning software to see if it works for the Zumo. If it does, everything usually goes well. If not, I add extra points on MRA (oops, said it) due to my above problem. Now that I've found I can also plan on my tablet with Tread when away, I've got a couple of options.

[Oop North John]

I've also been playing a bit more with Tread in my time off. What I find quite frustrating is amending a route. I realise you must first select the segment then delete or add route points accordingly but I seem to get my routes in a real tangle attempting it. I then find I have to delete points working backwards from the end point and starting again from where I want to amend. Do you have any tips or guidance on doing that better please?

You need to watch that you're inserting a shaping / waypoint etc into a route that's already from A to B. I try to insert waypoints that are already in Tread as then I am less likely to make errors in placing the point.

If you're building a route from A then I try to add the waypoints in sequence so that it's from A to B to C to D etc. Then see how it goes, if extra points needed, then insert as above.

One idea that's been suggested to me, and seems to work, is that the "Adventure Level 2" seems to match the routing algorithms of Basecamp, and it does seem to after a few tests.

[Regain]

Ok, thank you. I think that's kind of what I was trying to do. I'll keep on at it.

[Oop North John]

Ok, thank you. I think that's kind of what I was trying to do. I'll keep on at it.

One trick I use is if the route is something like I want, is to save it. Then if a subsequent amendment is wrong, for whatever reason, just "exit" it without saving, and start again from the known good point.

[proofresistant]

Tread - I sort of like it
...
I like how I can plan on the phone
...

@Oop North John ,
You have no idea how much I agree with you
I, too, think the Tread app is a great idea in principle and would be really worth it.
My favourite features are, for example:

• Quickly exchange routes wirelessly (without this constant plugging and unplugging and annoying shutdowns for data exchange, followed by restarting the device)

• Quickly check, correct, or modify a route

• Have offline maps on hand, including satellite views

• Sort collections, better than on the device

• ... and some more

But unfortunately, I’m not only having issues with shifted shapes, but also more serious problems, including frequent crashes.
That’s actually a different issue, but because of it, I’ve been hoping for an improvement for two years now. I try almost every update, but in the end, I’m always disappointed all over again and end up uninstalling it

One idea that's been suggested to me, and seems to work, is that the "Adventure Level 2" seems to match the routing algorithms of Basecamp, and it does seem to after a few tests.

I’ve also experienced that “Adventoure - Level 2” (may Level 3 also)) often results in pretty good outcomes
Plus the use of the “Michelin Scenic Routes” and the resulting routing calculations is almost automatically quite usable

[proofresistant]

... Do you have any tips or guidance on doing that better please? ...

I’m not “John”, but maybe my observations on editing, not specifically on deleting, will be of some help also.

Personally, I’ve noticed, for example:

• Keep in mind that your own shapings aren’t always realy relevant for the Tread app. The Tread app might think it knows better and therefore prefers to calculate the route to the VIA or destination on its own way.

• After making a change, let the Tread app finish calculating the rest of the route; you’ll know it’s done when the magenta line is drawn again is completed.

• Make sure you first click on a previous shaping; it should be active, this is more important than the selected route segment. Then next add a shaping or a destination will be placed after that previously activated point.

• Make sure that when you select a new point, you choose a position that can actually become a new one dialog. Sometimes you tap a spot, but the Tread app selects a neighboring existing point instead. You can quickly notice by the attributes available for your selection.

Maybe this helps a little also have fun with experimenting

[Regain]

Make sure you first click on a previous shaping; it should be active, this is more important than the selected route segment. Then next add a shaping or a destination will be placed after that previously activated point.

Thank you, that little gem of advice is just what was needed and works perfectly.

[Oop North John]

And today is an example of why I don't fully like it.

Two separate devices where the "calculating" goes on and on

[Regain]

@Oop North John I'm off work so been playing some more (sadly can't ride at the moment). The combination of selecting the last point before editing rather than 'select this segment' and your idea of saving the route in stages when happy before editing has made the whole process much easier.

I'm still not sure when I'll actually use this other than when I'm riding alone. Unless I'm much mistaken, and it seems I often am, sharing of a Tread route is only possible (or at least easy) between Tread users. My efforts so far to share via other means have only resulted in a straight line between points. I may be missing a trick.

So it would be nice if you could convert the Tread route to a track and share that way. Just so you could quickly share it around riders in your group to put on their own Zumo - I have friends on older non-Tread units. Maybe you can?

PS. I suppose SD card sharing is an option but I've never liked that idea in case you drop it down a drain or you get the wrong card back and have to listen to their crummy music when your phone playlist is exhausted.