Bug when recalculating a route from a GPX file with navigation prompts enabled

40° shared this problem 22 days ago
Not a Problem

Hello,

I've encountered an issue when working with routes imported from GPX files.
If I import such a route and start navigation immediately, everything works correctly: all navigation prompts and voice commands are present.

However, if I recalculate the same route in the route planner with the "Include navigation prompts" option enabled, the opposite happens — the navigation commands either disappear completely or only very few remain. As a result, turn-by-turn guidance along the route becomes useless.

Steps to reproduce:

  1. Import a GPX file with a route.
  2. Start navigation along the imported route — prompts work as expected.
  3. Open the same route in the route planner.
  4. Enable the "Include navigation prompts" option and slightly move the route's final point to trigger a recalculation.
  5. Start navigation along the recalculated route — prompts are missing or very few.

I am attaching a test GPX file.

video demonstrating the problem:
https://drive.google.com/file/d/1efNEcDtAMDRyMdh6cyJKqxmf9Tx69MrA/view?usp=drivesdk

Please look into this issue. Thank you in advance.

Files: test.gpx

Replies (1)

photo
1

Hi,

the GPX you provided doesn't contain navigation prompts. Locus Map generates them upon navigation start from the route shape. When you open such a route in the route planner, it is automatically divided into a few segments (two in this particular case), each of which has no routing profile assigned - they are marked as manual segments. If you move the final point, the particular segment is recalculated with the selected routing profile and navigation prompts are added in the proper places. The other segment is left untouched because the manual segments are by default not recalculated.

And here is a possible bug - when I deactivate the option "keep manual segments" in the planner settings, I expect that both segments will be rerouted when I move the final point. But the first is untouched despite this. I'll ask the devs about it.

This comment is in trash! Restore
photo
1

I understand your answer. All I had to do was additionally perform a "count everything". I know that now. Recalculating only the current segment when moving the point is likely to be correct. There is no need to change anything.

This comment is in trash! Restore
photo
Leave a Comment
 
Attach a file
You can't vote. Please authorize!