First I have to say that I am very impressed with this new function! It was a long waited option to ride on bicycle within the previously recorded random (or borrowed other) track with the voice prompts.
So after some testing with random tracks I have two rationalization suggestions.
1. I think its a good idea to voice the distance to the next driving maneuver provided that the distance to it is more than 1 kilometer. I have to explain this. When riding with the phone in the pocket, after the another turn you dont know how many kilometers you have to go further. So for example riding half an hour with silence you mentally start to worry about the program itself (it may crash) or phone itself or any other shit can happen! BUT when you know exactly that you must ride forward for 5,5 kilometers you can just relax and pedaling. ))) Just say "Keep moving more than 5 kilometers".
2. Recorded tracks often have the errors or unnecessary movements on the spot.
I think it would be a good thing for the algorithm to ignore the small track inaccuracy within 20-30 meters. I.E. if the radius of the some maneuvers is within the range of 20-30 meters and after them the direction of the route is still the same - there is no need to specify maneuvers.
The voice guiding will be confusing in such case.
Or in general if the track has more than one maneuver (change of the directions) within the range of 20-30 meters it would be logical to only take into account the last waypoint where the direction is changing.
For example in this case we have not the true left turn but "take the left" only.
So after some testing with random tracks I have two rationalization suggestions.
1. I think its a good idea to voice the distance to the next driving maneuver provided that the distance to it is more than 1 kilometer. I have to explain this. When riding with the phone in the pocket, after the another turn you dont know how many kilometers you have to go further. So for example riding half an hour with silence you mentally start to worry about the program itself (it may crash) or phone itself or any other shit can happen! BUT when you know exactly that you must ride forward for 5,5 kilometers you can just relax and pedaling. ))) Just say "Keep moving more than 5 kilometers".
2. Recorded tracks often have the errors or unnecessary movements on the spot.
I think it would be a good thing for the algorithm to ignore the small track inaccuracy within 20-30 meters. I.E. if the radius of the some maneuvers is within the range of 20-30 meters and after them the direction of the route is still the same - there is no need to specify maneuvers.
The voice guiding will be confusing in such case.
Or in general if the track has more than one maneuver (change of the directions) within the range of 20-30 meters it would be logical to only take into account the last waypoint where the direction is changing.
For example in this case we have not the true left turn but "take the left" only.