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...
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
POPULAR TOPICS
MY GROUPS