Adventure tours exported from the Tread App cannot be imported into BaseCamp

[proofresistant]

Adventure tours exported from the Tread App cannot be imported into BaseCamp
BaseCamp has problems with the CalculationMode Adventurous and the associated AdventurousLevel 1 (Faster), 2 (FastAndAdventurous), 3 (Adventurous), 4 (ExtraAdventurous).
Routes exported from the Zumo XT2 Adventures works fine, they do not have an AdventurousLevel.
edit:
From another point of view, it is definitely not a good behavior that the XT2 cannot even remember the levels 1, 2, 3, 4 (but I am not surprised, no matter where I try to look a little deeper into the zumo XT2 functionality, it makes more frustration than pleasure).

(my) Solution:
Either change Adventurous in the Tread App,
or (with Texteditor Editor) "replace" / “hide” / "delete" in GPX File the Tag AdventurousLevel before importing.

Code: Select all

  <rte>
    <name>CEP Tst RatSol TreadApp v3</name>
    <rtept lat="51.287315357476473" lon="6.8178982101380825">
      <name>Start</name>
      <extensions>
        <trp:ViaPoint>
            <trp:CalculationMode>Adventurous</trp:CalculationMode>
            <!-- <trp:AdventurousLevel>Faster</trp:AdventurousLevel> -->
        </trp:ViaPoint>

[jfheath]

That is something I clearly haven't tried. Thanks for pointing it out. Basecamp is usually very good at cleaning out invalid commands, using a default if necessary.

Regarding the XT2 adventure level - it does know what level was set for a particular segment, but when you come to edit it, it doesn't move the slider to the correct position or reveal what it was.

I did some 'research' into what each level did. Garmin have a couple of places where they describe in words what levels 1 - 4 mean. Both are slightly different. On roads that I know well, I cannot get it to follow roads that I would regard as twisty and/or hilly. As with the XT1 and 595 , I prefer to use additional shaping points than rely on what roads the adventure level chooses. I also turn off the other routing options like michelin scenic.

[0709]

@proofresistant

Microsoft XML Notepad is quite unique in that, in addition to the GPX core, it also checks the Garmin extensions based on their schema.
https://microsoft.github.io/XmlNotepad/

Validation using this tool is therefore recommended by Topografix.
https://www.topografix.com/gpx_validation.asp

So apparently the Tread GPX export is incorrect after all?
viewtopic.php?t=3447

Basecamp so rightly rejects this GPX export because the file is not compliant.
The Garmin GPX extension has not been respected.

Kurviger web apparently has copied the Tread app export mode?
https://forum.kurviger.com/t/new-export ... 269?u=0709

[jfheath]

Welcome @0709

That is an interesting topic for a first post. I did a bit of digging around a couple of days ago - I was looking at how other route planners behaved.
Kurviger has made some signifcicant changes since I last looked and they seem to be attempting to do what the Tread app does - assign calculation modes to individual 'segments'. A segment is the portion of route between two via points - which may include numerous shaping points.

But when I looked - the terms that they used did not match those used by garmin.

For the record - I assume that you have done this, but for anyone else looking into this thread in the future - here is a Gpx file of a route that I created using the Tread App and exported it as a GPX file. It has 7 segements and each segment is given a different calcualtions mode. In order:
00 Faster time
01 Direct
02 ShorterDistance
03 Adventurous / Faster
04 Adventurous / FastAndAdventurous
05 Adventurous / Adventurous
06 Adventurous / ExtraAdventurous

All of the Adventurous Calculation Modes also had the 'AdventurousLevel' tag which is what the second name is in the list above. These tags corresponded in order to the XT2 Adventurous Level of 1, 2, 3 and 4.

Code: Select all

