@Paul-Smith-3
I'm talking about GPX, specifically its structure and semantics.
A GPX file (implementation) or GPX container (model) might have multiple tracks and waypoints. All these elements are at the same level; they are not nested or linked in any way. Whatever the creator's intention was, you can't tell from looking at a GPX which waypoint belongs to which track. If you want to do so, you need some clues, rules, guessing - whatever.
That's why some Apps (e.g., DMD) prefer to import a GPX as a bundle to keep the content cohesive.
MRA, however, takes a different approach: you have to import tracks and waypoints in individual steps into different RouteLab areas. In particular, you don't end up with waypoints appearing in a route-track's "manage" tab in the "POI" section - that's what this thread is about, and that's what @guzzist is asking for.
@Paul-Smith-3 said in How to navigate a track?:
So yes, when importing a track, it is important to import any specified waypoints defined in the track file.
While still talking about GPX: there is no "track file", and there never was.
