Hello XT’ers, Say:
- I have a Basecamp prepared Trip loaded on my XT (300Km);
- The Route was prepared on BC with 4 Via Points;
- The Route Via Points show on the XT with their Orange flags.
Question please:
Is any Route uncertainty or risk introduced if I now change the Via Points shown on the XT to Shaping Points (on the XT), given the Route was prep’d on BC?
Thank you, Mikey.
Via Point / Shaping Point question
- lkraus
- Subscriber
- Posts: 483
- Joined: Mon Aug 24, 2020 2:36 pm
- Location: Central Ohio, U.S.A.
- Has liked: 64 times
- Been liked: 166 times
Re: Via Point / Shaping Point question
A bug in the XT editing process causes a Via point changed to a Shaping point to also change its name and position, forcing a route recalculation. See 101 The Moving Route Point. It does not matter if the route was created in Basecamp or on the XT.
A Shaping point can be safely changed to a Via point.
A Shaping point can be safely changed to a Via point.
____________________________________
2006 R1200RT
Galaxy S10<>Zumo XT<>Sena 20S
2006 R1200RT
Galaxy S10<>Zumo XT<>Sena 20S
Re: Via Point / Shaping Point question
Thank you Ikraus, I did read ‘101 The Moving Route Point’ but did not fully grasp the message. Thanks for your summary, I now I ‘get it’ and have read 101 again. Lots of learning happening:)lkraus wrote: ↑Thu Jan 16, 2025 11:53 am A bug in the XT editing process causes a Via point changed to a Shaping point to also change its name and position, forcing a route recalculation. See 101 The Moving Route Point. It does not matter if the route was created in Basecamp or on the XT.
A Shaping point can be safely changed to a Via point.
Mikey
-
- Posts: 2891
- Joined: Sat Oct 19, 2019 4:17 pm
- Location: West Yorkshire, Uk
- Has liked: 387 times
- Been liked: 844 times
Re: Via Point / Shaping Point question
There are two separate issues here.
- The moving route point - when you use the XT1 screen to change a via to a shaping point is a known fault, which has been present since the Zumo 595. You don't want to know what the XT2 does. Garmin have taken an original issue and made it much more dramatic.
Simple solution - don't do it. - ---------------------------------
- The issue that I documented on 101 The Moving Route Point, is a completely different issue that happens when an imported route on the XT1 is being navigated - under certain circumstances.
It only happens with imported routes. Eg a gpx file, or routes sent from Basecamp, MRA etc.
It only seems to happen if the route has been recalculated when navigating - in particular when Skip is pressed.
It never happens in either of the above circumstances if the route has been 'fixed'. ie the XT is made to believe that the route has been 'saved', rather than 'imported'.
The solution that is described for fixing the RUT behaviour of an XT route, also works for this situation
Let me submit this and I'll come back and add in some links.
P102 - at the bottom describes two ways of making an imported route appear to be 'saved'.
P110 - has some links to videos showing this behaviour in different circumstances
Video - A demonstration of how to make a route 'saved' using the XT1 screen
Note in the last video - it is advisable to be within a few miles of the start point of the route when you do this OR simulate your current position as being close to the start.
Have owned Zumo 550, 660 == Now have Zumo XT2, XT, 595, 590, Headache
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC
Use Basecamp (mainly), MyRouteApp (sometimes), Competent with Tread for XT2, Can use Explore for XT - but it offers nothing that I want !
Links: Zumo 590/5 & BC . . . Zumo XT & BC