Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine announcing highway refs #19869

Open
ZeljkoBG opened this issue May 14, 2024 · 6 comments
Open

Refine announcing highway refs #19869

ZeljkoBG opened this issue May 14, 2024 · 6 comments
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@ZeljkoBG
Copy link
Contributor

Add an option, trigger, so tts doesn't pronounce the number of road/street. It's just a name.
Most people don't care about the number of roads. And it's irritating.

@yuriiurshuliak
Copy link

To achieve a more streamlined voiace guidance experience, you can customize the voice prompt settings in the OsmAnd application. By disabling options such as Street names (TTS), Exit number, Traffic warnings, Pedestrian crosswalks, and Tunnels in the voice prompts settings, you can reduce the frequency of voice instructions.

To access the voice prompt settings, go to Menu → Navigation → Settings → Sound → Settings.

@ZeljkoBG
Copy link
Contributor Author

What you write has nothing to do with the pronunciation of the street name + "number of road/street".

Some applications, by default, do not read 'number of road/street' and others app have an option to turn it off (trigger).

@sonora
Copy link
Member

sonora commented May 15, 2024

The significance of highway numbers is extremely region-sensitive. In the US, for example, knowing the number of a US, state, or even county road will get you a long way and is very essential. In Germany, the number of motorways (Ax) or national highways (Bx) is significant, too, as found on all signing as well as in traffic announcements. While for lower hierarchy highways (e.g. "Staatsstrassen") the use of the numbers is limited to special cases only, e.g. construction crew or emergency crew maps.

Long story short, it is not easy to predict in what cases number announcement is essential vs. expendable. But I am certain it is more a regional topic than one of personal preference, e.g. the same user in different regions would in one region need numbers, in another not.

@ZeljkoBG
Copy link
Contributor Author

The solution is to select a trigger. Who needs it should read it. Who should not turn off. Simple.

@sonora
Copy link
Member

sonora commented May 15, 2024

The solution is to select a trigger. Who needs it should read it. Who should not turn off. Simple.

Possible solution, yes. But when you read my analysis above you will find it argues that a good solution would be region-automated. While a "select trigger" (I assume you mean a user setting) would be a manual user choice, potentially an inferior solution.

@sonora sonora changed the title TTS pronunciation - road/street number Refine announcing highway refs May 15, 2024
@ZeljkoBG
Copy link
Contributor Author

Of course it should be an option in the settings for TTS. And where else would you?

The worst option is your suggestion 'region-automated', because no application has that.
'potentially an inferior solution' - the best navigations have a selection (trigger). So 'inferior solution' has been an option for 20 years.

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests

4 participants