Zumo User Forums

Posted: **Sun Apr 26, 2026 9:37 am**

FrankB wrote: Sun Apr 26, 2026 5:17 am
jfheath wrote: Sat Apr 25, 2026 11:44 pm I cannot understand why route points made from waypoints are not affected by this import step - unless it is to do with the fact that waypoints are imported and stored first. So when the gpx file is imported and the lat, long coordinates are used to look up known locations, it treats its stored waypoints as known locations. That seems feasible. Whether or not it is right, I do not know.
It has always been my assumption that when the 'Waypoint gets copied in the route by BaseCamp' the <Subclass> in the created route point is set to 'Direct Routing'.
Code: Select all
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass> 

I knew that MyRouteApp used this trick to keep route point names. I had not realised that Basecamp did the same thing. You probably told me years back, and I related it to what I had seen in MRA.

So since I have one, I'll illustrate the point - for anyone else looking in.

The waypoint has already been declared at the top of the gpx file with its own <wpt> ..... </wpt> tags. Like this (I've stripped out the various extension information

Code: Select all

<wpt lat="54.180555297061801" lon="-2.085308292880654">
    <time>2026-04-26T07:53:07Z</time>
    <name>10 B6160 WP Via</name>
    <sym>Anchor</sym>
    <type>user</type>
  </wpt>

The first route point in the code below repeats the same lat/long coordinates, and duplicates exactly the same name and the same symbol.

But as @FrankB pointed out, that first point (which is derived from a waypoint) has its own subclass.

The very next point also has its own subclass which (I believe then applies to the 6 points which follow) - the subclass contains all sorts of coded information about the road, junctions, speed limits much of which Frank has been able to decode.

Code: Select all

<rtept lat="54.180555297061801" lon="-2.085308292880654">
      <time>2026-04-26T07:53:07Z</time>
      <name>10 B6160 WP Via</name>
      <sym>Anchor</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>
        <gpxx:RoutePointExtension>
          <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
          
          <gpxx:rpt lat="54.180555129423738" lon="-2.085308209061623">
            <gpxx:Subclass>0500597AF4016E151000211600002E024201</gpxx:Subclass>
          </gpxx:rpt>
          
          <gpxx:rpt lat="54.180965423583984" lon="-2.085492610931397" />
          <gpxx:rpt lat="54.180965423583984" lon="-2.085492610931397" />
          <gpxx:rpt lat="54.181716442108154" lon="-2.08566427230835" />
          <gpxx:rpt lat="54.182767868041992" lon="-2.086179256439209" />
          <gpxx:rpt lat="54.184441566467285" lon="-2.087702751159668" />
          <gpxx:rpt lat="54.186222553253174" lon="-2.088668346405029" />
 
          <gpxx:rpt lat="54.18705940246582" lon="-2.089033126831055">
            <gpxx:Subclass>0500597AF4016E1510001F001A00FEBB1100</gpxx:Subclass>
          </gpxx:rpt>

The above code is from the gpx file created by Basecamp.

Below is the same section of code that appears in Current.gpx - ie once the Basecamp gpx file has been imported into the Zumo XT2

Note that the lat/long figures have been rounded off to 6 decimal places - which is about 11cm, which is accurate enough !
Also that the 000000000000FFFFFFFFFFFFFFFFFFFFFFFF subclass has gone. But once imported, the Trip file has already been created so route point names cannot be changed again.

It cannot be seen in this snippet of code, but the two test points that were not defined as Waypoints both had their names changed in Current.gpx.

Code: Select all

<rtept lat="54.180556" lon="-2.085310">
      <name>10 B6160 WP Via</name>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode></trp:ViaPoint>
          <gpxx:RoutePointExtension>
            <gpxx:Subclass>80010000018000f0ffff0326fe0044876184</gpxx:Subclass>
            
            <gpxx:rpt lat="54.180553" lon="-2.085310">
              <gpxx:Subclass>0000597af4016e151000211600002e024201</gpxx:Subclass></gpxx:rpt>
              
              <gpxx:rpt lat="54.180966" lon="-2.085493"/>
              <gpxx:rpt lat="54.181717" lon="-2.085664"/>
             <gpxx:rpt lat="54.182769" lon="-2.086179"/>
             <gpxx:rpt lat="54.184442" lon="-2.087703"/>
             <gpxx:rpt lat="54.186223" lon="-2.088668"/>
             
             <gpxx:rpt lat="54.187060" lon="-2.089033">
              <gpxx:Subclass>0000597af4016e1510001f001a00febb1100</gpxx:Subclass>
            </gpxx:rpt>

Curiously - I have just put the same route into MRA and exported the gpx files (both types 1.1 and 1.2) and it no longer seems to include the subclass fields.

Posted: **Sun Apr 26, 2026 1:29 pm**

jfheath wrote:
I have assumed that when you said ‘less susceptible to change’ that you meant changes to the route points.

Correct. I was not thinking about RUT. That is a whole other issue, as you point out.

And, I had forgotten about the affect of the ... 000FFF... subclass. Frank's observation there makes perfect sense. Route points copied from waypoints probably don't get messed with because of that subclass.

I'm not sure, but I think having no subclass specified has a similar affect as the ...000FFF...

In general, I never have problems with any points (via or shaping) getting moved or renamed. I think there are 3 reasons for that:
1. I avoid the Tread App entirely.
2. I often install routes onto my XT2 with Trip Manager.
3. I often run my routes through Trk2Rt, which does not export any subclass information at all, just location name and type.

Code: Select all

    <rtept lat="44.0676" lon="-73.383">
      <name>02: Burlington, Lake Placid-1</name>
      <extensions>
        <trp:ShapingPoint />
      </extensions>
    </rtept>

If those points then go through Basecamp, they get exported with the ...000FFF... subclass.

Code: Select all

    <rtept lat="44.067600024864078" lon="-73.383000008761883">
      <time>2026-04-26T13:15:44Z</time>
      <name>02: Burlington, Lake Placid-1</name>
      <sym>Flag, Blue</sym>
      <extensions>
        <trp:ShapingPoint />
        <gpxx:RoutePointExtension>
          <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>

In case someone is wondering about my order of processing, it is Rever -> Basecamp -> zumo.
I often start my route planning with Rever, due to its Butler Map overlays, convert to Garmin's world with Trk2Rt, review and tweak in Basecamp, then install the route onto the XT2 with Trip Manager. It is much simpler than it sounds, and results in reliable routes, at least for me.

Posted: **Sun Apr 26, 2026 2:56 pm**

smfollen wrote: Sun Apr 26, 2026 1:29 pm In general, I never have problems with any points (via or shaping) getting moved or renamed.

I never have either. I have always (perhaps mistakenly) attributed it to creating routes in Basecamp mostly using points created with the New Waypoint tool. That said, I went through a testing period using the Insert tool and the rubber band method to shape routes that contained only begin and end waypoints. I did not notice any point renames or moves with those routes either. This was before TripManager.

Zumo User Forums

Loading BC GPX files into XT3

Re: Loading BC GPX files into XT3

Re: Loading BC GPX files into XT3

Re: Loading BC GPX files into XT3