Waypoints

Started by Andy Todd, April 08, 2019, 08:41:22 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Andy Todd

The new waypoint system appears to have a number of bugs.



I use oruxmaps with TTS on waypoint names, and it will often miss the closest waypoint and on the screen show that it has select another one.



In addition the TTS is not read at the selected distance, but at something closer. eg Waypoint distance is set to 40m it will speak at 30m.

orux

#1
Quote from: "Andy Todd" post_id=30799 time=1554748882 user_id=1800
The new waypoint system appears to have a number of bugs.



I use oruxmaps with TTS on waypoint names, and it will often miss the closest waypoint and on the screen show that it has select another one.



In addition the TTS is not read at the selected distance, but at something closer. eg Waypoint distance is set to 40m it will speak at 30m.


Hello!



Maybe you can provide an example of route as GPX.



You have to take into account the GPS settings. 40 meters it can be a short distance, if you are cycling, for example.



The app starts giving the messages the first time it detects the Wpt at a distance less than the indicated one.



If the Wpts are not exactly on the route, the app takes the nearest point of the route as a reference. It will not always indicate the closest Wpt, if you have already passed a Wpt, and you move away, the app can indicate the following.



On round-trip routes along the same route, there may be a problem, if the Wpts. they are not exactly on route points.



orux

Andy Todd

#2
Attached is link to a quick example, and a the recorded logs.



The route walked was Untitled (6). On the way out (2019-04-08 2240__20190408_2240) Oruxmaps did not speak waypoints 5 and 6. On the return (2019-04-08 2249__20190408_2249) it failed to speak waypoint 4.



The screen captures should give an indication of 2 of those



https://drive.google.com/drive/folders/1ie4zttWxiPJ7gFwbKBRXyA8zr-GTc5Bt?usp=sharing">//https://drive.google.com/drive/folders/1ie4zttWxiPJ7gFwbKBRXyA8zr-GTc5Bt?usp=sharing

orux

#3
Quote from: "Andy Todd" post_id=30802 time=1554761348 user_id=1800
Attached is link to a quick example, and a the recorded logs.



The route walked was Untitled (6). On the way out (2019-04-08 2240__20190408_2240) Oruxmaps did not speak waypoints 5 and 6. On the return (2019-04-08 2249__20190408_2249) it failed to speak waypoint 4.



The screen captures should give an indication of 2 of those



https://drive.google.com/drive/folders/1ie4zttWxiPJ7gFwbKBRXyA8zr-GTc5Bt?usp=sharing">//https://drive.google.com/drive/folders/1ie4zttWxiPJ7gFwbKBRXyA8zr-GTc5Bt?usp=sharing


I'm sorry, but it's a route with very few points.



 The app uses the points of the route as a reference.



In this case, where each wpt is almost a waypoint, the 'wpts navigation' mode works much better. Try like this.







orux

Andy Todd

#4
Tried to give you a simple failure, I am sure that those waypoints would have been spoken in the past, but are now not.



In the past I have always used follow route. My preference would be to use follow route for the route alarm, and distance calculations.



I have put into that drive share 2 more GPX



2019 Shropshire Way 80K.gpx was the route I was following

2019-04-06 0900__20190406_0900.gpx was the log of the walk



Orux map missed a large number of waypoints, but can only remember a few. Some that I know were missed were



  <wpt lat="52.46583" lon="-2.81993">

    <name>T-junction. Here turn right and continue along the road for 250m to reach a ford</name>

  </wpt>



  <wpt lat="52.44205" lon="-3.00428">

    <name>forestry track. Here turn right and continue for 400 meters to a fork.</name>

  </wpt>



  <wpt lat="52.44165" lon="-2.86715">

    <name>go through the stile, cross a little footbridge, through a metal gate go across a small field for 70 meters, to reach another metal gate leading into a carriage drive. Turn right down the carriage drive for 300 meters to a crossroads</name>

  </wpt>



also from memory none of the waypoints with a name 'continue' were spoken, eg



  <wpt lat="52.47729" lon="-2.78697">

    <name>continue</name>

  </wpt>



  <wpt lat="52.44763" lon="-3.06534">

    <name>continue</name>

  </wpt>

Andy Todd

#5
After more experimentation I cannot get the new waypoint TTS to work reliably.



This was something that worked all the time before.



Can you tell me what version was the last with the old approach in and where I can download a copy?