New Topic

Locus Map - help desk Topic Question Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Comments 14

Subscribers 4

Votes 1

Importing routes without arrows

Ingo Rau shared this question ago

Answered

I exported a track (created with edit, not recorded) as GPX with "Track as route" checked. Now when I re-import it, the track is littered with red arrows at every trackpoint.

Is there a way to avoid that? The original track didn't have that and I don't see the use for them. I would've expected the import to look just like before the export.

The same question

Best Answer

Menion ●

I personally do not like separating into tracks / routes. Nothing like this exists in Czech and we are really fine :).

"?" - nobody reads extra texts

I'll do something with this - probably "advanced options" with "?", hidden by default. Thanks for discussion

Replies (8)

Bucky Kid ●

You must export as track

For track cleanup vote here: http://help.locusmap.eu/topic/cleanup-of-imported-routes-cleanup-of-saved-tracks

URL

Michal Stupka ●

if you want to have track without routepoints, keep the original track besides the exported route so that there's no need to re-import it. Importing a "route" makes the routepoints visible as the annoying arrows. And as Bucky Kid has written and I thank him this way, vote for the http://help.locusmap.eu/topic/cleanup-of-imported-routes-cleanup-of-saved-tracks

URL

0709 ●

For immediate help to correct. Use pc program Javawa RTW tool. Export route as track.

URL

0709 ●

Cleaning In Locus. Actually just tested....pse someone for a double check and confirmation.

Start condition:

Source file: A gpx route(rte-tags) file (mixed with Navpoints).

Import into a TRACKS FOLDER. In POINTS FOLDER select "Merge with track." Tip: Select: Empty selected folders.

Export the now visible route(rte) as a new track file (trk tags !). Hide the route.

Import the previous track (trk) and split up into a TRACKS FOLDER and POINTS FOLDER. No Merge points with track ! In POINTS FOLDER delete the red arrows rte points and the Navpoints. Export result as cleaned track (trk). Red arrows gone, Navpoints gone.

URL

Michal Stupka ●

Hi Willy, thanks for your contribution. Looks like this workaround does what is expected. Anyway, let me re-write it into more plain English:

1) export the arrow-littered route as a track (uncheck the RTE option)

2) import the track back - importing dialog will indicate importing points as well - select NOT to merge points with the track

3) delete the arrow points from the folder where they've imported in

URL

Ingo Rau ●

Thx for all your advice. Sure that is a working workaround, but I still voted for that idea, as I think the red arrow should at least be optional. A non-recorded track is a route (no timestamps), and when I export it for backup (as route) and reimport it, I expect it to look the same.

May I also point you to one of my ideas, that would also help here:

http://help.locusmap.eu/topic/is-there-a-list-of-waypoints-in-a-track

It's in status planned, but for a while now, so perhaps Menion needs some reminding ;)

URL

Michal Stupka ●

Hi Ingo, as I had written, I think it's best to export without the TRK-RTE change when we do it as a backup.

As for your waypoints folder idea, I'm sure Menion knows that and will read this as one of the assigned agents.

URL

Ingo Rau ●

Yes, I realized that now, too. Usually I do, but in one case I forgot because I only recorded for someone else and deleted it after export. Now the other one imported it in Locus (which I recommended to him) and was like "What the heck is that? Why does that happen? That's so stupid!"

And that's why I'm no fan of that workaround. We're all experts here and can find a way around. But unexperienced users are likely to be put off of Locus by things like this. I mean, it's the obvious thing to do: Create a route, export it as route, import it again when needed. Bamm! Looked great before, now a mess. There's nothing there to warn the user. Perhaps at least a "?" should be added to the "Export as route" option. I'll write that in the idea...

URL

Michal Stupka ●

I fully understand. Thanks for your comment as we are really struggling to make Locus Map more "inexperienced-user-friendly" and, on the other side, keep it as advanced as it is. Quite a hell of a job :)

URL

Menion ●

Hi guys,

to be true, I see biggest problem in "Track as route" export settings. Is anyone using it at all? Because to be true, I now do not see any usage in it. Also it's translation is not perfect. It should be "Export track not as common list of trackpoints <trkpt>, but as a list of routepoints <rtept>.

URL

Ingo Rau ●

Of course that's too long, but probably the problem is really the expectation that you have when you read "Track as route".

As I said above, my (laymen's) interpretation is that a "real" track has timestamps, a route just points. So if you create a "track" beforehand, you don't have timestamps, therefore it's a route and you can export it as such. When reimporting, you don't expect it to look so different.

So I would be fine if the option is removed. However I usually don't like features being removed, so why don't you put your long explanation above on a "?" explanation button. Then nobody can say they haven't been warned ;)

URL

Menion ●

I personally do not like separating into tracks / routes. Nothing like this exists in Czech and we are really fine :).

"?" - nobody reads extra texts

I'll do something with this - probably "advanced options" with "?", hidden by default. Thanks for discussion

URL

Ingo Rau ●

I didn't see it mentioned in the Changelog, but obviously in 3.12.0 you did add a "?" and hid this and other options with "Show more".

Although that's not what I initially was asking for, I think that's a reasonable solution and I'm fine with closing this topic.

Thanx as always for quick implementation.

URL

Menion ●

Hello,

understand. I also do not think that change in Locus is a real solution. Problem here is that there is no solution because what Locus do is just .... correct. So I hope that change in Locus improve usability and prevent similar problems in future.

URL