Changed adventurous behavior on XT2

[rhoenschrat]

Meanwhile I have published my videos.
It has become a mini series of 8 videos
Unfortunately for you they are in German, but you can torture yourself watching them with the automatically generated AI audio translation from YouTube.
Maybe some of you are brave enough to do so.

But then it would be nice to mention the helpful lights on the horizon, such as TripManager, which would be the icing on the cake

As mentioned above, the videos are available now. So, you can check if I did.

The Zumo never calculates a route to the next ‘waypoint’. It should calculate to the next route point - which will be either a via point or a shaping point. Whether or not the route point was originally created and saved as a waypoint is irrelevant.

I already learned that I missues the word "waypoint" most of the itme, when I meant "route point". Try to get better with this, but still do the same misstake from time to time.

In my experience, I can set the adventure level per segment in the Tread app, but on the XT2, every change is applied to the entire route. Has that been your experience as well?

As @jfheath already mentiond, this is only caused by the fact that the XT2 does bot show somewhere what is the current adventurous kevel of a rout segment, And when you open the selection, it shows whatever level was selected the last time the selector was used.
I show this in part 6 of my videos.

In my opinion, the Kurviger app is much easier to use, especially when it comes to adventure. Export it as a track, and you're all set.

Similar to @jfheath I don't see a track as a proper solution for the naviagtion. Even if you convert the track into a route on device, it's not what I expect from a route.
I want to have
- my via points anounced on screen and with voice prompts
- see the ETA for my next stop and the final destination
- get visual and voice direction in general

[jfheath]

Off topic slightly, but have you tried loading a track and then selecting Go! ?

I’ve not done it on the XT2, I assume it will do what the XT1 does.

It is remarkably relaxing. No voice comments, no instructions, the satnav keeps your route displayed on your current position and if you deviate it gives you a straight line direction - dotted and a distance - just indicating where you need to be heading to get back to the routes closest point.

I thought - ‘Why ? What use is that ?’ Until I tried it. Nothing goes wrong, you’re in control, it’s there if you need it. It’s like having a paper map with the route highlighted and someone turning the pages and keeping their finger on your current position. I guess it’s made for off road use, but I was pleasantly surprised with it on the road.

[rhoenschrat]

Off topic slightly, but have you tried loading a track and then selecting Go! ?

Yes, I did. And you're right, it’s the same on the XT2.

As you mentioned earlier, the downside is that you lose the ETA for both your "pit-stops" and your final destination, as they aren't indicated anywhere. However, for people who don't mind that, it’s a great option—and I suspect many use it exactly this way.

For me, though, I rely on voice instructions as a reminder to turn. Once I’m in "the zone," I often forget to look at the nav and just keep riding. Without those voice prompts, I’d be constantly off-route.

I really wish the dotted line was available in regular routing mode (with recalculation turned off) whenever you deviate from the route. Furthermore, I wish the "imported routes" behaved more like the dotted line does with: always pointing to the closest point on the route relative to your current position. Recalculation should ideally guide you there, rather than the "RUT behavior" which tries to force you back to exactly where you left the route.

That said, track navigation remains an option for me, and I’ve developed a specific strategy for it. When exporting a planned route from Kurviger, I include everything in the file:

• The route points (as waypoints)

• The route itself

• The track

Just as I display a track as a background reference while navigating a route, I do the opposite here: I show the waypoints/favorites as a visual reference while following the track. This gives me a clear visual of my planned stops.

To get an audio alert as well, you’d currently have to convert those waypoints into POIs using the Garmin POILoader. It’s a lot of extra work, and I’m not always sure it’s worth the effort. But if you do, you get that discreet "double ping" and an on-screen notification when you get close.

It could be so much simpler: GPX extensions already allow for "Proximity" settings on waypoints (something you can do in BaseCamp). It would be a minor tweak to include a proximity value in the imported GPX file. Then, much like toggling the visibility of a collection on the XT2, you could simply toggle audio prompts for waypoints with proximity values. Just a thought!

[FrankB]

It could be so much simpler: GPX extensions already allow for "Proximity" settings on waypoints (something you can do in BaseCamp). It would be a minor tweak to include a proximity value in the imported GPX file. Then, much like toggling the visibility of a collection on the XT2, you could simply toggle audio prompts for waypoints with proximity values. Just a thought!

TripManager can do that, I can create POI files from GPX files. You can select Way points, Via and Shaping points. They will give a) the correct icon (not a green/white heart) and b) an alert

Now I know you're a Mac guy, and can't be convinced to use Windows, but what you could do is have a look at the implementing Pascal Unit, and a very good documentation from Herby Oppman.

https://github.com/FrankBijnen/TripMana ... nitGpi.pas
https://www.memotech.franken.de/FileFor ... Format.pdf

Frank

[rhoenschrat]

TripManager can do that, I can create POI files from GPX files. You can select Way points, Via and Shaping points. They will give a) the correct icon (not a green/white heart) and b) an alert
Now I know you're a Mac guy, and can't be convinced to use Windows, but what you could do is have a look at the implementing Pascal Unit, and a very good documentation from Herby Oppman.

I kown, I know. It's already on my ToDo

But what I meant was, it would be nice, If we don't need to create them as POI, but just provide the proximity value in the regular GPX waypoints and get them transfered and used from the Favorites.

[FrankB]

Actually lately I like POI files better than Saved Waypoints.

Saved Waypoints increase the boot time for the Zumo. (At least for my XT)
It's so much easier to delete them. Try to delete all Saved Waypoints from an imported GPX.

Very useful for 'Streckensperren' !
https://frankbijnen.github.io/TripManag ... files.html

[rhoenschrat]

Saved Waypoints increase the boot time for the Zumo. (At least for my XT)

Interesting - wasn't aware of this.
I mean I realized that the Zumo has mor struggles to load, the more you put on it, but had no idea what exactly is the issue.
Especially the switch into MTP mode takes ages, once you have a bunch of stuff on it.

It's so much easier to delete them. Try to delete all Saved Waypoints from an imported GPX.

I guess you mean by just deleting the POI (.gpi) file, right?
But this requires to connect to a computer to remove the file, isn't it?
On the XT2 I used to put almost every import into an own collection. So it's quite easy to select all waypoints of a selection and delete them.