<?xml version="1.0"?>
<gpx version="1.1" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v1">
	<metadata>
		<link href="https://www.garmin.com">
			<text>Garmin Tread App™</text>
		</link>
		<time>1970-01-01T00:00:00</time>
	</metadata>
	<rte>
		<name>Tread Route Test</name>
		<rtept lat="53.961619986221194" lon="-2.0158299431204796">
			<name>00 Start</name>
			<sym>Flag, Green</sym>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>FasterTime</trp:CalculationMode>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="55.00131469219923" lon="-3.3080683741718531">
			<name>01 A75</name>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>Direct</trp:CalculationMode>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="55.122201684862375" lon="-4.1818307340145111">
			<name>02 A713</name>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>ShorterDistance</trp:CalculationMode>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="56.059849988669157" lon="-4.9842099566012621">
			<name>03 JFH Point</name>
			<sym>Flag, Blue</sym>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>Adventurous</trp:CalculationMode>
					<trp:AdventurousLevel>Faster</trp:AdventurousLevel>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="57.215533889830112" lon="-5.4235130455344915">
			<name>04 A87</name>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>Adventurous</trp:CalculationMode>
					<trp:AdventurousLevel>FastAndAdventurous</trp:AdventurousLevel>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="57.765489919111133" lon="-5.6045699492096901">
			<name>05 Via Point 5</name>
			<sym>Flag, Blue</sym>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>Adventurous</trp:CalculationMode>
					<trp:AdventurousLevel>Adventurous</trp:AdventurousLevel>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="57.951825745403767" lon="-5.1441134512424469">
			<name>06 A835</name>
			<extensions>
				<trp:ViaPoint>
					<trp:CalculationMode>Adventurous</trp:CalculationMode>
					<trp:AdventurousLevel>ExtraAdventurous</trp:AdventurousLevel>
				</trp:ViaPoint>
			</extensions>
		</rtept>
		<rtept lat="58.502009930089116" lon="-4.2750599607825279">
			<name>Destination</name>
			<sym>Flag, Red</sym>
			<extensions />
		</rtept>
	</rte>
</gpx>

But I notice one thing that is different in one of your screen shots. The use of the term 'Motorcycling' for the Transportation Mode.
The gpx file produced by the Tread App does not include a tranportation Mode. But when you look at the .trip file that the XT2 creates for each route it uses the term "zūmo Motorcycle"

All previous Zumos have set a default if the Transportation mode is not present, or if the Zumo doesn't recognise it. Perhaps (I don't know) the XT2 recognises the 'Motorcycling' Mode and doesn't switch to the default. By not putting anything int he gpx file, it switches to 'zūmo Motorcycle'.

Just a thought.

The other possibility is that the headers at the top of the gpx file are not pointing to the same formats.

That file included in the code box below was create by the Tread App, exported as a GPX file and then imported to the XT2. All of the settings for each segment in the route were set correctly.

Addendum

When the above route is sent as a gpx file to my phone and the phone opens it up with the Tread App the route is displayed ont e Tread App screen. Select Edit, and the route list shows each segment with the correct route level - Faster, Direct, Shorter, 1, 2, 3, 4.

However - when I import the same GPX file into the XT2 and let it sync via Tread and then select edit in the Tread app it shows different information

Faster, Direct, Shorter, 4, 4, 4, 4

I cannot check what values are set on the XT2 itself - as soon as you click Adventurous it sets the level to the level that was last selected - which is why I think the levels are showing as 4. That happens to be where I last moved the slider.

I'll move the slider to 2, delete the route and re-import the same route and see what it does then.

Yes - it has re-imported and levels are set as Faster, Direct, Shorter, 2, 2, 2, 2

[proofresistant]

@0709
Welcome and thanks for the good answers

Microsoft XML Notepad is quite unique in that, in addition to the GPX core, it also checks the Garmin extensions based on their Schema.
https://microsoft.github.io/XmlNotepad/

I'll take a look at it, but as a non-professional, Notepad++ with plugins should suffice for my needs.
Sometimes I simply rename gpx to xml and view the file in Edge.
OK, i don't recognize schemas, but at least I can see the formatting and read the file better.
And honestly, which schemas are in the background is too deep into development for me anyway.

So apparently the Tread GPX export is incorrect after all?
viewtopic.php?t=3447

Whether the schema doesn't fit the GPX or the GPX doesn't fit the schema, I'll leave that aside for now.
The fact is, the GPX contains Adventurous attributes that BaseCamp doesn't like, but other tools or Navi devices do, Even if they ignore some of the content.

Basecamp so rightly rejects this GPX export because the file is not compliant.
The Garmin GPX extension has not been respected.

Yes and no
May BaseCamp GPX extension has not been respected or may Schema is out of date

Kurviger web apparently has copied the Tread app export mode?
https://forum.kurviger.com/t/new-export ... 269?u=0709

It seems to be the same problem, Garmin may has problems with its own attributes



But anyway,
BaseCamp has stood still in time, while Garmin tools continue to evolve.
And so there are now functions that BaseCamp does not support.
BaseCamp can handle curvy routes that the zumo XT2 cannot understand, and the zumo XT2 can handle adventures that BaseCamp does not support.



@jfheath
Please also note
Transportation Mode = Motorcycling, Automotive, ...
and Vehicle Profile = zūmo Motorcycle, Motorcycle, car, ...

[proofresistant]

Addendum
Faster, Direct, Shorter, 4, 4, 4, 4
...
Faster, Direct, Shorter, 2, 2, 2, 2

Shown Identical Adventurous levels are probably (very likely) “just” a display problem in the zumo XT2.

The zumo XT2 remembers the levels correctly internally.
You can see the different values later in the Tread app, in the trip files, and in the calculation results.

