This object is in archive!
Make navigation Store Permanently setting sticky
Declined
Every time navigation is performed the Store Permanently setting is cleared. And unfortunately because the screen is quite high you have to scroll down to see this setting, and be reminded of the fact. I'd like to suggest making this setting "sticky" so the previous preference becomes the default next time.
I like this idea 
Hi Andrew, a nice proposal, and probably easy to implement. So my + Vote !
Hi Andrew, a nice proposal, and probably easy to implement. So my + Vote !
Hi,
this feature is disabled by intent to prevent filling of database folder with unwanted data. It's based on my own experience where I found permanent storing of computed track as rare option and in most cases, I forget to disable it ( so database was full of unwanted tracks ).
Mainly on devices with smaller display, where as Andrew wrote, "you have to scroll down to see this setting", this option may be risky and may slow down work with Locus ( storing generated track and later deleting of unwanted tracks ). So sorry, idea declined.
Hi,
this feature is disabled by intent to prevent filling of database folder with unwanted data. It's based on my own experience where I found permanent storing of computed track as rare option and in most cases, I forget to disable it ( so database was full of unwanted tracks ).
Mainly on devices with smaller display, where as Andrew wrote, "you have to scroll down to see this setting", this option may be risky and may slow down work with Locus ( storing generated track and later deleting of unwanted tracks ). So sorry, idea declined.
I thought was asked for fastest method by creating different trajects to a finish point, then compare (by statistics distance, elevation) and select a favourite path to cycle.
Or sticky during an actual Locus session only ? Restart Locus ->standard set: Disabled. Lets hear Andrew.
I thought was asked for fastest method by creating different trajects to a finish point, then compare (by statistics distance, elevation) and select a favourite path to cycle.
Or sticky during an actual Locus session only ? Restart Locus ->standard set: Disabled. Lets hear Andrew.
Too true Willy. That is the way I use the Navigation To function.
Too true Willy. That is the way I use the Navigation To function.
After an interesting comment by Michael Bechtold in this related topic, maybe here is a simple but powerful way to improve many issues regards recently used points/ recently used tracks:-
How about having two special folders, "temporary points" and "temporary tracks". The points and tracks are purged after a user-settable number of days. #days defaults to 1. Personally I would set to 10. All recent points used by Navigate To go into the Temporary Points folder. All recent tracks created by Navigate To go into the Temporary Tracks folder. This solves @menion concern "filling of database folder with unwanted data". The Store Permanently setting can become sticky. Temporary points and tracks are handled consistently with others; can be renamed to more useful names if offline address data is not available; can be moved to other folders to save. Win-Win situation?
After an interesting comment by Michael Bechtold in this related topic, maybe here is a simple but powerful way to improve many issues regards recently used points/ recently used tracks:-
How about having two special folders, "temporary points" and "temporary tracks". The points and tracks are purged after a user-settable number of days. #days defaults to 1. Personally I would set to 10. All recent points used by Navigate To go into the Temporary Points folder. All recent tracks created by Navigate To go into the Temporary Tracks folder. This solves @menion concern "filling of database folder with unwanted data". The Store Permanently setting can become sticky. Temporary points and tracks are handled consistently with others; can be renamed to more useful names if offline address data is not available; can be moved to other folders to save. Win-Win situation?
Good day Andrew,
I'm sorry, but for me this still looks like "one (maybe two) man show".
Problem I see here, is that you do not want to use "Add new route" instead, which is made for such planning. Unclear answer for me is still "why"? I guess that it's because inability to modify track after planning is done. Well it's same in case of "Navigate to". Anyway solution here should be to load saved track to "Add new route" planning mode to allow modifications like during planning, right?
Good day Andrew,
I'm sorry, but for me this still looks like "one (maybe two) man show".
Problem I see here, is that you do not want to use "Add new route" instead, which is made for such planning. Unclear answer for me is still "why"? I guess that it's because inability to modify track after planning is done. Well it's same in case of "Navigate to". Anyway solution here should be to load saved track to "Add new route" planning mode to allow modifications like during planning, right?
Hi Menion
>I guess that it's because inability to modify track after planning is done
yes
>Anyway solution here should be to load saved track to "Add new route"
planning mode to
>allow modifications like during planning, right?
The main issue I see is the Navigate To & BRouter Direct methods allow points to be reused quickly with different profiles. Points can be moved and new tracks quickly computed. BRouter Direct is the fastest in this regard - just click the BRouter button & select different profile - new track auto-detected & map updated - very nice. With the Add New Route method you more-or-less start from scratch if the compute engine goes along a route you would subsequently modify.
Hi Menion
>I guess that it's because inability to modify track after planning is done
yes
>Anyway solution here should be to load saved track to "Add new route"
planning mode to
>allow modifications like during planning, right?
The main issue I see is the Navigate To & BRouter Direct methods allow points to be reused quickly with different profiles. Points can be moved and new tracks quickly computed. BRouter Direct is the fastest in this regard - just click the BRouter button & select different profile - new track auto-detected & map updated - very nice. With the Add New Route method you more-or-less start from scratch if the compute engine goes along a route you would subsequently modify.
I think you don't need to start from scratch. When BRouter computes route between two points and I don't like result, it's simply to change routing profile and simply tap/move with point little bit, which trigger recompute of this segment. Same may be done for any point in the middle of planned route.
Because I may really simply change and modify currently planning route, I still see no benefit in using BRouter over start/stop points or by navigate to. Only not yet supported feature are nogo areas, agree it may be useful in some cases.
I think you don't need to start from scratch. When BRouter computes route between two points and I don't like result, it's simply to change routing profile and simply tap/move with point little bit, which trigger recompute of this segment. Same may be done for any point in the middle of planned route.
Because I may really simply change and modify currently planning route, I still see no benefit in using BRouter over start/stop points or by navigate to. Only not yet supported feature are nogo areas, agree it may be useful in some cases.
I think we should agree each of the 3 methods have their own unique advantages.
>When BRouter computes route between two points and I don't like result,
>it's simply to change routing profile and simply tap/move with point little bit
In reality it's not that simple. In an unfamiliar country I generally have a single start and finish point for each days (say 100km) track. You let each profile decide the route (of course). You can't see the detail of the chosen roads until after you save then zoom/ pan in very great detail; also checking the elevation profile. By then it's too late to recompute. Only with the Direct BRouter method is it then easy to change profiles, alter via points, to experiment with routing options.
Another thought - remove the Store Permanently checkbox and dropdown folder selection all together - they are no longer necessary with this topic if all tracks are automatically saved for temporary period of time. Simplify the screen, maybe even remove the Show Less/More button because only one setting is hidden.
I think we should agree each of the 3 methods have their own unique advantages.
>When BRouter computes route between two points and I don't like result,
>it's simply to change routing profile and simply tap/move with point little bit
In reality it's not that simple. In an unfamiliar country I generally have a single start and finish point for each days (say 100km) track. You let each profile decide the route (of course). You can't see the detail of the chosen roads until after you save then zoom/ pan in very great detail; also checking the elevation profile. By then it's too late to recompute. Only with the Direct BRouter method is it then easy to change profiles, alter via points, to experiment with routing options.
Another thought - remove the Store Permanently checkbox and dropdown folder selection all together - they are no longer necessary with this topic if all tracks are automatically saved for temporary period of time. Simplify the screen, maybe even remove the Show Less/More button because only one setting is hidden.
Replies have been locked on this page!