Track name when following route

Guy Evans shared this idea 14 days ago
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

Comments (9)

photo
1

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?

photo
1

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).

photo
1

Oki, and where you see (want to see) mentioned "Following X"? Sorry, I still do not perfectly understand your idea.

photo
1

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...

photo
1

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]"

photo
1

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.

photo
1

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.

/ea3fed39fbe2682605f0a5a0f8eb1c3d

photo
1

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} ...

photo
1

Guy - "All these tracks will have the same name" - not if the date &/or time are incorporated into the file name?

Isn't

  • 2021-04-24 08:26:50 Oxon
  • 2021-04-17 08:39:28 Oxon
  • 2021-04-10 09:03:47 Oxon

better than:

  • Following Oxon 20 challenge walk
  • Following Oxon 20 challenge walk
  • Following Oxon 20 challenge walk?

photo
1

Sorry you are right the name will be different due to the timestamp. However, the timestamp doesn't make it possible to differentiate the walk that I did. So in the example you give above, "Oxon" is not the name of a place but the name of the challenge walk. The different challenge walks will have different names.

An easier example to think about is if I walk up Snowdon (highest mountain in Wales). There are multiple routes that can be taken - all from the same carpark. Tracks named

  • Snowdon via Miners Track, 2021-04-24 09:00
  • Snowdon Horseshoe, 2021-04-17 09:00
  • Snowdon via Y Gribin Ridge, 2021-04-15 09:00

are much more meaningful then

  • Llanberis, 2021-04-24 09:00
  • Llanberis, 2021-04-17 09:00
  • Llanberis, 2021-04-15 09:00

where Llanberis is the name of the nearest village. Indeed, in this case the automatic naming is particularly confusing as Llanberis is a couple of miles away from where you'd start these walks and is the name of yet another trial up Snowdon. The Snowdon Horseshoe (classic grade 1 scramble) is a very different walk than the Llanberis path!


Or similarly in the Lake district, I might choose to do a little walk from Ambleside across to Braystones (a fell/mountain), or head in completely the opposite direction to Lloughrigg Fell (a fell/mountain) or do the classic Fairfield Horseshoe. Track names like

  • Fairfield Horseshoe, 2021-04-24 09:00
  • Braystones from Ambleside, 2021-04-17 09:00
  • Lloughrigg Fell from Ambleside, 2021-04-15 09:00

are much more meaningful then


  • Ambleside, 2021-04-24 09:00
  • Ambleside 2021-04-17 09:00
  • Ambleside 2021-04-15 09:00


Note I am not against having the timestamp in the track name and can see it might be potentially useful. However, the route name has a lot more useful information then the name of the nearest village/town/city where I started walking.

photo
1

I'm pretty confused by the down votes for this idea. If you just want your tracks named as they are just leave the "track name format" as it is now - {t}.

This is just about adding additional functionality so that people who want to have a different naming convention can. (It also means that Locus Map will be able to optionally support the naming convention that ViewRanger uses so is not completely whacky!).

One of the big strengths of Locus Map verse other apps is the level of configurability it offers instead of the "one size fits all" mentality.

photo
1

Im puzzled by downvotes as well, were not asking for the default to change, or make it awkward for other users

The template is great, I would also just like {route} option as well....

This wont affect anyone that doesnt want to use it!

photo
photo
2

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

photo
1

Thats excellent

This is really pedantic, bt is there any way to to have text Like "Following", Or "Track following" or similar to only show when nav_name is not null

Otherwise you might get the word following when you arent actually following a route.

photo
1

Menion,

Thank you! You've made my day. Just to double check, that will also be populated when guiding along a route as well?

photo
2

@Alistair Parsons, this is more complicated. Suggest to not use pattern where missing route name cause a problem :).

@Guy Evans, to be honest, I did not tested it anyway it should work for navigation as well as for guidance along the line.

photo
1

No problem, Thanks for adding the feature.

photo
1

Just to confirm that this feature (including {nav_name}) is working really well.

Many, many thanks Menion. Your responsiveness to user requests is greatly appreciated.

photo
1

Perfect!

I've received another nice idea, so list of supported tags (since 4.2 version) is here: https://help.locusmap.eu/topic/24560-název-zaznamenané-trasy-v-lm4#comment-97471 . We will have to add this list to the app or on the web soon ...

Menion

photo