Improve copied-reversed track creation

Andrew Heard shared this idea 22 days ago
Completed

When I create a copy of a track with Reverse+Generate Command options as below

61e3a924f48d87eebfc2172cf502491e

the new track has a navigation waypoint at every minor change of direction of the road, not just at road intersections, as below

97214873d43cb9a318926db1867362d83efb5aa752301c9bd35e9d5cb8becefe

Locus is using its old internal simplistic algorithm for calculating navigation waypoints based on road geometry. Once I commence navigation I can tap the Recalculate button to eliminate these fake waypoints but this leads to other problems because the recalculation is not based on the original compute source (in my case BRouter) or the original waypoints or via points. For anything except very simple copies where navigation is not required, the new track is of little use, and it is generally quicker just to create the new track from scratch using the Route Planner.

So, when creating a reversed copy of a track which was itself created with the Route Planner, could the original track section profiles, the original waypoints, and original via points, all be preserved and the new track calculated in a method similar to if the user had used the Route Planner?

Comments (4)

photo
1

Good day Andrew,

when you have track generated by BRouter, why you then check the option "Generate commands"? What if you leave it unchecked?

photo
1

Hi Menion,

I assumed if I uncheck the option "Generate commands" then no commands will be generated for the new copied track - clearly my misunderstanding because when I create a copy with your suggestion the commands are correct! But isn't that confusing in itself - new commands have been generated - for example original track left turns are now (correctly) right turns etc. even though I have unchecked "Generate commands"?

photo
1

Understand. Probably wrong wording :). From a technical point of view, new commands are not generated, they are just reversed (except roundabouts where is an unknown total number of exits so the reverse is not possible). We will try to update this option little bit. Anyway, enjoy new discovery ;).

photo
1

OK, thanks, I understand as well. From a users point of view their seems to be 3 possibilities when reversing a track: retain existing waypoints (although not useful), remove existing waypoints, generate new/ reverse existing waypoints; which is not conveyed well through a simple checkbox. I only very occasionally use this copy/reverse track, but when I use it again in a years time I will have probably forgotten the subtlety of this discussion.

photo