How to draw a route on the Tread and not have problems on the XT2

[Gelo]

Hello
I would like to share a document that I uploaded to a web of how to create a route in Tread in such a way that just by having a track that has been created, shared or downloaded from the internet you can create a route in the Tread and be read in the XT2 without problems, which allows us not to need a PC and that in route can be important.
It is enough to translate it web to the personal language.
Good luck.

How to draw a route on the Tread and not have problems on the XT2..pdf

(3.34 MiB) Downloaded 44 times

https://www.bmwmotos.com/foro/threads/z ... st-9743355

[jfheath]

Thank you. An excellent point to make.

Routes created on the Tread App will generally not have any issues - except the the XT2 receives only the route points and the method of calculation. The XT2 itself may have different ideas about which way is (say) faster. But it will go through all of the route points.

The same cannot be said of routes sent as a gpx file- including, weirdly, gpx files created by the Tread app.

[Gelo]

Thanks for your comment.

The idea is to be able to link Tread to the XT2 and thus dispense with the PC to transfer the routes created, downloaded, etc., to the XT2 via the USB connection that gave many problems in the calculations, this will be very useful on trips to pass routes directly from Tread to the XT2.

I use Basecamp and web planners like Kurviger, MRA, etc. At first, in order not to damage them when transferring them to the XT2 via Tread, I unlinked the application from the XT2, like many others. However, the essence of this device was lost: to be able to dispense with the PC.
I simply need the track, as Tread will read it exactly and, with it, I create the route in Tread very quickly and easily, as I indicate in the document.

It is important that the conditions to avoid in both Tread and XT2 are identical.

So far I have created many routes and XT2 has read them all correctly.

[jfheath]

I wish you well in your efforts.

I'm curious as to how you get a track into the XT2 - as the last time that I checked, the Tread app doesn't have the ability to create one.

I was really determined to make the Tread app work. But for what I wanted it has always let me down:

I like to use a minimum of Via Points - usually one to mark each of the stopping places. That way I can have a trip data display which reveals the ETA for the stopping places - something that is important for my pillion. All of the rest are shaping points.

But the Tread App is very poor at editing shaping points: I have to place them in strict order of travel between via points, and the app names them all as 'Shaping Point', so although there were facilities to re-order them, in practice it is extremely difficult to pick up one shaping point in a list and drop it precisely between two other shaping points. It sounds easy, but as seen as I start dragging one line in the list called 'Shaping Point', the list display moves. So the place that I was going to drop it, is no longer where it was.

Furthermore, when transferred / synchronised, the XT2 calculates the route and it has a habit of moving groups of shaping points onto faster roads.

So if I want reliable route planning I have to use only Via points. Via points are non - negotiable. I MUST visit them. If I don't then I will be redirected back to it - even if I rejoin the magenta route line after the missed Via point. So situations like minor detours, road blocks present a problem which can be solved only by pressing Skip.

If you press Skip, the route is recalculated and nature of the route changes. In my numerous tests, it seems that all route points are now optional. If I fail to follow an instruction to visit one, the Zumo seems to head for the route at its closest point and any shaping and via points are simply removed from the plotted route before the point that it has chosen.

Furthermore - for imported routes (ie from gpx files) that presents the opportunity for RUT behaviour to develop - but using Tread, that will no longer be an issue.

So, for me, until the Tread App is sorted out - and I doubt that Garmin has any intention of putting any effort into a 2 year old device - it is something that promised a lot but offers me absolutely no solution. It is installed, but I refuse to let it synch. Doing so will destroy my route by moving its shaping points and renaming route points.

As far as I can tell, up ahead places may only look as far as the next Via Point, so road closures don't show up very far ahead if you use lots of Via Points.


To be honest, I'm done with the XT2 and Tread. I can make it work like the 590 now, and it is reliable and does what I want. But I have to use a computer - but I have no problem with that. I have an ipad, I have a smartphone. There are maybe just a few jobs that they can do, that I cannot do better on a computer at home. But for me, route planning isn't one. Tread had me really excited when I first saw it, but for me, it fails to deliver in its implementation. ie the programming and project management.

But that is only my view of things. I will watch with interest and I would be more than pleased if you come across things that have changed or which are different observations from my own. Or a different way of making Tread do what you want.

[Oop North John]

So if I want reliable route planning I have to use only Via points. Via points are non - negotiable. I MUST visit them. If I don't then I will be redirected back to it - even if I rejoin the magenta route line after the missed Via point. So situations like minor detours, road blocks present a problem which can be solved only by pressing Skip.

If you press Skip, the route is recalculated and nature of the route changes. In my numerous tests, it seems that all route points are now optional. If I fail to follow an instruction to visit one, the Zumo seems to head for the route at its closest point and any shaping and via points are simply removed from the plotted route before the point that it has chosen.

Because of the skip problems, if I want to miss a via point, introduced as it doesn't get messed about in Tread etc, then I always open up the route and select the next via point I want to visit. It can be cumbersome given the number of via points needed to keep off the "fastest" roads the XT2 etc loves to use, but so far, has worked for me.

[Gelo]

I wish you well in your efforts.

I'm curious as to how you get a track into the XT2 - as the last time that I checked, the Tread app doesn't have the ability to create one.

I was really determined to make the Tread app work. But for what I wanted it has always let me down:

I like to use a minimum of Via Points - usually one to mark each of the stopping places. That way I can have a trip data display which reveals the ETA for the stopping places - something that is important for my pillion. All of the rest are shaping points.

