Importing GPX Route: Locus Map removes most route points (rtept) after import

[sonymaster]

Hello,

I have a question about importing GPX routes.
I import a route (not a track) that contains many <rtept> elements. After the import, Locus Map removes most of these route points.
For example, if the GPX route contains about 30 route points, only about 10 points remain as via points when I open the route in the route planner for editing.
Is there a way to import the route without losing any route points, so that a later route recalculation uses all original points?

If many route points are missing, the recalculated route is often very different from the original one.

Here is a simplified example of the GPX structure:

Code Select Expand

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" xmlns="http://www.topografix.com/GPX/1/1">
    <rte>
        <name>Locus Route</name>
        <rtept lat="49.88311" lon="8.594734"></rtept>
        <rtept lat="49.883197" lon="8.605491"></rtept>
        <rtept lat="49.870131" lon="8.607834"></rtept>
        ...
    </rte>
</gpx>

Am I missing a setting, or is this the expected behavior?

Thank you for your help.

[0709]

The problem is that Locus makes virtually no distinction between GPX RTE and GPX TRK.
Locus Map does not (never did) strictly follow the GPX standard as intended.
Garmin, Kurviger Web, Cruiser GPS, on the other hand, adhere consistently to the GPX standard.
In Locus Classic, you might +/- get a result that's more or less what you want.
Since the "spirit" of the GPX standard isn't implemented, it's a matter of luck.

[Menion]

Hi sonymaster,
answer from 0709 is only partially correct. At least, it is not just about "luck".

We were facing problems with routes created from huge amount of rtept points. Such routes were not usable and we often forwarded users to, for example, GPSVisualizer, where exists the option to convert such route to track.

A few years ago, we decided to automatically use rtept points as trackpoints in case, they do not contain a navigation instruction (it may be defined in many ways, over "sym", as a custom Locus extension, in "cmt" etc). Since then, you are first who has now the opposite problem.

Probably most easy solution if you really want to preserve these points is to add to every of them <sym>pass_place</sym> tag.

[0709]

Importing the gpx rtept as trkpt is simply wrong. So you'll definitely need some luck.
The only correct and 100% solid solution is to support the gpx rtept properly.
Garmin and some gps apps handle the gpx rtept without any problem. Locus does not.