Double Route Line on Importing BC GPX route

[LQQK_OUT]

I'm just going to compare the <rtept> commands in the Basecamp file with the ones that have been created in the Zumo XT (from Current.gpx). I have a sneaking suspicion that the route points are getting out of synch when the XT2 processes it. We shall see.


I might move all of these posts to its own new thread (eventually). If I do I'll leave a temporary pointer to it in this thread.

Sounds good!
As I mentioned earlier, I have a couple of routes in Basecamp that behave the same way.
I do think it's a software bug.

[jfheath]

Ok that's enough for tonight.

Summary - I have a 5 point route showing just the 4 route points after the Brio Pizza Waypoint. It shows simialr symptoms.

From Basecamp

5 Point Route BC Screenshot.png (532.85 KiB) Viewed 1383 times

5 Point Route List BC.png (197.3 KiB) Viewed 1383 times

From the XT Screen

5 Point Route XT2 Map.png (1.15 MiB) Viewed 1383 times

5 Point Route XT2 List.png (122.66 KiB) Viewed 1383 times

And it won't let me attach text files but I can copy and paste the content.

From the GPX file sent from Basecamp. Showing just the route points and names

5 Point Route RTEPT Tags - BC.TXT
============================

<rtept lat="42.083225687965751" lon="-74.315442061051726"><name>Brio's Pizza and gas to the left</name>
<rtept lat="42.118201106786728" lon="-74.381698742508888"><name>7302 Hwy281121</name>
<rtept lat="42.034346116706729" lon="-74.431898798793554"><name>Catskill Park81121</name>
<rtept lat="41.990647902712226" lon="-74.494706075638533"><name>1926 Frost Valley Rd1</name>
<rtept lat="41.899555390700698" lon="-74.58076324313879"><name>703 Claryville Rd21</name>

From Current.gpx - ie the route once it has been imported into the XT2

I have just extracted the lat/long ccordinates and the name for each point from the gpx file.

5 Point Route RTEPT tags Current gpx.txt
=================================

<rtept lat="42.083224" lon="-74.315446"><name>Brio&apos;s Pizza and gas to the left</name>
<rtept lat="42.118192" lon="-74.381712"><name>RT-28</name>
<rtept lat="42.034336" lon="-74.431902"><name>Shandaken Twn</name>
<rtept lat="42.034336" lon="-74.431902"><name>Shandaken Twn</name>
<rtept lat="41.990648" lon="-74.494708"><name>Frost Valley Rd</name>

Conclusion

Look at the lat/long coordinates. The route on the Zumo has taken the first 3 points OK, then it has repeated the third point and then added the fourth point. It clearly knew how many points there were - 5 - and it has stopped creating the route points after its 5th - actually missing off the actual end point.

This has all the appearance of a programming error. Goodness knows what cause it to repeat point 3, but whatever it is, it could happen again. I wonder if there is an odd character in the tags following that particular route point that has caused a particular section of the program to abort unexpectedly, and as a result it has skipped the command to increment the route point counter.
(Sorry, many years of teaching programming and fault finding in students' coding)


@LQQK_OUT - if you want the original files to pursue this, I can send you all of them - but I'd need an email address as I cannot post them all as attachments.

[jfheath]

Addendum to the last comment.

There are two parts to each route point - the stuff that goes with the route point name, lat/long, the type of point: shaping / via and a Gpxx subclass
Typically about 6 lines.

And then all of the gpxx:rpt ghost points and subclasses. Lots of lines.

In the XT2 verison of the route it is the first part of the rtept that is wrong. The 4th route point has got the location and name and sublcass for the third route point. All of the ghost points are declared correctly.

So we have rtept for section 1 Brios Pizza
Ghost points for section 1 after Brios Pizza

rtept for section2 from Rt28
Ghost points for section 2 after RT28

RtePt for section 3 from Shandaken Twn
Ghost points for section 3 after Shandaken Town

RtePoint for section 3 Shandaken town (Wrong, itshould be frost valley road)
Ghost Points for Section 4 from Frost Valley Road

Rte Point for Section 4 Frost Valley Road. (wrong, it should be Claryville Road)
End of Route

[LQQK_OUT]

I called Garmin support again today. I explained the situation and uploaded the test file that jfheath generated. The support person ran a couple of tests and then mentioned to me that Basecamp is not a supported platform with the Zumo XT2. He generated the GPX file using the Tread application and said it worked.

So there you have it. Basecamp is generating a GPX file that the Zumo XT2 doesn't know how to process. I now need to move to MyRoute-app.

https://www.myrouteapp.com/en/home

[Peobody]

He generated the GPX file using the Tread application and said it worked.

Did he just process your gpx file through Tread or did he create a new route? If the later, then it sounds like he is saying that if you don't create the route in Tread, in may not work. This then warrants a discussion about .gpx files from others sources, like a download, or a route created and shared by a riding buddy.

[jfheath]

So they provide the means to import GPX files from other sources and don't care less if their software screws it up (if that is what it is).

I'm not surprised by the answer. There was a reason that they update the Basecamp software of late. Now we know that it was to put out a message. I think that same problem could arise with any route from any other software.

[Peobody]

I just finished reading through this discussion again. I don't have and XT2 so feel a little bit like a fish out of water but a couple of things struck me that I think are worth mentioning.

First, the route in the XT appeared fine however there were numerous duplicately named route points. I think there were three "RT-28" and two "Shandekan Twn". The number of Via and Shaping points shown on the XT map corresponded to the number of points in the routes list so I don't think they were duplicate points. I did not look at coordinates and have since cleaned after testing so can't easily check it. @jfheath, would this be an instance of renamed route points by the XT, an issue that you have mentioned often but I have rarely experienced?

Second, the first response by @jfheath contains an image of the Basecamp route points list. I see names like "7302 Hwy281121", "Catskill Park81121", and "703 Claryville Rd21". Typically, numbers suffixed to the street address indicate the sequential number of the occurrence of that address as a route point in Basecamp. I can't imagine that there are 1121 route points in Basecamp with the name "7302 Hwy28" so is there an explanation for these numerical suffixes?

[jfheath]

I just tried something on a whim.

I moved points 3 and 4 of the 5 point route slightly. Then transferred to the XT2.
The route list now had the correct points in the correct order. None missing.
But the map still showed the same sort of shape with the extra stright line limb. But the two shaping points that I moved slightly were now almost on top of each other.

Shaping point have adopted a fuzzy logic - the jump to a recognised point that is near the location but on the faster route between adjacent points. It is behaving as though that date is skewed. But again - recalculating on the XT sorts it out. But you lose your original BAsecamp route.

And that is another good reason for making a track in Basecamp and exporting that to the same Collection.
At least we have the RUT situation sorted if it is copied - Oh - thats a good idea. I'll try that.

No. Same issue on the original route - It starts to split at RT-28. I wonder if it matters that the 2 shaping points have the same name . So do the next pair.

[Peobody]

No. Same issue on the original route - It starts to split at RT-28. I wonder if it matters that the 2 shaping points have the same name . So do the next pair.

I also wonder if it would matter if they were created with the Waypoint tool, renamed if any had a duplicate name, and then changed to shaping points.

[smfollen]

@LQQK_OUT Do you have Tread syncing to your XT2?
If so, the issue here may be Tread, not Basecamp.
I have had good success with routes created in Basecamp and exported to the XT2, however, I have seen Tread make significant changes, including creating duplicate shaping points.
See viewtopic.php?p=22678#p22678