Unexpected distortions of the route during its processing by the scheduler.
Solved
1. Create a simple route from two points so that there is one turn;
2. Save the route;
3. Export the route to a GPX file;
4. Delete the route;
5. Import the route from the GPX file by combining the points with the route;
6. Select "Route Recalculation";
7. Save the route by overwriting it;
8. Select "Recalculate route" again;
---> Attention, distortion: another auxiliary point appeared out of nowhere.
9. Save the route by overwriting it;
10. Select "Route Recalculation";
11. Cancel the "Route Recalculation".;
12. Select "Route Recalculation" - "Continue";
---> Attention, distortion: an additional turn command appeared out of nowhere!
13. Save the route by overwriting it again;
---> Attention: The route is now displayed with two turns in one place.
In addition to the above...
Here is a simple route that I created using the scheduler and then exported to a GPX file. Then I imported this file into Locus. An attempt to recalculate this file in the scheduler results in the closure of Locus v3 and v4. I've tried doing this on different phones with different versions of Android 7 and 10.
In addition to the above...
Here is a simple route that I created using the scheduler and then exported to a GPX file. Then I imported this file into Locus. An attempt to recalculate this file in the scheduler results in the closure of Locus v3 and v4. I've tried doing this on different phones with different versions of Android 7 and 10.
Hi Vyacheslav,
thanks for reporting the bug. As a whole, it is not considered critical (the procedure to replicate it is quite complicated) so it won't be fixed in Locus Map 3 Classic. The crash in the route planner after importing the route was fixed in LM4 though.
Hi Vyacheslav,
thanks for reporting the bug. As a whole, it is not considered critical (the procedure to replicate it is quite complicated) so it won't be fixed in Locus Map 3 Classic. The crash in the route planner after importing the route was fixed in LM4 though.
This is sad because I use Locus 3. :-(
This is sad because I use Locus 3. :-(
Replies have been locked on this page!