How to navigate a track?
-
Hi everyone, this discussion is drifting in an unintended direction. May the header is misleading? My first post was simply meant to describe the situation, and ended with a simple question: why.
Of course, this was implied with the hope, that there would be a future development that treats imports and exports equally.By the way: I am very familiar with all the features of MRA Routeplanner, MRA Navigation and GPX standard.
The background to my question is this: at many prominent events, the organizers provide a GPX file containing one or more tracks. This ensures that all participants get the same result on their different navigation devices (since routes always turn out differently!).
The GPX file often includes additional necessary locations - which aren’t necessarily part of the track - but may also be situated somewhat off to the path. For example: checkpoints, bivouacs, gas- or water sources, etc.These were established when the GPX format was created in the last century by the company TopoGrafix - and exists in the same way until today.
If you look into a GPX file that contains such points, they stand alone and are not related to a route or track. They are called waypoints and are labeled as <wpt>.
In opposit: if a point is needed to calculate a route, then this point is called routepoint and labeled <rtept>.
If a point is needed to draw a track, this point is called trackpoint and labeled <trkpt>.Yes, we may wonder why they were called waypoints if they had nothing to do with the route nor the track.
Unfortunately, many navigation devices still cause confusion today because they use the terms inconsistently.In MyRouteApp, these waypoints <wpt> are called Points Of Interest (POI). And yes, MyRouteApp contains an extensive library of such POIs that can be used in route planning. You can even enter manually single custom POIs, also import lists of POIs.
So MyRouteApp can handle this in a variety of ways.
This really leaves the question open - why the import routine for GPX files can’t handle this and display them together with the imported route or track.
Quite a few other apps can do this.I know that I can import the contents of a GPX file into MyRouteApp in several steps and then merge them. But that’s an unnecessary amount of work (and prone to errors), for example, on the eve of a rally when you’re under time pressure.
Not sure about, but it looks like, all the technical basics are there in MyRouteApp - only the idea or the willing to use it for further development is missing...
-
perfect how you write it. i have the same question but maybe i was taking over.
i also realy want to know if wpt in a track file will be taken by MRA planner and MRA Next. it would be a great option. other options that are told here are in my eyes to difficult to do. beter is to import all information form gpx file and then ask what you want to import. only trackpoints or also wpt point with info (poi).
-
perfect how you write it. i have the same question but maybe i was taking over.
i also realy want to know if wpt in a track file will be taken by MRA planner and MRA Next. it would be a great option. other options that are told here are in my eyes to difficult to do. beter is to import all information form gpx file and then ask what you want to import. only trackpoints or also wpt point with info (poi).
@Bouke-Ent said in How to navigate a track?:
wpt in a track file
wpts are not part of a track file; that's a common misunderstanding. Unlike VIA points, that are part of a route, there is no link between wpts and tracks in any way even if they are part of the same GPX file.
-
@Bouke-Ent said in How to navigate a track?:
wpt in a track file
wpts are not part of a track file; that's a common misunderstanding. Unlike VIA points, that are part of a route, there is no link between wpts and tracks in any way even if they are part of the same GPX file.
@Martin-Wilcke said in How to navigate a track?:
@Bouke-Ent said in How to navigate a track?:
wpt in a track file
wpts are not part of a track file; that's a common misunderstanding. Unlike VIA points, that are part of a route, there is no link between wpts and tracks in any way even if they are part of the same GPX file.
wpt in a gpx means a single not to route or track point. when export a track and poi file in MRA a poi gets wpt in gpx file.
TopoGrafix
- stand alone and are not related to a route or track. They are called waypoints and are labeled as <wpt>.
- a point is needed to calculate a route, then this point is called routepoint and labeled <rtept>.
- trackpoint and labeled <trkpt>.
-
@Martin-Wilcke said in How to navigate a track?:
@Bouke-Ent said in How to navigate a track?:
wpt in a track file
wpts are not part of a track file; that's a common misunderstanding. Unlike VIA points, that are part of a route, there is no link between wpts and tracks in any way even if they are part of the same GPX file.
wpt in a gpx means a single not to route or track point. when export a track and poi file in MRA a poi gets wpt in gpx file.
TopoGrafix
- stand alone and are not related to a route or track. They are called waypoints and are labeled as <wpt>.
- a point is needed to calculate a route, then this point is called routepoint and labeled <rtept>.
- trackpoint and labeled <trkpt>.
Yep, I know
-
That's the major difference between MyRouteApp and DMD:
MyRouteApp is very good in street routing; not sure if developer is willing to enhance it also for track operation in future. By the given solid foundation in on-road routing, it will be difficult to build on that with off-road routing (track navigation) on top. And: it looks like the interoperability with other apps isn't in focus.DMD is excellent in offroad routing (track navigation) and offers all stuff you can imagine could be important for it. No wonder about, it can inform you p.e. about distance to a <wpt> which is close to the track.
Nowadays, the developer is going to include also onroad routing (route planning). But this is just in the beginning and far away from MyRouteApp level!This discussion here shows, there are MyRouteApp users which are interested to get things like:
if there are <wpt> in a gpx file additionally - they should be handed as well. Of course they can be imported, but that's not enough. Because currently they can be "added" only to routes but not to tracks.Both user groups forces both developers, to enhance the underdeveloped part of the apps. Not sure how many time it will need for enhancement. But we are lucky: we can run both apps parallel on a Android device - feed by same gpx file. So, it's easy to switch between the apps just what is best for the situation
-
@Bouke-Ent said in How to navigate a track?:
wpt in a track file
wpts are not part of a track file; that's a common misunderstanding. Unlike VIA points, that are part of a route, there is no link between wpts and tracks in any way even if they are part of the same GPX file.
@Martin-Wilcke said in How to navigate a track?:
wpts are not part of a track file; that's a common misunderstanding.
Actually, that is the common misunderstanding.
Waypoints do not have to be on the track, but that does not mean they are not part of it. In navigation going back long before motorbikes were invented, a turn point was commonly defined by following a specified heading until a given waypoint (distinguishing feature usually off the track) was observed on a specified bearing. So yes, when importing a track, it is important to import any specified waypoints defined in the track file. Whether MRA uses them as part of its calculations is irrelevant. You must accept that if they were important enough to the creator of the track to be included in the file, then they are probably just as important to the user of the track.
-
@Martin-Wilcke said in How to navigate a track?:
wpts are not part of a track file; that's a common misunderstanding.
Actually, that is the common misunderstanding.
Waypoints do not have to be on the track, but that does not mean they are not part of it. In navigation going back long before motorbikes were invented, a turn point was commonly defined by following a specified heading until a given waypoint (distinguishing feature usually off the track) was observed on a specified bearing. So yes, when importing a track, it is important to import any specified waypoints defined in the track file. Whether MRA uses them as part of its calculations is irrelevant. You must accept that if they were important enough to the creator of the track to be included in the file, then they are probably just as important to the user of the track.
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.
-
I blieve, we have the same understanding, but may using other words to explain - or translation does it not in best sense.
MRA does it in it's own way and sepereates data in stricktly separated areas:
- Tracklogs - which sould collect only own logged travels (as tracks)
- Routes - which collects own or received routes and received tracks (here called Route-Tracks)
- POI - which collects Points of Interests (in gpx standard named as <wpt>
For the moment, I will not discuss this.
But I'm asking towards development: based on given build in MRA - if a gpx is going to be imported (which contains a route <rte> and <wpt>. Can we get a solution:
- to import in one hit the <rte> into the area "Routes" (as route) - and the <wpt> into the area "Routes" / Section "Point of Interest" / tab "Manage"?
- to Import in one hit the <trk> into area "Routes" (as Route-Track) - and the <wpt> into the area "Routes" / Section "Point of Interest" / tab "Manage"?
But yes, I see: this will change a paradigma in MRA, because until now Route-Tracks can't have Points of Interest.
And I consider: what if a gpx file does contain both <rte> and <trk> - and if there are also <wpt> in?
I believe we need 2 import actions: one for Route and another for Route-Track. Or it could be automated, to get both in one hit - because this is the case in current MRA build if there are 2 routes or 2 tracks in one gpx file to be imported (it creates that separated).
And I also consider: in this case, a gpx file does contain <rte> and <trk> and <wpt>. To which one sould be the imported <wpt> belong to? To the Route, to the Route-Track, or to both?
I prefer to both, because if to one of them it's not necessary to get the <wpt> - it's more easy to delete them (one by one), as to enter them (one by one) with search of position afterwards.Yes, other Apps can show more than one track in the same map; MRA doesn't. But I think, there is no need to change this in MRA also.
I can imagine, this would not be a big effort, but a "masterpiece" - which resolves the problems we are discussing here and makes many users happy. And brings MRA again a step vorward in relation to DMD
I know, many users are there, who will love it - but the "louder" ones are those with Carplay issues...Bay the way: DMD does also exactly was gpx standard is: showing groupwise content of a a gpx file. All routes <rte>, all tracks <trk>, all waypoints <wpt>. But they don't belong to each other; they are only in one file.
The only belongings are trackpoints <trkpt> which belongs to tracks <trk>.
And routepoints <rtept> which belongs to <rte>.
(see attached images)
Nothing is impossible ;-)
In past: GARMIN Zumo 210->GARMIN Zumo 395->GARMIN XT=> now: DMD T865-X + MyRoute-App, LocusMaps, OsmAnd.
In past: GARMIN MapSource ->GARMIN BaseCamp->Tyre->Kurviger->Calimoto=> now: MRA-Routplanner. -
I blieve, we have the same understanding, but may using other words to explain - or translation does it not in best sense.
MRA does it in it's own way and sepereates data in stricktly separated areas:
- Tracklogs - which sould collect only own logged travels (as tracks)
- Routes - which collects own or received routes and received tracks (here called Route-Tracks)
- POI - which collects Points of Interests (in gpx standard named as <wpt>
For the moment, I will not discuss this.
But I'm asking towards development: based on given build in MRA - if a gpx is going to be imported (which contains a route <rte> and <wpt>. Can we get a solution:
- to import in one hit the <rte> into the area "Routes" (as route) - and the <wpt> into the area "Routes" / Section "Point of Interest" / tab "Manage"?
- to Import in one hit the <trk> into area "Routes" (as Route-Track) - and the <wpt> into the area "Routes" / Section "Point of Interest" / tab "Manage"?
But yes, I see: this will change a paradigma in MRA, because until now Route-Tracks can't have Points of Interest.
And I consider: what if a gpx file does contain both <rte> and <trk> - and if there are also <wpt> in?
I believe we need 2 import actions: one for Route and another for Route-Track. Or it could be automated, to get both in one hit - because this is the case in current MRA build if there are 2 routes or 2 tracks in one gpx file to be imported (it creates that separated).
And I also consider: in this case, a gpx file does contain <rte> and <trk> and <wpt>. To which one sould be the imported <wpt> belong to? To the Route, to the Route-Track, or to both?
I prefer to both, because if to one of them it's not necessary to get the <wpt> - it's more easy to delete them (one by one), as to enter them (one by one) with search of position afterwards.Yes, other Apps can show more than one track in the same map; MRA doesn't. But I think, there is no need to change this in MRA also.
I can imagine, this would not be a big effort, but a "masterpiece" - which resolves the problems we are discussing here and makes many users happy. And brings MRA again a step vorward in relation to DMD
I know, many users are there, who will love it - but the "louder" ones are those with Carplay issues...Bay the way: DMD does also exactly was gpx standard is: showing groupwise content of a a gpx file. All routes <rte>, all tracks <trk>, all waypoints <wpt>. But they don't belong to each other; they are only in one file.
The only belongings are trackpoints <trkpt> which belongs to tracks <trk>.
And routepoints <rtept> which belongs to <rte>.
(see attached images)
I understand and agree with all the facts and details you pointed out.
Just one more question: I mentioned the TET S GPX file in the other thread, which contains 21 <trk> and 760 <wpt>.
What is your preferred solution here: creating 21 route-tracks and inserting 760 POIs in the "POI / manage" tab for each of the 21 route-tracks?
