Webplanner viapoints not notified
Web Planner has recently (v2.7.0) included via point management. Thanks! It works very nicely, except there seems to be an issue with notifications not working when navigating the route using the android app, and also with the location of the via points.
If a route is created with the android app then via point locations are always moved to a track point when you save it (you can see where it will be moved to before saving - there is a small green or red dot on the generated route). Makes sense - a via point has to be exactly on the route, unlike independent points which do not.
So, if I create a route with the Web Planner where I explicitly convert the shaping point to a via point I would expect the same thing to happen, but it does not, nor does that happen after syncing with the android app.
When navigating, the via points are not notified - neither on the display nor audibly. (Yes, I did set the 'Notify during Navigation' on the via points in the WebPlanner, and saved the route without setting the 'without navigation commands' option)
This can be corrected by doing recalculate-all in the android app route planner. After that the via points are moved to a track point, and are notified properly when navigating.
The same problem 
Well, it could have been offered a long time ago in a very simple way. But unfortunately, Locus didn’t finish it back then.
TBT GPX navigation track. https://forum.locusmap.eu/index.php?topic=5953.msg49519#msg49519
Check out the following demo video “Just for fun.” https://youtube.com/shorts/ZHdykTAcvVs
You’ll see what Locus, unfortunately, doesn’t offer. Notice as well the u-turn plus via combination.
Well, it could have been offered a long time ago in a very simple way. But unfortunately, Locus didn’t finish it back then.
TBT GPX navigation track. https://forum.locusmap.eu/index.php?topic=5953.msg49519#msg49519
Check out the following demo video “Just for fun.” https://youtube.com/shorts/ZHdykTAcvVs
You’ll see what Locus, unfortunately, doesn’t offer. Notice as well the u-turn plus via combination.
Hi,
we managed to simulate the problem, thanks for reporting it. The devs are working on a fix.
Hi,
we managed to simulate the problem, thanks for reporting it. The devs are working on a fix.
Hello
It appears that the behaviour has changed in the latest release but the issue is not fixed.
Now, in V4.36.1, when I create a route in the Web Planner, with a viapoint not precisely on the route, after it has synced to the android app and I view the track in android then the viapoint is displayed at the position it was created in the web planner. However If I navigate it then the viapoint is still NOT notified/announced.
If I then edit the route in android and save it (in fact I do not need to do recalculate-all) then in the route planner the viapoint (blue box) stays in its original position but when viewing the track (not in route planner) the viapoint is now displayed ON the track - I guess at the nearest trackpoint to the actual viapoint. When I navigate it now the viapoint IS notified/announced.
After syncing back to the web planner and viewing the track the viapoint is displayed at the original position, so android and web track displays are inconsistent.
Is this still "work in progress" ?
Hello
It appears that the behaviour has changed in the latest release but the issue is not fixed.
Now, in V4.36.1, when I create a route in the Web Planner, with a viapoint not precisely on the route, after it has synced to the android app and I view the track in android then the viapoint is displayed at the position it was created in the web planner. However If I navigate it then the viapoint is still NOT notified/announced.
If I then edit the route in android and save it (in fact I do not need to do recalculate-all) then in the route planner the viapoint (blue box) stays in its original position but when viewing the track (not in route planner) the viapoint is now displayed ON the track - I guess at the nearest trackpoint to the actual viapoint. When I navigate it now the viapoint IS notified/announced.
After syncing back to the web planner and viewing the track the viapoint is displayed at the original position, so android and web track displays are inconsistent.
Is this still "work in progress" ?
HI Alan,
could you please send a GPX of the route with a waypoint that is not notified? We'll test it. Thanks.
HI Alan,
could you please send a GPX of the route with a waypoint that is not notified? We'll test it. Thanks.
Hi
I think exporting/importing the track would risk confusing the issue as it would not necessarily provide an accurate representation of what is happening as there might be data altered or lost in the process.
The reported issue is simply about creating a track in web planner then syncing it to android then navigating it. I would expect any viapoint to get notified/announced without knowing that I first have to edit it in android route planner then save it.
To reproduce this is very easy - simply create any route you want in web planner, change a shaping point to a viapoint with notify enabled, then wait for it to sync to android, or do a manual sync , then navigate it using the simulate method (disable GPX and move map center along the route). The viapoint should get notified/announced, but it does not, until you edit/save the route in android. (If you want you can include several viapoints either as close to a path as you can make it or at varying distances from any path)
Alternatively include a lopoint in the web route - which is automatically added as a viapoint - and then sync/navigate. Same happens - no notification/announcement.
Are you saying you cannot reproduce it - i.e. you have tried this and it does work for you ?
Hi
I think exporting/importing the track would risk confusing the issue as it would not necessarily provide an accurate representation of what is happening as there might be data altered or lost in the process.
The reported issue is simply about creating a track in web planner then syncing it to android then navigating it. I would expect any viapoint to get notified/announced without knowing that I first have to edit it in android route planner then save it.
To reproduce this is very easy - simply create any route you want in web planner, change a shaping point to a viapoint with notify enabled, then wait for it to sync to android, or do a manual sync , then navigate it using the simulate method (disable GPX and move map center along the route). The viapoint should get notified/announced, but it does not, until you edit/save the route in android. (If you want you can include several viapoints either as close to a path as you can make it or at varying distances from any path)
Alternatively include a lopoint in the web route - which is automatically added as a viapoint - and then sync/navigate. Same happens - no notification/announcement.
Are you saying you cannot reproduce it - i.e. you have tried this and it does work for you ?
Hi Alan,
of course I tested it the same way you described it, and the via points are announced. Do you have the latest web version? If ynot, please reload the website. Also, make sure you have the latest version of Locus Map app.
Anyway, I'd like to test your route - please send me its sharing URL. This will make sure the route is the same and that no GPX bias will interfere.
Thanks.
Hi Alan,
of course I tested it the same way you described it, and the via points are announced. Do you have the latest web version? If ynot, please reload the website. Also, make sure you have the latest version of Locus Map app.
Anyway, I'd like to test your route - please send me its sharing URL. This will make sure the route is the same and that no GPX bias will interfere.
Thanks.
Hi,
I'm using Web version v2.11.1, and android version v4.36.1. I've tried it on two different android devices.
Here is the share link to a small test track: https://link.locusmap.app/t/quqv1c - created by sharing the track in Web-planner.
It includes three viapoints:
via1 - created from shaping point where I clicked closely on the path
via2 - created from shaping point where I clicked away from the path by about 40 meters.
cats tor - a lopoint included in the route.
All three have the "Notify during navigation" checkbox ticked and when saving the route the "Without navigation commands" checkbox was left un-ticked.
I get no notifications/announcements for the viapoints on both android devices I tried, when navigating using the simulation method. I do get announcements as usual for navpoints.
I have not yet edited/saved the route in android web-planner - as that would do some change which then causes the display of the viapoints to move (as described previously) and the announcements to appear.
Please could you also share a link to a test track where you definitely do get the announcements (without having edited it in android) - it would be useful if you could also include viapoints similar to the ones I included - i.e. on the path, off the path , and a lopoint. I can then test whether I get the announcements - if not then that might point at some setting affecting it.
Please would you confirm - when accessing the link to a shared track does this use the exact same binary representation of the original track , and after syncing to android does that transfer the exact binary version to android with no changes. Also when edit/save in android with no user changes made - what internal changes are made to the route ?
Thanks
Hi,
I'm using Web version v2.11.1, and android version v4.36.1. I've tried it on two different android devices.
Here is the share link to a small test track: https://link.locusmap.app/t/quqv1c - created by sharing the track in Web-planner.
It includes three viapoints:
via1 - created from shaping point where I clicked closely on the path
via2 - created from shaping point where I clicked away from the path by about 40 meters.
cats tor - a lopoint included in the route.
All three have the "Notify during navigation" checkbox ticked and when saving the route the "Without navigation commands" checkbox was left un-ticked.
I get no notifications/announcements for the viapoints on both android devices I tried, when navigating using the simulation method. I do get announcements as usual for navpoints.
I have not yet edited/saved the route in android web-planner - as that would do some change which then causes the display of the viapoints to move (as described previously) and the announcements to appear.
Please could you also share a link to a test track where you definitely do get the announcements (without having edited it in android) - it would be useful if you could also include viapoints similar to the ones I included - i.e. on the path, off the path , and a lopoint. I can then test whether I get the announcements - if not then that might point at some setting affecting it.
Please would you confirm - when accessing the link to a shared track does this use the exact same binary representation of the original track , and after syncing to android does that transfer the exact binary version to android with no changes. Also when edit/save in android with no user changes made - what internal changes are made to the route ?
Thanks
Hi Alan,
thanks for the link to the route. I've tested it with the latest beta version without any issues, see the video: https://drive.google.com/file/d/1Hus_jbRrUjtCaRyf-Ja5S9heeqfBABvj/view?usp=sharing.
Please install the latest beta from our repo at https://bit.ly/lmVersionsTest and test it too.
My route with a few via points that are announced: https://link.locusmap.app/t/wy2ry6.
Hi Alan,
thanks for the link to the route. I've tested it with the latest beta version without any issues, see the video: https://drive.google.com/file/d/1Hus_jbRrUjtCaRyf-Ja5S9heeqfBABvj/view?usp=sharing.
Please install the latest beta from our repo at https://bit.ly/lmVersionsTest and test it too.
My route with a few via points that are announced: https://link.locusmap.app/t/wy2ry6.
Hi
In v4.36.1 your route also does not, for me, announce the viapoints.
In v4.36.1.3_1222_beta viapoints are announced, and after editing the route in android it does not now move the displayed position of the viapoint to the track.
So the bug does exist in v4.36.1 and is fixed in latest beta.
(BTW - One thing which was a bit confusing is that on the forum v4.36.0.1 was listed at https://forum.locusmap.eu/index.php?topic=9736.msg82014#msg82014 which included a lot of fixes in this area, but it turns out this was deferred until after 4.36.1. I wasn't sure if they had been included but just not listed in v4.36.1 as there was a comment about "shrink the list of news". Keep the full list IMO then we can continue to see exactly what changed and when, which does help when encountering issues)
Hi
In v4.36.1 your route also does not, for me, announce the viapoints.
In v4.36.1.3_1222_beta viapoints are announced, and after editing the route in android it does not now move the displayed position of the viapoint to the track.
So the bug does exist in v4.36.1 and is fixed in latest beta.
(BTW - One thing which was a bit confusing is that on the forum v4.36.0.1 was listed at https://forum.locusmap.eu/index.php?topic=9736.msg82014#msg82014 which included a lot of fixes in this area, but it turns out this was deferred until after 4.36.1. I wasn't sure if they had been included but just not listed in v4.36.1 as there was a comment about "shrink the list of news". Keep the full list IMO then we can continue to see exactly what changed and when, which does help when encountering issues)
Hi Alan,
I use Locus Map quite often, obviously, and the use case "planning on the web > navigating on the phone" is very common for me. I didn't notice this issue in 4.36.1. either. Anyway, the issue is now fixed also for you, which is great.
The changelog for each version is generated by an AI code crawler and it should thus contain all changes compared to the previous version in the same build line.
Hi Alan,
I use Locus Map quite often, obviously, and the use case "planning on the web > navigating on the phone" is very common for me. I didn't notice this issue in 4.36.1. either. Anyway, the issue is now fixed also for you, which is great.
The changelog for each version is generated by an AI code crawler and it should thus contain all changes compared to the previous version in the same build line.
Replies have been locked on this page!