Can Basecamp assign Route preference to each segment ?

[jfheath]

Once upon a time, I'm sure that someone made a comment that this was possible.

eg a few segments (between Vias) set as Faster Time and one in the middle set as 'Direct'

This in order to get around a section of route that was incorrectly mapped for example.
I've searched, but cannot find it, and so far I have been unable to get it to work on Basecamp.

You can select individual segements of a route - but how to change properties of just that segment ?

[Peobody]

To set the Profile of a specific segment you open the properties of its starting route point and change is Profile. Must do this from a route detail window.

CnP_06092025_112625.png (155.41 KiB) Viewed 1039 times

[FrankB]

As I understand it, but I have never actually used it for a trip.

What you assign is a profile. That profile has a route preference. Faster Time, Shorter Distance and Curvy roads. When you expert it to a GPX you can find that in <trp:CalculationMode>CurvyRoads</trp:CalculationMode>

BTW @Peobody Your example shows a Shaping point. The CalculationMode is ignored for Shaping points. It is not exported to the GPX

[Peobody]

I just grabbed a test route to use to show where the route point profile setting. I think I have only done it with with Via points although my usage has always been to force Basecamp to route between two route points so I wonder whether the CalculationMode not being in the GPX was relevant if the ghost points were, as long as a recalc didn't happen.

[jfheath]

Ah thanks, @Peobody .
I was looking for the wrong thing.
I'll check out what the gpx file looks like after this has been applied.

[FrankB]

so I wonder whether the CalculationMode not being in the GPX was relevant if the ghost points were, as long as a recalc didn't happen.

First of all, sorry if my previous response was to blunt. Your answer was correct.
I was trying to warn, not specifically you, but anyone who tries this, that setting this on a shaping point can easily result in data getting lost.

Consider this small route in BC:
The start and end have MotorCycling Fastest, The Via and Shaping have MotorCycling Shortest

BC_start.jpg (69.15 KiB) Viewed 1014 times

With my profile definitions when exported this results in a GPX that has NO CalculationMode for the shaping point.
Start:

Code: Select all

    <rtept lat="51.391277108341455" lon="6.171882385388017">
      <time>2025-09-07T08:57:09Z</time>
      <name>Start Fastest</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>

Shape:

Code: Select all

    <rtept lat="51.401350563392043" lon="6.211706651374698">
      <time>2025-09-07T08:58:00Z</time>
      <name>Shortest Shape</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ShapingPoint />

Via:

Code: Select all

    <rtept lat="51.408070921897888" lon="6.220527095720172">
      <time>2025-09-07T08:58:05Z</time>
      <name>Shortest Via</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>ShorterDistance</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>

End:

Code: Select all

    <rtept lat="51.435713768005371" lon="6.256842613220215">
      <time>2025-09-07T08:57:13Z</time>
      <name>End Fastest</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>

It gets even worse when you import that GPX back in BC (Delete first if you try this)
Every thing is reset to the default MotorCycling. I assume that is based on the TransportionMode. But the key point to remember is that when BC imports a GPX it does not always use the CalculationMode of the Via/Shaping points.

BC_after.jpg (57.54 KiB) Viewed 1014 times

For the XT (that we both have) you would indeed have to make sure the trip/route does not get recalculated.
The trip file format only has 1 setting for the RoutePreference=Calculationmode. There are no items per Segment as the XT2 and Tread 2 have. So it can only use 1 mode for the complete trip.

For the XT2, and Tread 2, you can set the RoutePreferences for every segment in the Tread App. A segment is from one Via to Another Via. It can not be set for Shaping points. I can tell that by looking at the trip file format, not because I know how the Tread App works.
It would need to be tested if the GPX import process uses the CalculationMode to set the correct values in trip file.

[jfheath]

I was just looking at that this morning.

The Calculation Mode is changed to the default Motocycling by Basecamp on Export - and it doesn't contain any information about routing - it just alerts the Zumo that if it recalcualtes, then it should use the settings that are in the Zumo in the Motrocycle Profile. The values used in the Motorcyling Profile in BC never have had any realtionship with the settings in the Zumo.

So - I did the same experiment that you have just done. A route with various Transportation methods. and what you get is every via point with the Faster / Shorter / Direct routing preference that was associated with the profile in BC. If you use a profile that is not valid, then it uses a default.

