Tread - I sort of like it

[proofresistant]

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

My observation:

• The route comes from the Tread app to your Zumo XT2

• The Zumo XT2 checks it and recalculates

• The Tread app receives the route from the Zumo XT2, checks it, and recalculates

• The route comes from the Tread app to your Zumo XT2

• ...

Yes, that’s how I’ve observed it many times, and it often ended up seeming in endless loops

Now, when a second Zumo XT2 is added, it behaves asynchronously, just like the first Zumo XT2
I’m not surprised that the behavior described above gets even more chaotic or confusing with more devices. But ultimately, that doesn’t make things better, quite the opposite

And I can definitely confirm that it was sometimes like a nightmare when I tested with two devices at the same time.

[proofresistant]

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.

There are no Tread app routes (in the strict sense).
It is probably, or very likely, not widely known that routes can only be shared among Tread app users.
In principle, routes can generally be exchanged via GPX files, and this also applies to the Tread app as a source.

If you only see “a single” straight line between the (start shape via end) points in the Tread app (and you didn’t select direct routing), just wait, sometimes for a few minutes, and Tread app will automatically turn it into a route.
Note! Multiple shaping points, e.g., >30, may Can the calculation take a long time or become a problem or even completely block the route calculation.
But you probably know very well how best to handle many shaping points.

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?

Then you can convert a route from the Tread app into a track file by visiting the Explore Cloud website; you can do that there.
Maybe you can convert a route into a track using the Explore app—I haven’t tried it yet, but I wouldn’t rule it out.

PS
You're welcome anytime, anywhere

[proofresistant]

In principle, routes can generally be exchanged via GPX files, and this also applies to the Tread app as a source.

Update: “in principle” really mean “in principle”
Already been discussions about issues where routes exported using the “Adventoure” algorithm are saved incorrectly and therefore cannot be imported everywhere.

[Oop North John]

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?

I've failed to work out how to convert a route into a track using Tread or XT2. I can do it on the Explore website, but the track is only straight lines between waypoints, so can only assume that it doesn't have routing algorithms.

When the "calculating" is going on and on, the XT2 seems to be happy to calculate the routes, and still the Tread app keeps on "calculating". I have another assumption that the Garmin's servers cause the problem with some of the strange behaviors.

[proofresistant]

... do it on the Explore website, but the track is only straight lines between waypoints, so can only assume that it doesn't have routing algorithms.

You're right, they're “just lines” first. But what if you turn them into a route again in the other navigation device (app)? I think that could work; I've tried something like that before, but I can't quite remember right now—I'd have to try it again.

When the "calculating" is going on and on, the XT2 seems to be happy to calculate the routes, and still the Tread app keeps on "calculating". I have another assumption that the Garmin's servers cause the problem with some of the strange behaviors.

I don't think it's the servers; the calculation happens in the Tread app. I'm not sure, but it's very likely. Shapes might be more critical.

[proofresistant]

... But what if you turn them into a route again in the other navigation device (app)? I think that could work; I've tried something like that before, but I can't quite remember right now—I'd have to try it again.

I just tried turning such a track (created with explore cloude) like that back into a route on my GPS device.
The result was usable, even if not ideal, more lika a backup plan. It seems like 90% of the route path matched, so this method isn't suitable for general use, but as backup, it's better than nothing.

[smfollen]

For what its worth, Trk2Rt, which is included with the current version of Trip Manager, will also convert a route to a track. It run a pc however. The route must be calculated and contained in a gpx file.
viewtopic.php?t=3581

Sorry if off topic, but I thought it might help.

[proofresistant]

For what its worth, Trk2Rt, ...

Using tracks definitely makes the Tread app more enjoyable.
In any case, it’s a good choice to have tracks available or to display them in the Tread app and/or on your device.

With Trk2Rt (including in Trip Manager), you’ve hit a sensitive spot for me. I really need to test it out; it’s been on my to-do list for a long time
Let’s see if it makes the Tread app even better to use, I wouldn’t be surprised.

[Regain]

Ok, thanks for the responses and trials. It all sort of backs up what I had found which is a shame. My straight track lines were not in the Tread app but wherever else I sent the Tread built route on to such as Explore App, GPX Reader Pro etc.

Whenever I view or follow an imported route on Tread or the XT2, I have the track showing underneath it. Belt & braces.

But I have got quite slick at quickly planning these Tread routes now. Easier on a tablet than a phone and I like the way that shaping points snap to the road as you move along the plan.

[Oop North John]

So yesterday getting tired on the hours taken when calculating a route in the Tread app after just removing a waypoint from a previously calculated route I took the plunge and deleted the Tread app and reset my XT2. I installed TripManager and Tread but without enabling storage, and seem to have got the hang of it, after one self-induced error. Hopefully as I'm off on a trip to Morocco in just over two weeks time, certainly no map updates will be carried out between now and then!

Learning how best to import data from Basecamp caused a few choice words about Garmin software, but now I have a system that I feel confident won't induce errors due to me doing something unrelated elsewhere. I do miss the ease of exporting a folder from Basecamp via e-mail to my phone and opening it up, and all the data is there.

All this messing about because Garmin messed up the routing algorithms by the faster roads and RUT. Pretty damming that a navigation system can't do the basics correctly, and, needs its users to work out how to manage their failures.