@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)
