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

[0709]

@proofresistant
Very interesting new information.
XML Notepad does not show errors as there are none.
This GPX file is valid and imports into Basecamp.

Why does it work?
Look at the GPX header.
creator="Tread 2"
And the new xml namespace
xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v2
And new v2 schema
http://www.garmin.com/xmlschemas/TripExtensions/v2 http://www.garmin.com/xmlschemas/TripExtensionsv2.xsd

[FrankB]

FYI:
Mapsource will read the GPX that BaseCamp doesn't. Also TripManager has no problems.

[0709]

@FrankB

Mapsource? Yes, sure I still know that program too of course.
Mapsource is strict when it comes to the gpx core, but does not read the extensions.
As so ShapingPoint did not exist at the time. This came later in the trp extension.
Color was also not available. This is now offered in the gpxx extension.
The trkpt “nesting” between the rtept is also offered in the gpxx extension.
Adding the already precalculated TBT by Basecamp however is not offered.
The receiver must so recalculate to add the TBT and complete that task again.
(This means that the result may deviate unexpectedly).

The gpx 1.1 core. The topografix standard
Topografix requires a very strict order of all the “point” gpx elements.
These gpx elements are so available in the wpt, rtept, and trkpt.
Mapsource and Basecamp apply this very strict, while other GPS apps are more tolerant.
A gpx file with elements in the false order can be optimized by import it into for example the more tolerant gpx editor (freeware).
After re-export, the elements will be placed in the correct order. Of course, the GPX editor does not resolve all deviations.
The GPX editor even does contains some minor bugs. But the developer is unavailable.

- A non Garmin topic.

All the GPX point elements are available in as well WPT, RTEPT, and TRKPT.
In the TRKPT, this excellent opportunity has still been unused for years.
Anyway Cruiser Android and Desktop (Java) uses it in a gpx navigation track.

Find a short gpx demo file in the attachement.
This gpx file contains 4 gpx wpt plus a gpx track (navigation track)


Follow the precalculated track 100% accurately by the attached TBT, inclusive via and shaping trkpt support. Using the via and shaping trkpt, flexibly recalculate any track section later, even using a different routing profile if you wish. The important basic functionality is done without use of any gpx extension. Only the less important “trinkets” as track color, track segment color, and wpt color are to be placed in a gpx extension. A proprietary app extension is not used. Just as in nature the cuckoo uses another bird's nest, an existing “nest” in the gpx header is used. The “eggs” are placed in it. Of course, there is no schema. Organic maps now also uses this too. As well the trk and trkseg color plus width, and the wpt (origin b/w icon) color, are read and shown by the OsmAnd app.

* A track section is located between two consecutive via or shaping track points.
Track section is used because track segment (trkseg) meaning is different.

Translated with DeepL.com (free version)

[proofresistant]

@proofresistant
Very interesting new information.

The information is getting even better, or rather, there are even more surprises.

Firstly, I have to admit that the previous findings describe the symptoms more than they identify the real cause
Yes, I had noticed that AdventurousLevel was causing problems, but I hadn't actually identified the real reason and hadn't questioned it further.
@0709 Thanks again for your perspective

But now to my new findings.

• BaseCamp can also read the new Adventurous values but cannot interpret them and replaces them with default values.

• The zumo XT2 can only partially write Adventurous values to a compliant GPX file, which can at least be read by BC.
  CalculationMode = Adventurous is still present in the GPX, but the
  AdventurousLevel is not exported.

• The Tread app can write Adventurous values completely to a GPX file.
  The written file is not TopoGrafix-compliant and therefore cannot be read by BC.

• The Tread 2 can write Adventurous values completely to a compliant GPX file, which can at least be read by BC.

PS
One piece of information that is important to know, at least for me right now:
The GPX standard is from topografix https://www.topografix.com/ and is not owned by Garmin

[0709]

@proofresistant
It had been years since I had looked at a Garmin application in such depth. Due to its complexity and lack of support, I abandoned Garmin more than 10 years ago and it appears that nothing has changed in this regard. My last visit to the shop, when I was still unsure about my choice see pdf.
The image in the PDF is misleading for the Garmin bike GPS. You have to photograph this outside in full sunlight, of course. But with those expensive devices, you couldn't just walk outside. And the salesperson lost interest when I showed him the comparison.
Despite the phone hardware disadvantages, I am happy with my favorite app. And the developer is definitely available to answer questions. Worth its weight in gold! (€10/year)