This is one where I used the Off Road Profile in Basecamp

eg

Code: Select all

 <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>ShorterDistance</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>
        <vptm:ViaPointTransportationMode>
          <vptm:TransportationMode>OffRoad</vptm:TransportationMode>
        </vptm:ViaPointTransportationMode>
        <gpxx:RoutePointExtension>

But it didn't like Transportation Modes or Calculation Modes that it didn't know about.

So I started to mess around with the windows registry for Basecamp - and created my own vehicle profile in there - 'Adventurous'. This, I thought would give it something that it did know about - or at least put a word or phrase in the GPX file that TM could latch on to. So I evented a profile 'Adventurous' which Basecamp recognised. I thought that the routing preferences would be picked up from my Adventurous profile.

No. 'Adventurous' is replaced in the GPX by 'Motorcycling' and the Calculation Mode is set to whatever is set in Basecamp for the calculation mode for the Motorcycling profile - Shorter DIstance in the above example.

That is exactly what happens if you create a new profile using Basecamp. I tried that years ago.

I used to have a DLL editor when I started writing programs for Windows using Borland Tubo C, but That has long gone. You used to be able to edit dialogue boxes and change the values that were set by check boxes - for other programs. (check boxes are the things that are used for faster, shorter, curvy etc. They are given a value in certain registry keys - but it would need a checkbox and value and the program would need process the check boxes without caring what they were. Just do the same thing n times. Once per check box on the form. I suspect that does not happen.

I gave up on that. If it was something that turned out to be a desirable feature, it would be far easier to create a GPX file using the Tread App and Export it, and feed that into TM. But since TM is a superb tool to avoid that software, using Tread would seem an odd route to take. (Ho Ho !)

Nb - It is not possible to use the Tread app on phone or on ipad, unless the device is first linked to the Tread app. And that link is what causes the route changing problems. I've found a way around it - so I can not have Tread App synching to my phone, but I can use the App on my ipad.

nb - There is no Web based equivalent of Tread. You can see your collections, routes waypoints and tracks on the Explore Web-based app, but it gets confused about which device created it and it ends up not synching. So you have to make an edit (eg to the name) and synch. Then it sysncs it to the XT2 - with a new UUId. Whenever I have done that, I have had old trips left in the trips folder after everything has been deleted. Everywhere I look in tread there seem to be some very simple programming errors. They check to see whether it works. It seems that they don't try to provoke failure.

For Adventurous, I reckon that it would be easier to do something in Trip Manager, display the identified segments and provide a selection box for adventure level for each segment. Otherwise do what the Zumo does - default to zumo Motorcycle/ Faster.

But this is just an interesting observation. I do not for one minute think it is something you should take on. It's not something I would use anyway - Garmin's idea of adventurous routing and mine are at complete odds with each other - which I am quite pleased about actually. I know the really nice motorcycle rides in these parts. And usually none of the XT2 settings will choose 'my' roads.

Thankfully the sort of motorcyclists that I would rather not share a road with seem to be the ones that cannot read maps !!

[Peobody]

First of all, sorry if my previous response was to blunt. Your answer was correct.
I was trying to warn, not specifically you, but anyone who tries this, that setting this on a shaping point can easily result in data getting lost.

No worries. I get it. Setting a profile for a single leg is useful in Basecamp but on the device, that usefulness is lost once the ghost points are gone. This is valuable to know since the trick of using a Direct route point to force routing now should come with the disclaimer that a device calculation will break it.

[LQQK_OUT]

I've pretty much given up on Basecamp and primarily use MRA to create my new routes.
MRA alliows you to do what you are asking. One can set a shaping point or a waypoint with the option "skip".

https://support.myrouteapp.com/en/suppo ... ecognized-

[Peobody]

I've pretty much given up on Basecamp and primarily use MRA to create my new routes.
MRA alliows you to do what you are asking. One can set a shaping point or a waypoint with the option "skip".

https://support.myrouteapp.com/en/suppo ... ecognized-

This appears to produce the same result as using the Direct route point trick in Basecamp. This forces Basecamp to route between two points that it would not otherwise do but what I have since learned is that a recalculation of the route by the device will likely circumvent the stretch of road that Basecamp was forced to route over. I suspect that the same would occur with an MRA created route. Do you know?