This object is in archive!
Track name when following route
Completed
The suggestion is for the track name to default to "Following <route name>" when navigating/guiding along a route.
The current default of using the timestamp is not helpful when reviewing old tracks (and is actually redundant since the track itself includes timestamp data).
For further motivation my last few tracks in LocusMap is:-
- 2021-04-24 08:26:50
- 2021-04-17 08:39:28
- 2021-04-10 09:03:47
I'm an ex-ViweRanger user. My last few tracks in ViewRanger are:
- Following Oxon 20 challenge walk
- Following Ramble 13: Fifeld and Gays Lane
- Following Peak District Challenge
I like this idea 
Hello,
where you please see and use these default values? They should be generated in case of track recording or also on any other place?
Hello,
where you please see and use these default values? They should be generated in case of track recording or also on any other place?
Yes, just in track recording.
I guess in "Recording Profile" there could be a "Track name format when following route" with a {r} parameter for the route name (or something along those lines).
Yes, just in track recording.
I guess in "Recording Profile" there could be a "Track name format when following route" with a {r} parameter for the route name (or something along those lines).
Oki, and where you see (want to see) mentioned "Following X"? Sorry, I still do not perfectly understand your idea.
Oki, and where you see (want to see) mentioned "Following X"? Sorry, I still do not perfectly understand your idea.
As the track name. So when following a route the track name will be "Following X" and not something like "2021-04-24 08:26:50".
In particular, when the track is saved then it will use the name "Following X". Thus when I'm reviewing my previous tracks in the "Track & Routes Manager" I get useful names and not just timestamps.
I hope that's clear - please let me know if it would be useful to include screenshots...
As the track name. So when following a route the track name will be "Following X" and not something like "2021-04-24 08:26:50".
In particular, when the track is saved then it will use the name "Following X". Thus when I'm reviewing my previous tracks in the "Track & Routes Manager" I get useful names and not just timestamps.
I hope that's clear - please let me know if it would be useful to include screenshots...
This is something I miss from viewranger as well
Basically logic is if track recording is started while If Guidance/Navigation" is chosen from a track option
the default track name should prefix "following [NameOfTrack]"
This is something I miss from viewranger as well
Basically logic is if track recording is started while If Guidance/Navigation" is chosen from a track option
the default track name should prefix "following [NameOfTrack]"
I understand that. He does not want to display the name during navigation.
It creates a route with the route planner.
Saves this with the name XYZ
Now he naves the XYZ and makes a recording in parallel.
When saving, he wants to automatically change the name when saving XYZ.
I would write the date behind Xyz.
I understand that. He does not want to display the name during navigation.
It creates a route with the route planner.
Saves this with the name XYZ
Now he naves the XYZ and makes a recording in parallel.
When saving, he wants to automatically change the name when saving XYZ.
I would write the date behind Xyz.
Hi guys,
I'm not a fan of this idea. It is not easy to understand and does not give reliable results (depend on the fact, that you have active navigation with a correctly named route).
In new version 4.1 that is just publishing is an option to customize the name of the autogenerated recording. In this version is added option {city} to generate better names. So you may end with these results. Give it a try, it may be better ;). Btw. name is generated from the offline address search so LoMaps of the area is needed.
Hi guys,
I'm not a fan of this idea. It is not easy to understand and does not give reliable results (depend on the fact, that you have active navigation with a correctly named route).
In new version 4.1 that is just publishing is an option to customize the name of the autogenerated recording. In this version is added option {city} to generate better names. So you may end with these results. Give it a try, it may be better ;). Btw. name is generated from the offline address search so LoMaps of the area is needed.
Thanks. I'll be interested to try this when 4.1 comes out.
This sounds like a definite improvement but does not completely resolve my original issue. I do lots of walks from the same place - either my home or a few favourite car parks close to home. All these tracks will have the same name which means when looking through my list of tracks they will still be impossible to differentiate.
I only ever use Locus Map when following a route and always record that route so I have a record of it. If the route name is not sensible then that's my problem. Further, Locus Map itself behaves very differently when following a route compared to when not doing so, so having a different default track name in this case doesn't seem like a problem at all.
Perhaps, if as well as {city} you also added {route} (but did not change the default track name format template) then that would be the best of both worlds. (If following a route {route} would be the route name otherwise empty). For people who want the route name in the track they can add {route} to the track name format. Other people can just ignore it. Going further, you could even add {description} which is the {route} if following a route and otherwise is {city} ...
Thanks. I'll be interested to try this when 4.1 comes out.
This sounds like a definite improvement but does not completely resolve my original issue. I do lots of walks from the same place - either my home or a few favourite car parks close to home. All these tracks will have the same name which means when looking through my list of tracks they will still be impossible to differentiate.
I only ever use Locus Map when following a route and always record that route so I have a record of it. If the route name is not sensible then that's my problem. Further, Locus Map itself behaves very differently when following a route compared to when not doing so, so having a different default track name in this case doesn't seem like a problem at all.
Perhaps, if as well as {city} you also added {route} (but did not change the default track name format template) then that would be the best of both worlds. (If following a route {route} would be the route name otherwise empty). For people who want the route name in the track they can add {route} to the track name format. Other people can just ignore it. Going further, you could even add {description} which is the {route} if following a route and otherwise is {city} ...
Hi guys,
Oki, let's try it in the next Locus Map version. First experiment ;).
Because there is this new system for the setup of the custom name of the recorded track, let's try a new key {nav_name}, that will be filled by the currently active (or empty) navigation route name.
Menion
Hi guys,
Oki, let's try it in the next Locus Map version. First experiment ;).
Because there is this new system for the setup of the custom name of the recorded track, let's try a new key {nav_name}, that will be filled by the currently active (or empty) navigation route name.
Menion
Replies have been locked on this page!