But the Tread App is very poor at editing shaping points: I have to place them in strict order of travel between via points, and the app names them all as 'Shaping Point', so although there were facilities to re-order them, in practice it is extremely difficult to pick up one shaping point in a list and drop it precisely between two other shaping points. It sounds easy, but as seen as I start dragging one line in the list called 'Shaping Point', the list display moves. So the place that I was going to drop it, is no longer where it was.

Furthermore, when transferred / synchronised, the XT2 calculates the route and it has a habit of moving groups of shaping points onto faster roads.

So if I want reliable route planning I have to use only Via points. Via points are non - negotiable. I MUST visit them. If I don't then I will be redirected back to it - even if I rejoin the magenta route line after the missed Via point. So situations like minor detours, road blocks present a problem which can be solved only by pressing Skip.

If you press Skip, the route is recalculated and nature of the route changes. In my numerous tests, it seems that all route points are now optional. If I fail to follow an instruction to visit one, the Zumo seems to head for the route at its closest point and any shaping and via points are simply removed from the plotted route before the point that it has chosen.

Furthermore - for imported routes (ie from gpx files) that presents the opportunity for RUT behaviour to develop - but using Tread, that will no longer be an issue.

So, for me, until the Tread App is sorted out - and I doubt that Garmin has any intention of putting any effort into a 2 year old device - it is something that promised a lot but offers me absolutely no solution. It is installed, but I refuse to let it synch. Doing so will destroy my route by moving its shaping points and renaming route points.

As far as I can tell, up ahead places may only look as far as the next Via Point, so road closures don't show up very far ahead if you use lots of Via Points.


To be honest, I'm done with the XT2 and Tread. I can make it work like the 590 now, and it is reliable and does what I want. But I have to use a computer - but I have no problem with that. I have an ipad, I have a smartphone. There are maybe just a few jobs that they can do, that I cannot do better on a computer at home. But for me, route planning isn't one. Tread had me really excited when I first saw it, but for me, it fails to deliver in its implementation. ie the programming and project management.

But that is only my view of things. I will watch with interest and I would be more than pleased if you come across things that have changed or which are different observations from my own. Or a different way of making Tread do what you want.

Obviously what I intend with this idea is not as deep as what you are worried about.
My idea is how to take advantage of the idea for which this navigator was conceived, that is to say, that it allows me to go on a route for several days and to be able to create routes, modify them, receive from other colleagues, etc... and to be able to do it without having to use a laptop, that for me is the important and useful thing of this navigator.
I just use the track that I receive or have and I open it with the Tread, there I draw easily and quickly my route with its WP and that's it, the XT2 calculates it without difficulty.
In the case that I have to make a route in march I use a planner in the mobile, Kurviger (it can serve any other) and why? because its interface is much more friendly than the Tread, that is to say, I create the track, route, WP and I open it with the Tread and there I draw the final route in a couple of minutes and that YES it is going to be calculated by the XT2 without problems.
It is important that the points or WP are on the roads or tracks on the map and not outside them, otherwise the XT2 will not complete the route when calculating it.
Honestly, I was very critical with this navigator for not being able to do this and having to use the USB cable to pass my routes having unlinked the XT2 app and that at least with the latest updates I have been able to recover this quality, otherwise the navigator for me would be a paperweight.
Good day

[jfheath]

Yes - it works well but as I say - if you use shaping points there is a reasonable chance that during synchronisation it will move the shaping point onto a faster road. It nearly always moves them a bit - but when there is a faster road nearby, it often proves to be too tempting for it.

[Oop North John]

I've been plotting some routes for my upcoming trip to Croatia, and have done this in Basecamp I then exported the routes as I usually do via an e-mail to my smartphone, and open the gpx file in Tread on it.

Some of the days the distance / time were very different and so I checked why, and usually it's the "faster" roads problem that exists on the XT / XT2 and also "helpfully" in Tread. So in the comfort of my home I could add in extra via points to force it from trying to use every motorway in Europe, and onto the scenic roads I'd like to use. This is helped by the Michelin scenic roads being shown in Tread.

Much, much less stressful than in the middle of nowhere trying to work out what the XT2 was trying to suggest to me. So whilst not a fully paid up fan of Tread, my thoughts on it have improved. Pity to the XT users who don't have this option

Now if they could fix the "faster" roads fault, I wouldn't need to mess about so much!

[jfheath]

The use of Via Points helps to fix the route onto the road.

Shaping points seem to have a purpose which is unknown to me - With Tread enabled the XT2 seems to calculate a route between the Vias and it then moves the shaping points onto it.

It does not do this if Tread is not involved.

You can use Tread to get traffic, weather, up ahead info etc onto the XT2 screen without allowing it to synchronise. Unfortunately, if you want to email a gpx file so that the Tread App can pick it up, Tread synch needs to be fully enabled - so for me its back to using the USB cable.

But I like to use Shaping points. The Trip Data that can be displayed at the right hand side of the screen can show the distance, time, ETA for the next Via Point. I ride with a pillion and I use the Via Points to inform me/her of the distance and time to the next possible stopping place - ie the next Via Point. That would not be possible if I used Via points instead of shaping points. But the Tread app seems quite happy to relocate shaping points - so for me using the Tread App to synch is a non starter.

[Oop North John]

I'd guess that I only need to add about 10% fake via points. The others are actual POI's to me, eg viewpoints / fuel / cafe's etc so they are of interest to me.