Driving instructions in odd numbers of feet when using imperial measurements

[la7qz om]

Hi

When using imperial measurements, I get spoken instructions like "Turn right in 798 feet. I assume the decision on when to speak the instruction is made based on metric measurements and then converted before it is sent to espeak. It would be better if the decision was based on the units in use so that the spoken instrucion would be "Turn right in 800" feet. Given at the correct point of course. That would make the spoken instruction shorter and easier to understand.

Owen

[la7qz om]

Copilot (on Android) speaks the instruction as "In two tenths of a mile, turn right"

[korrosa]

As a workaround for now, you can change the distance that the announcements are made at by converting your imperial lengths into metric equivalents.

So for example, 800 feet would be 243.84 metres. You can do this in the <announce ... > tags within the <navigation> tag (don't use those in the vehicleprofile tags - they don't work yet). You would need to change level0, level1 and level2 values for each announce tag (currently four in the default navit.xml).

I, too, live in a silly imperial country, but haven't tried the method above....

[usul]

Had this been fixed already?

Otherwise a suggestion:

• short time: add the ability to define the units within the <announce> element. Convert them into the current active runtime unit system, but give rounded values (e.g. "800ft" would result in "in 240m")
• long time: setup a default catalogue for distances, to allow spoken wavepacks trigger for this exact values

[robotaxi]

fixed in r6127. Miles and feet are now announced in appropriately rounded values.