replace "soon" by a real distance estimate

[kiddo]

soon is useless. The driver needs a real distance/time estimate announcement, which navit should have no problem providing since it already does for other announcements. 2 3 This also entails a sub-bug: if the user is told "soon" and that navit means "in 5 street corners", the user will have no idea if the street corner/traffic light he sees in 10 meters is the one to be considered "soon".

[kiddo]

one liner patch that fixes the problem for good

[KaZeR]

I personnaly agree about the fact that 'soon' is useless. But i'll have to check with cp15 if he's ok about this change.

[KaZeR]

It is intended to make it configureable.

[Kiddo]

well, in the meantime, having the (I think) "saner" default that this patch provides is better. The option to control it (though I have no idea why someone would want navit to give uncertain statements like "soon") could come later.

[akashihi]

In my opinion, 'soon' is usefull. It warns you that in the near future you'll get detailed description of the next maneuvre.

Oops, missed entry fields

[number6]

I agree with OP - Replace "Soon" with a real distance estimate.

[number6]

To back track on myself, "Soon" can be configured in navit.xml

<announcement level="2" distance_metric="200"/> Is an example of the line that can be edited.

[korrosa]

To clarify Number6's point:

• <announcement level="2" distance_metric="200"/> specifies the distance (metres) before the manoeuvre when "soon" is used.
• <announcement level="1" distance_metric="100"/> specifies the distance (metres) before the manoeuvre when "in X metres" is used.
• <announcement level="0" distance_metric="50"/> specifies the distance (metres) before the manoeuvre when "now" is used.

As such, the functionality is available to enable/disable the "now" announcement in Navit. If you wanted Navit to give two announcements with "in X metres", then try applying the patch.