Zumo User Forums

Can someone explain how Basecamp is creating a non-simple route with multiple turns via this simple route I received that only has (2) waypoints. The route generated via this same GPX file by MyRoute-app is completely different and what you would expect. The route created via MyRoute-app is the quickest way from point 1 to point 2.
How is Basecamp generating this route?
GPX file attached.

The gpx file specifies curvy roads

smfollen wrote: Mon Oct 20, 2025 8:52 pm The gpx file specifies curvy roads

Code: Select all

<trp:CalculationMode>CurvyRoads</trp:CalculationMode>

Thank you!

smfollen wrote: Mon Oct 20, 2025 8:52 pm The gpx file specifies curvy roads

Code: Select all

<trp:CalculationMode>CurvyRoads</trp:CalculationMode>

What options do I have to check within Basecamp (route options) to get the same route when I recalculate the route? I can't seem to duplicate this. Whenever I recalculate the route, it's different from the original.

OK. I think this has something to do with creating a route from a track within Basecamp.
So, the question I have is:
If I create a route from a track within Basecamp, can I take the created Waypoints and generate an exact same (or very similar) copy of the original track from the new route? I don't think you can.

LQQK_OUT wrote: Mon Oct 20, 2025 10:51 pm OK. I think this has something to do with creating a route from a track within Basecamp.
So, the question I have is:
If I create a route from a track within Basecamp,

You will get a route in which the start and end points become your only via points, and the track points become "ghost" points, so the new route will match the track exactly.

can I take the created Waypoints

There are no new waypoints, nor via points.

and generate an exact same (or very similar) copy of the original track from the new route?

The new track will match the original track.

But if you let the new route recalculate (in Basecamp or on the GPS), the currently active routing preferences are used to reach the end point, ignoring the original track entirely. To safeguard the original path, add via and shaping points to the newly created route.

Here is some background information.
I went on a charity motorcycle run this past weekend. Along with a route sheet, I had one of the club members send me the GPX route and track. There were a total of four files, two GPX files for the "outbound" portion of the run (route and track files) and two GPX files for the return trip (route and track file).

The outbound GPX file had 55 shaping/waypoints. Worked perfectly fine on my Zumo XT2

The return GPX file is what I posted, and it had only two waypoints. Obviously, my Zumo XT2 wanted to route me directly to the end point.
Why would anyone want to create a GPX route file for a motorcycle run that people are going to load into a GPS device that contains "ghost" points? That doesn't make any sense to me.

I assume you selected the end point, if you'd selelected the start point it would have taken you there and then along the route to the end point.

You have a route file.
It contains two Waypoints - defined using the <wpt> tag at the top of the gpx file.

The waypoints are marked on the Zumo screen with Blue Flags - these are named as

2025 RMC FFR Return Track1
2025 RMC FFR Return Track2

The route goes from ...Track1 to ...Track2 - that is, from west to east (left to right).

These two waypoints are set to be the start and finish points of the route (a type of Via Point)
There are no other via points in the route (which show on the Zumo screen as Orange Flags)
There are no shaping points in the route, which show as blue discs on the Zumo.

There are ~1370 invisible route points - ghost points (properly named GPXX route point - route point extensions).

Route point extensions are items created by Garmin to make sure that the route that you plot on (say) Basecamp is drawn with 100% accuracy on the zumo screen. MyRouteApp uses the same technique in the gpx file that it exports as v1.2

However, if the Zumo deems it necessary to recacluate the route, it is replacing the existing route with a newly calculated one. And for that to happen, all of the existing gpxx 'ghost points' are deleted and new ones obtained. ie the roads that the route travels will be changed.

The route can be recalculated for any number of reasons:

1. There is a setting in Basecamp which demands that the route is recacuated on transfer (in Edit / Options / Device Transfer)
2. If the maps on the Zumo are different from the ones used to create the route. A prompt is issued which you can refuse
3. If the transportation method is different in the file fromt he one set in the Zumo
4. If the avoidances have been changed recently in the Zumo
5. If you deviate from the route.
6. if you are receiving traffic and road closure infor via your phone

You can avoid all of these by not allowing the Zumo to recacluate the route when prompted.
Also ensure that automatic recalculation is turned off.
And that traffic data is not being relayed from your phone (some Zumos do not prompt - they just recaclulate the route.

If there were shaping points in the route or more via points then any recalculated route would have to pass through each of those points in turn.

In your case there were no additional shaping points or via points. If you skipped the start point, or if the route was recalculated, it would take you to the next route point in the best way it knew how - probably / possibly using the faster road direct to the end point. That would depend on your zumo and what it's internal setting were - and possibly on earlier Zumos - which cradle it was in.


** Do not confuse the term 'Waypoint' with either 'Via Point' or 'Shaping point'. They are not the same thing - no matter what any one else may tell you. (This is a Zumo forum, so I use Garmin and Zumo definitions.)

Click the map for a larger image.

LQQK_OUT wrote:
...
What options do I have to check within Basecamp (route options) to get the same route when I recalculate the route? I can't seem to duplicate this.

As others have said here, a route is calculated from the user specified route points - that is the via and shaping points (not the waypoints, although waypoints may be used as via or shaping points).
In addition, the resulting calculated route depends on user specified setting for route preferences (e.g. faster road vs shortest distance) and avoidances (e.g. avoid highways), as well as the map being used and the routing algorithm (which varies between software and devices). If all of those variables are the same, then the same route will be calculated, but that is a big if.

This is not specific to Basecamp. Most any route planning software or nav device works more or less this way, although names may change.

Basecamp uses "Activity Profiles". The profile for a route can be selected at upper right of the route dialog.

They can be created and edited by opening the Activty Profile dropdown at top right of the main page and selecting Edit Activity Profiles...

There you can set routing preferences and avoidances.

All of that affects how Basecamp calculates a route.

Only a bit of that information is included in an exported gpx file however.
Further, your zumo XT2 supports only the motorcycling profile and has its own route preference and avoidance settings.
You can find "Calculation Mode" and "Avoidances" under Settings -> Navigation->
Those take affect if your zumo recalculates the route - see @jfheath post above.

As @lkraus pointed out, adding via and / or shaping points to a route will help to hold the route where you want it.
Any device or route planning software should always calculate a route through all specified via and shaping points.

The Trip Manager software provided to us by @FrankB has a very helpful feature to compare a gpx file route to a zumo calculated route and can add points to the zumo route as desired. You can find it via this post viewtopic.php?t=3150