Introducing TripManager

[FrankB]

That is what I did, showed the track on the XT map then loaded the route, let it calculate, then looked for any exposed track line.

OK. That should work.
When you have the time please have a look at this method using TripManager. The advantage I see is that you can do the compare on your computer's monitor. But I'm really interested what you think.
https://htmlpreview.github.io/?https:// ... /README.md
Option 7 Checking, comparing, the trip with the original GPX route.

[FrankB]

I just said that I like the "shape route" function of the XT but I have just realized that its propensity is to place added shaping points at the nearest intersection. ...... What are your thoughts on whether this is a potential problem?

Well I also avoid doing that. My experience dates back from the Zumo 220. (The 220 had no knowledge of Via and Shaping points) It made the anouncements difficult/useless.

I still avoid it with the XT. I can think of 2 cases:
1. The junction is (temporarily) closed and you have to take a detour.
2. Mainly with small to medium sized villages they tend to create roads around them, to avoid traffic passing thru the main road.

If this is a problem with respect to the calculation I wouldn't know.

[FrankB]

@Peobody

There are 2 things left.

Why was the result of the recalculation by pressing skip different?
I'm willing to take a look at your files. My problem is that I dont have your CN USA maps. So I would have to look at them with OSM maps, and that in itself could cause all sort of differences.

Did V1.1.0.121 fix the transfer of multiple GPX files?
And, provided it works, what do you think of the Grouped display in the TripManager? TripManager always groups the trips from a GPX if you transfer trips. Should it have an option to disable that?

Frank

[lkraus]

I nearly always place my shaping points at intersections, but never at an intersection where I might turn. It's the easy way to drag and drop a route in BC without editing each point's alert status later.

Shaping points in intersection turns do work, but I do not use them. I want to preserve my option to change a shaping point to a via point. The alerts for an approaching via point take precedence over the turn instructions, so I never want a via in a intersection turn. I have also had a via converted from a shaping point, in a intersection turn, cause my XT to actually reboot when I reached the intersection.

[Peobody]

Why was the result of the recalculation by pressing skip different?

That is indeed a curiosity. One would expect the original calculation and a recalculation triggered by a skip to produce the same results, especially when the skip occurred early in the route but the variation was well into the route.

Did V1.1.0.121 fix the transfer of multiple GPX files?

I will let you know. I need to clean out the XT and do some work on some of the route in Basecamp before I try again.

[Peobody]

I'm back to confirm that v1.1.0.121 fixed the transfer of multiple GPX files.

Thanks Frank!

[HarryMJ]

Hello Frank,

Seems like only GPX files exported from BC will work correctly, is that a correct assumption?

I have a planning tool (TourStart), and when I export a route to GPX, then send it to the XT with TripManager will all look correct with the .trip file, but does not show in the Trip Planner.

If I import the same file to the SD card on the XT, and then export it from BC, then send it to the XT with Tripmanager, then will the file show up in the XT Trip Planner.

I have attached a file exported from TourStart that have this issue, exported as route.

Brgds. Harry

[FrankB]

Hello Harry,

Seems like only GPX files exported from BC will work correctly, is that a correct assumption?

No, GPX files from other planners should work. Provided they meet some basic standards. The truth is that I have only tested BC and MRA V1.1

I have attached a file exported from TourStart that have this issue, exported as route.

I had a look at the GPX (Thanks for that) and I can see what's bothering TripManager. The Name of the trip is in the !CDATA format. When I change that to 'normal characters' it loads just fine.
This is what I changed:

I will see if I can change the program to accept also that format. Maybe you can check if there is a setting in TourStart to get only 'normal characters''?
(maybe it's enough to replace the last character. The a with a little circle on top)

compare.jpg (157.82 KiB) Viewed 1902 times

How it looks on my XT after importing.

8681.png (503.4 KiB) Viewed 1902 times

7512.png (115.77 KiB) Viewed 1902 times

6943.png (119.04 KiB) Viewed 1902 times

Frank

[HarryMJ]

Hi,

Thank you for that... so TripManager do not like the Danish characters .
I will just use the standard characters in my route planning, do not make to much effort into accepting these, I can easily leave such characters out.

TripManager is amazing, just found that I can group my trips

Brgds. Harry

[HarryMJ]

Hi Frank,

I just realized that the issue is with TourStart.... no matter what I do, regarding standard characters (no Danish characters), TourStart will export the file with these CDATE lines.

Brgds. Harry