hmarian wrote:Working with Waze to fix this is the way to go.
Sure! This is just a suggestion
jasonh300 wrote:This would be a very bad idea and would defeat the true purpose of Alt Name fields (which is for search results).
No, it's not. For instance:
Street: Northeast Kentucky Industrial Parkway <- this would be used by default (for search in this case)
Alt City: #short Alt Name: Northeast Pkwy <- this would be used to display and for TTS
Correction of pronunciation:
Street: John Paul IV Street <- this would be used by default (for search and to display)
Alt City: #tts Alt Name: John Paul 4th St <- this would be used for TTS
The #tts name could be a transcription (phonetic spelling) of the street name.
Having a prefix (#) it's easy to disting those properties and not use them for search if you like. But its not such a bad idea if one could find both '4th' and 'IV' IMO.
jasonh300 wrote:However, it wouldn't be a bad idea for a new dedicated field in which a phonetic spelling of names could be entered.
You see! They call it a brainstorming