Waypoints are defined individually and separate from the route - usually at the very top of the gpx file.
Like this
Code: Select all
<wpt lat="53.944583432748914" lon="-1.889413995668292">
<time>2025-09-01T14:03:34Z</time>
<name>04 Ignore Addingham ShPt</name>
<cmt>38 Main Street
Addingham, W.YORKS, LS29 0, GBR</cmt>
<desc>38 Main Street
Addingham, W.YORKS, LS29 0, GBR</desc>
<sym>Flag, Blue</sym>
<extensions>
<gpxx:WaypointExtension>
<gpxx:DisplayMode>SymbolAndName</gpxx:DisplayMode>
<gpxx:Address>
<gpxx:StreetAddress>38 Main Street</gpxx:StreetAddress>
<gpxx:City>Addingham</gpxx:City>
<gpxx:State>W.YORKS</gpxx:State>
<gpxx:Country>GBR</gpxx:Country>
<gpxx:PostalCode>LS29 0</gpxx:PostalCode>
</gpxx:Address>
</gpxx:WaypointExtension>
<wptx1:WaypointExtension>
<wptx1:DisplayMode>SymbolAndName</wptx1:DisplayMode>
<wptx1:Address>
<wptx1:StreetAddress>38 Main Street</wptx1:StreetAddress>
<wptx1:City>Addingham</wptx1:City>
<wptx1:State>W.YORKS</wptx1:State>
<wptx1:Country>GBR</wptx1:Country>
<wptx1:PostalCode>LS29 0</wptx1:PostalCode>
</wptx1:Address>
</wptx1:WaypointExtension>
<ctx:CreationTimeExtension>
<ctx:CreationTime>2025-09-01T14:03:34Z</ctx:CreationTime>
</ctx:CreationTimeExtension>
</extensions>
</wpt>
This happens whether or not the waypoint is used in a route.
In a route, the point is declared again, using the same data. Here is the same waypoint used as part of a route - as produced by Basecamp.
Code: Select all
<rtept lat="53.944583432748914" lon="-1.889413995668292">
<time>2025-09-01T14:03:34Z</time>
<name>04 Ignore Addingham ShPt</name>
<cmt>38 Main Street
Addingham, W.YORKS, LS29 0, GBR</cmt>
<desc>38 Main Street
Addingham, W.YORKS, LS29 0, GBR</desc>
<sym>Flag, Blue</sym>
<extensions>
<trp:ShapingPoint />
<gpxx:RoutePointExtension>
<gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
<gpxx:rpt lat="53.944583432748914" lon="-1.889413995668292">
<gpxx:Subclass>0500BA0DED01281B10002116000052001B00</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="53.94463062286377" lon="-1.889712810516357" />
<gpxx:rpt lat="53.94463062286377" lon="-1.889712810516357" />
<gpxx:rpt lat="53.944931030273438" lon="-1.890163421630859">
<gpxx:Subclass>0500BA0DED01441F10001F001E00D9D21300</gpxx:Subclass>
</gpxx:rpt>
<gpxx:rpt lat="53.944931030273438" lon="-1.890163421630859" />
<gpxx:rpt lat="53.945188522338867" lon="-1.890678405761719">
<gpxx:Subclass>0500BA0DED01601F10001F001E00C4D20500</gpxx:Subclass>
</gpxx:rpt>
.
.
.<Snip>
.
.
.
<gpxx:rpt lat="53.927082186564803" lon="-1.924656126648188">
<gpxx:Subclass>0600BA0DED0126030C0021170000DB004E00</gpxx:Subclass>
</gpxx:rpt>
</gpxx:RoutePointExtension>
</extensions>
</rtept>
In the example in a route, the waypoint has been set as a shaping point.
Before the XT2 - this was one way of making sure that the route point retained the name that you gave it.
With the XT2, the waypoint that is declared at the top remains intact, but when it is used in a route, it tends to be relocated and given a different name. So in effect, the waypoint is no longer part of the route. Instead, the waypoint is shown on the map, and a new routepoint with a different name and in a different position marks a completely different location. Closeby, but not always close enough.
I can think of a few places where I have used a Waypoint to mark the location of a car park for a hotel so that the satnav guidance take me to where I need to park. I take the trouble to use street view to find where I need to be. But sometimes my parking spot is not on a legitimate road and the route point (via / Shaping) will be moved by the XT2. So my route doesn't take me to the waypoint that I had plotted. The symbol will still appear on the map in the correct location - but the route will not necessarily go to it.
