Round trip recalculated

[klirtom]

There is the missunderstanding I do not create the round trip on my own. I'm using Round Trip app available on XT2.

[jfheath]

There is the missunderstanding I do not create the round trip on my own. I'm using Round Trip app available on XT2.

No - not a misunderstanding: There are a number of ways that you can create a round trip and @smfollen's response showed Basecamp Maps - just to illustrate his reply.

But you did not say how you created your round trip. So I thought that I would try a different approach from that used on many forums. I thought that I would find out what the question involved before giving a reply.

When using the XT2 to create a round trip - Main Screen -> Apps -> Round Trip - you can specify the start, the distance, duration or intermediate destination, and the direction in which you wish to travel. (I know that you know that, but other people reading may not - although you kindly provided the link to the relevant page in the 'manual'.)

What you get is a route. But it is not a normal route - it has no route points and if you try to edit it, it looses the information that keeps it in place and takes you straight home. Also if you use the 'shape' button, it then becomes a normal point to point route and any deviation will take you straight to the next route point. Home or the mid point. The manual doesn't tell you that, but the Zumo will warn you if you try to edit it.

The route created by the "round trip" facilty behaves like a track that has been converted to a route. (Or converted to a trip if using the XT1). A Track-Trip.

These don't behave like normal routes. They stay fixed in place - like a track, but they give directions. But if you have to deviate from the route - eg if a road is closed, or there is a traffic problem - then it locates a point on the remaining route that it is closest to your current position, and navigates you to that. That is pretty good - usually - but it presents two potential problems:

• These type of routes can be subject to the RUT issue. It would happen if you are forced to deviate from the route (eg road works) and the XT2 calculates a way to rejoin the route by going back the way that you have just ridden. And you ignore it - because it is taking you straight back to the road works. It will then spend the rest of your route trying to make you go back - unless you manage to find the original route up ahead. I know this because I came across it when I did weeks of testing that lead me to the discovery of RUT behaviour in normal point to point routes.
• 'Round Trips' are not circular. I'm sure that you were just trying to explain etc.
  
  Typically a long round trip will be going there and coming back a slightly different way. A very long thin oval.
  
  Or like this 250 round trip that I have just generated on my XT2.
  
  

  

  XT2 250 mile Round Trip.png (989.44 KiB) Viewed 202 times

  
  The route starts at the bottom of the page and heads north up the right / east side of the loop. Then from the A69 it starts heading south down the left / west side of the route.
  
  There are a number of places where the route heading north is VERY close to the route heading south - if you go off route - eg for a coffee stop - the XT2 will find a way to the nearest point on the route from your current position - and in places like Kendal and Penrith, that could easily find the section heading south, when you are still heading north. This is not what I think - I know this because I have tried it.
  
  So what @smfollen was suggesting was to create two routes. In the example from my map, One route would take you north using the East / Right side of the map - up to the A69 at the top. The other would bring you back down the west / left side.
  That technique prevents the problem of the satnav jumping onto the wrong part of the route
  
  You cannot do this using round trip. However - you can insert an intermediate destination and it plots the first half and draws a dotted straight line back to the beginning, Perhaps when you get there, it calculates the return part of the route. I don't know. It seems likely. I'll have to try that one day to find out.

[klirtom]

Nice summary @jfheath.

Of course I can create one trip there and one trip back. But when I want to take another route back, then I have to add extra point. In this case I've already created the round trip manually. Which is not a problem. And I do not have to split it. It works well even if it is one route.

But I started this thread because I like the convenience that XT2 will create it for me. I'm not really looking for another way of making a round trip. I'd like to use the round trip app. I'm interrested if anyone has found a solution to my problem with route recalculation.

[Treve]

I don´t think this recalculation issue is no big deal. When one have made a route one really want to drive - regardless in what way it´s made - why let the Zumo recalculate it if one eventually deviate from the route?

I personally use the route as a kind of "track". When i deviate from routes and get the question "do you want to recalculate" I almost never let it. Then I use the map on the unit as a "old school" map - finding my way to whatever I want to deviate to. Knowing that I have the route in "magenta" just nearby and easily can go back to it.

I almost never use "waypoints" between "start" and "stops" - just "shaping points" - in order to fix the route on roads where I want it to go. By doing so I avoid the risk of "missing" a "waypoint" when I deviate from the route - with well-known consequences. When I reach the route again "Swedish Ingrid" continue to give me prompts from where I join the route again.

I have resent practise this on our 5000+ km trip to Nordkap. Not a single issues on the whole trip. Many deviations every day to places I didn´t knew were present when I planed the 20 different routes. As a second security I also have the TrimManager-made tracks on board.

So - for me - the recalculating issue is no issue at al any more. And XT2:s bright screen, outstanding batterylife and the good onboard topo map makes me love my XT2. It shows me the present speed limits. Gives me speed camera alerts. Display my custom POI:s. Give me fuel-alerts. Find petrol stations ahead and some other important information. Maybee I may use Tread-app but only to get real-time alerts. And the "rout-planer" on board is - with a little practice - fairly easy to use.

That´s howe I use my Zumo XT2. One issue is the fact that this BT-equipped beast don’t let you cordless transfer data without this "Tread"-app - witch I don´t use at al for the moment. Why in earths must Garmin store my data in its cloud?
Drive safe.
Shappe