[jfheath]

@jfheath
Please also note
Transportation Mode = Motorcycling, Automotive, ...
and Vehicle Profile = zūmo Motorcycle, Motorcycle, car, ...

Yes - you got me there ! That was a stupid mistake to make.

I have never seen the vehicle profile name in any GPX file. They only ever send the Transportation Mode. The early zumos used to use it to swithch to using the routing preferences being used when recalculating a route in the Zumos like the 590 where a different sets of preferences were stored for car and motorbike. Send it a car route it would switch to using the settings that were stored in the 590 for the car.

So when I saw the zūmo Motorcycle in the .trip files (I first saw it in the hex code) - I thought it was a new name for the transportation mode to distinguish it from the transportation mode that was sent by Basecamp. I mentioned it too, without challenge. And I must have made the assumption ever since.

So yes, many thanks for that. That clearly isn't the issue with the gpx file.

Its difficult to know whether the issue is the display of the number or with the route. I'd need to find a route between two points that calculated different roads for all 4 adventure levels. I also do not know whether the tread app calculates the same route (say) for level 4 as the Zumo calculates for its level 4. It ought to, but ....

[0709]

Well, the situation is this.
I don't have a motorcycle and haven't had a Garmin (cycle) GPS for over +10 years.
I sometimes still use Basecamp as a tool to quickly check whether a GPX file is valid.
This is also very effective for the many Garmin extensions with schematics.
Basecamp imports the compliant GPX files but rejects invalid GPX files without mercy.
However, Basecamp does not report the cause.
I also follow the Kurviger website to some extent.
According to forum members, Basecamp rejects the new Zumo XT2 export.
This is a good reason to investigate.
I use Notepad++ with the xml plug-in and the compare plug-in.
Notepad++ makes it easy to check and validate the gpx core.
Microsoft XML Notepad also checks the Garmin extensions.
This tool can be installed in no time.
@proofresistant.It is definitely recommended.

Although sometimes annoying, it is commendable that Basecamp is strict.
It seemed very strange to me that Garmin Tread gpx would violate the rules.

@jfheath
Thanks for the additional information and especially for the demo gpx file.
Very surprising.
- The result is file 1.
It lacks just about everything required for a compliant gpx1.1 file.
The file does not even import into some fairly tolerant GPS apps.
The file also does not import into Microsoft XML Notepad.

- Action.
Added encoding utf 8.
Added creator (mandatory).
Applied the topografix and Garmin extension schema references. (desired)
Change Ansi to utf8 and remove Trade Mark symbol in the Garmin Tread app text.
- Result is file 2_

The tolerant gps apps do import the gpx.
The strict Basecamp does not.

- Validation using Microsoft XML Notepad.
The error list shows you the (4) errors.
trp:AdvanturousLevel is therefore not allowed.
The Garmin extension has not been respected.
Garmin is violating its own schema here.

Strange, as Garmin was always exemplary in terms of gpx conformity.

The files in the zip.

Translated with DeepL.com (free version)

[proofresistant]

@proofresistant.It is definitely recommended.

OK,
I've now taken a look at XmlNotepad, but I haven't found out any more than I did before about the issue mentioned

The attribute value AdventurousLevel is the main problem

Thanks anyway for the new ideas
Hopefully you'll stay here with us, even if you don't ride a motorcycle (yet).


Then please take a look at my "o0Trd2 PrfTst BC FsTShDD.gpx" example, exported from the device.
Even with XmlNotepad, I don't see any fundamental structural problems.

o0Trd2 PrfTst BC FsTShDD.zip

(5.7 KiB) Downloaded 50 times

o0Trd2 PrfTst BC FsTShDD (XML Notepad).png (69.64 KiB) Viewed 636 times

I would be happy to receive your feedback.


PS
I also briefly read the thread you mentioned (forum kurviger.com new-export) and other things.
From the responses, I personally gather that Germin uses an XML structure but does not use a standard XML parser.
Even the order in which something is stored in the GPX can play a role.
So I think that Garmin not only expects strict specifications, but also sets its own rules.

[jfheath]

The Garmin format does allow for different manufacturers to create their own tags.

These (as I understand, which is not very well) are enclosed between <extensions> </extensions> tags.

I also thought that providing that the structure is correct (ie opening and closing tags, or <selfclosing tags /> ) that any software should be able to cope - if it comes across a tag that it doesn't recognise, then it simply ignores everything up to the matching closing tag.

Usually Basecamp is excellent at cleaning up badly formed gpx files. But you are right - it cannot handle that file exported from the Tread App.

I wonder if MyRouteApp ....Yes, MyRouteApp Imports it without any fuss. Route calculated, all Vias present and correct.

How odd.