include street names in voice guidance

TimMagee commented

2021-06-18 04:55:05 +00:00

(Migrated from github.com)

Almost every navigation app in existence will say the name of the street that the user is supposed to turn on. Organic Maps does not do this.

Here is an example. If the user is coming up on a turn, and is supposed to turn right on Second Street in 900 feet, Organic Maps will state "In 900 feet, turn right". In order to find the name of the street, the user must look at the app and check the name of the street displayed at the top.

It would be of great benefit if the app stated, "In 900 feet, turn right on Second Street" so that the user would know what road to turn onto without having to look at the app.

Almost every navigation app in existence will say the name of the street that the user is supposed to turn on. Organic Maps does not do this. Here is an example. If the user is coming up on a turn, and is supposed to turn right on Second Street in 900 feet, Organic Maps will state "In 900 feet, turn right". In order to find the name of the street, the user must look at the app and check the name of the street displayed at the top. It would be of great benefit if the app stated, "In 900 feet, turn right on Second Street" so that the user would know what road to turn onto without having to look at the app.

👍 9

letkan commented

2021-06-18 07:19:04 +00:00

(Migrated from github.com)

Almost every navigation app in existence will say the name of the street that the user is supposed to turn on. Organic Maps does not do this.

Here is an example. If the user is coming up on a turn, and is supposed to turn right on Second Street in 900 feet, Organic Maps will state "In 900 feet, turn right". In order to find the name of the street, the user must look at the app and check the name of the street displayed at the top.

It would be of great benefit if the app stated, "In 900 feet, turn right on Second Street" so that the user would know what road to turn onto without having to look at the app.

I would recommend street names as an option only, not a default, from experience I can tell you that the pronunciation of street names in a language other then the local one is more annoyance then help.

> Almost every navigation app in existence will say the name of the street that the user is supposed to turn on. Organic Maps does not do this. > > Here is an example. If the user is coming up on a turn, and is supposed to turn right on Second Street in 900 feet, Organic Maps will state "In 900 feet, turn right". In order to find the name of the street, the user must look at the app and check the name of the street displayed at the top. > > It would be of great benefit if the app stated, "In 900 feet, turn right on Second Street" so that the user would know what road to turn onto without having to look at the app. I would recommend street names as an option only, not a default, from experience I can tell you that the pronunciation of street names in a language other then the local one is more annoyance then help.

TimMagee commented

2021-06-18 14:51:12 +00:00

(Migrated from github.com)

I would recommend street names as an option only, not a default, from experience I can tell you that the pronunciation of street names in a language other then the local one is more annoyance then help.

Well, then lets make it the default if the language of the current region matches the language of the TTS engine. For example if I am navigating in the USA (where English is the primary language), and I am using English as my TTS language, street names will be on by default.

We could have them off be default if the primary language of the region does not match the TTS language. So, in my case if I switch to Spanish TTS, then street names would be off by default.

> I would recommend street names as an option only, not a default, from experience I can tell you that the pronunciation of street names in a language other then the local one is more annoyance then help. Well, then lets make it the default if the language of the current region matches the language of the TTS engine. For example if I am navigating in the USA (where English is the primary language), and I am using English as my TTS language, street names will be on by default. We could have them off be default if the primary language of the region does not match the TTS language. So, in my case if I switch to Spanish TTS, then street names would be off by default.

Donkey-Doug commented

2021-10-23 22:40:13 +00:00

(Migrated from github.com)

I don't know a maps app that pronounces street names. Seems unnecessary. Perhaps add is as an option.

👎 2

TimMagee commented

2021-10-23 23:31:02 +00:00

(Migrated from github.com)

Here is a list of maps apps that pronounce Street Names:

Google Maps
Apple Maps
Bing Maps
OsmAnd
Garmin GPS devices
Here Maps
Waze

Perhaps in Non-English locales, some of these don't. But everyone in the USA expects a maps app to read the street name aloud and will think the app is "broken" if it doesn't.

Here is a list of maps apps that pronounce Street Names: - Google Maps - Apple Maps - Bing Maps - OsmAnd - Garmin GPS devices - Here Maps - Waze Perhaps in Non-English locales, some of these don't. But everyone in the USA expects a maps app to read the street name aloud and will think the app is "broken" if it doesn't.

👍 4

zyphlar commented

2021-11-14 07:31:54 +00:00

Member

Additionally, exit numbers on motorways. A simple "take exit 54" greatly reduces the difficulty of using a GPS app, at least in America where every significant exit is consistently numbered with prominent signage.

The longer-form announcement for motorways would often omit the street name unless it's the only destination name, so "take exit 54 for/towards Seattle" or "take exit 65 for 5th Street." Sometimes in interchanges both are supplied: "take exit 123, for I-10 towards Seattle" or surface streets: "take exit 12 for 5th Street, Downtown Shops" but that quickly gets into "would be nice" territory.

The big mistake to NOT make at least in America is, don't just announce the destination:ref. Many junctions happen where your choices are Highway 12 North, Highway 12 North: Business Route, and Highway 12 South. Which can often be tagged in OSM like "Hwy 12" so not only can the data quality be poor but using it as a navigational aid is confusing. Since we are often putting the unique exit number and the helpful large destination name in the database, those are the most important things to say out loud: 12 North goes Downtown, 12 South goes to Springfield, and 12 Business clearly has its destination set to "Business Route," confusion solved.

Additionally, exit numbers on motorways. A simple "take exit 54" greatly reduces the difficulty of using a GPS app, at least in America where every significant exit is consistently numbered with prominent signage. The longer-form announcement for motorways would often omit the street name unless it's the only destination name, so "take exit 54 for/towards Seattle" or "take exit 65 for 5th Street." Sometimes in interchanges both are supplied: "take exit 123, for I-10 towards Seattle" or surface streets: "take exit 12 for 5th Street, Downtown Shops" but that quickly gets into "would be nice" territory. The big mistake to NOT make at least in America is, don't just announce the `destination:ref`. Many junctions happen where your choices are Highway 12 North, Highway 12 North: Business Route, and Highway 12 South. Which can often be tagged in OSM like "Hwy 12" so not only can the data quality be poor but using it as a navigational aid is confusing. Since we are often putting the unique exit number and the helpful large destination name in the database, those are the most important things to say out loud: 12 North goes Downtown, 12 South goes to Springfield, and 12 Business clearly has its destination set to "Business Route," confusion solved.

👍 4

MarcTheSpark commented

2021-12-09 21:51:45 +00:00

(Migrated from github.com)

Just to add another voice to this: I had been using OSMAnd and just find out about organic maps, so I downloaded it. It looks great, works great, but I was baffled by the lack of street names in navigation, which forced my to take my eyes off the road a bunch unnecessarily. I'm in the US, for context, and agree that this is an expected feature of a maps app in this region.

👍 2

sn0ot commented

2022-01-12 19:12:12 +00:00

(Migrated from github.com)

echoing @zyphlar 's comment

Additionally, exit numbers on motorways. A simple "take exit 54" greatly reduces the difficulty of using a GPS app, at least in America where every significant exit is consistently numbered with prominent signage.

Voice guidance saying "turn right to exit 4B" instead of "turn right" is absolutely necessary in situations when multiple exits exist and are several hundred meters apart.

I've been screwed in similar situations to when, for example, I need to take Exit 4B and just couple hundred meters before it is Exit 4A. I was approaching Exit 4A and the navigator gave me a heads up to "turn right" implying take Exit 4B and the confusion can send a worried driver swerving to not miss Exit 4A that is closer.

"turn right to Exit 4A" would be a sufficient start to address this issue and "turn right to Exit 4A, follow signs to Rt Blah" could be the end goal.

echoing @zyphlar 's [comment](https://git.omaps.dev/organicmaps/organicmaps/issues/615#issuecomment-968237661) > Additionally, exit numbers on motorways. A simple "take exit 54" greatly reduces the difficulty of using a GPS app, at least in America where every significant exit is consistently numbered with prominent signage. Voice guidance saying "turn right to exit 4B" instead of "turn right" is **absolutely necessary** in situations when multiple exits exist and are several hundred meters apart. I've been screwed in similar situations to when, for example, **I need to take Exit 4B and just couple hundred meters before it is Exit 4A. I was approaching Exit 4A and the navigator gave me a heads up to "turn right" implying take Exit 4B and the confusion can send a worried driver swerving to not miss Exit 4A that is closer.** "turn right to Exit 4A" would be a sufficient start to address this issue and "turn right to Exit 4A, follow signs to Rt Blah" could be the end goal.

👍 1

tvld commented

2022-06-02 04:28:02 +00:00

(Migrated from github.com)

I drive a lot in Europe with Waze, real-time traffic is essential, but the English accent for Street names make it unusable. They only sound good with original language voice... Just to consider;))

AntonM030481 commented

2022-06-03 10:34:24 +00:00

(Migrated from github.com)

I believe that we can easily add voice for exit numbers and road numbers.
Since they usually consist from letters and digits, which are pronounced separately.
Note: in USA numbers of target roads at exit contain also directions at the end, like B2 North or X33 South.

Destination names and road names look like much more difficult to implement with reasonable quality.

I believe that we can easily add voice for exit numbers and road numbers. Since they usually consist from letters and digits, which are pronounced separately. Note: in USA numbers of target roads at exit contain also directions at the end, like B2 North or X33 South. Destination names and road names look like much more difficult to implement with reasonable quality.

TheAdventurer64 commented

2022-06-17 09:34:50 +00:00

(Migrated from github.com)

What steps need to be done in order for this feature to be added?

TimMagee commented

2022-06-17 12:09:49 +00:00

(Migrated from github.com)

What steps need to be done in order for this feature to be added?

Here is my personal opinion as to what needs to be done for this issue:

We need a new setting.

This setting will be located at Settings -> Navigation -> Voice Instructions.
It will be titled, "Say Street Names".

When this settings is set to on, the voiced navigation instructions need to include Street Names.

> What steps need to be done in order for this feature to be added? Here is my personal opinion as to what needs to be done for this issue: 1. We need a new setting. - This setting will be located at Settings -> Navigation -> Voice Instructions. - It will be titled, "Say Street Names". 2. When this settings is set to on, the voiced navigation instructions need to include Street Names.

TheAdventurer64 commented

2022-06-18 20:23:26 +00:00

(Migrated from github.com)

What steps need to be done in order for this feature to be added?

Here is my personal opinion as to what needs to be done for this issue:

We need a new setting.

This setting will be located at Settings -> Navigation -> Voice Instructions.

It will be titled, "Say Street Names".

When this setting is set to on, the voiced navigation instructions need to include Street Names.

Regarding this, I think that street names should be on by default. You shouldn't have to turn on any settings in order for street names to be enabled.

> > What steps need to be done in order for this feature to be added? > > Here is my personal opinion as to what needs to be done for this issue: > > 1. We need a new setting. > > * This setting will be located at Settings -> Navigation -> Voice Instructions. > * It will be titled, "Say Street Names". > > 2. When this setting is set to on, the voiced navigation instructions need to include Street Names. Regarding this, I think that street names should be on by default. You shouldn't have to turn on any settings in order for street names to be enabled.

👍 2

zyphlar commented

2022-08-08 06:42:39 +00:00

Member

Implemented in #3130

🎉 2

Rows
Columns

include street names in voice guidance #615