"Street" being pronounced "Saint"

The street I live in, I have noticed, gets pronounced as View Saint instead of View Street regularly. Recently I thought I heard it get pronounced the correct way, but then heard it pronounced wrong again.

Not sure how to request for this to be fixed, or if it can be fixed? I had a look through some long threads on TTS and abbreviations, but got a bit overwhelmed.

I am keen to help improve Waze when I can too.

Mark

For things such as this, the wiki is the best place to start. There is an entire page covering abbreviations and how they affect TTS (https://wiki.waze.com/wiki/Abbreviations_and_acronyms)

Basically, somehow has that street named “View St.” but it should be “View St” with no period at the end.

Thanks, that’s odd as it appears as either View Street or View St (this is in Highett, Victoria). Never see it with the period.

I will test it again today and see if perhaps it’s been fixed since I last experienced it.

Thanks for the helpful reply!!

Just had a UR report that the suburb ‘Saint Marys’ is being pronounced as ‘Street Marys’.
Permalink

Seems like the TTS system has had some changes recently according to the wiki:
https://wiki.waze.com/wiki/Abbreviations_and_acronyms

A quick search of the linked forum seems to indicate the best way to fix this is to place a period after the ST. ie
‘St’ = Street
‘St.’ = Saint

This could mean updating all streets in quite a few suburbs.

As per the Wiki:

If you plug the street name into the search bar with the dot after St does it locate the offending segments?

But changing the suburb name to “St. Marys” would be wrong. The suburb name is “St Marys”, not “St. Marys” and not “Saint Marys”.

Likewise for street names. “Saint” is abbreviated as “St” in Australia, not “St.” We follow UK spelling & shouldn’t follow American spellings just because the American programmers tell us to.

Are we going to introduce map errors just so we can get the TTS right? Surely the fix is to get the TTS programmers to fix the problem, or introduce a phonetic/pronunciation field.

Agree with B Carp 100%

I think we are getting off on a tangent here. Firstly this thread started about a street being pronounced saint. As far as I can tell there was no reason for that as the street was named correctly.

Next, Jay brought up a separate UR. However, I don’t see how this could happen as I don’t ever recall the suburb being read out except if it was written on a BGS. If that is all we are talking about then that one segment will have to be named as per the wiki for the TTS to work.

If you want a broader change to the TTS engine to somehow know when it should say street and when it should say saint with nothing to go on then I think that is a bit of an ask. The wiki is clear for suburbs dont use the fullstop as it is not required. For street names though it is required for the TTS to work. You have to do that because otherwise the TTS will say street and there is pretty much nothing you can do to avoid that except spell it out which we dont really want to do.

So just do as per the wiki that jab_au posted and everything should work fine with minimal deviation from what you would traditionally see in Oz.

That is true. My solution would be not to say “street” when it is in the city name but we know how hard it is to get Waze HQ to do anything we actually want… :frowning:

In the meantime you have to follow the wiki if you want the TTS to work. If Waze HQ ever does a fix then they could do a global search and replace to change everything back.

You are probably right but again the chance of Waze changing something…?

An editor has gone ahead and renamed an entire suburb changing St to Saint.

Did we come to the conclusion that this wasn’t the preferred solution here?

Can you post a permalink to the suburb, thanks

Of course.

Permalink

Usually I would resolve this type of query by working with the editor is question, however after attempting communication with this particular editor in the past and receiving no reply ever - I’ve given up!

Edit: Fixed permalink

I wonder if it’s the same editor I’ve had issues with as well. Unfortunately I can’t get your permalink to work. I can’t seem to sign in to what looks like the beta map editor that you’re linking to

Permalinks should be to the production WME

Whoops fixed the link.

Well it would appear that it is “St Clair” but you are going to have to make it “St. Clair” if you need the TTS to say it properly.

Travelling_Gav, you are correct on the TTS, but would still disagree that doing this is the correct thing to do as the suburb name is clearly “St Clair” & not “St. Clair”. Same for St Marys. I don’t think we should be putting in an incorrect suburb name just because Waze doesn’t have a phonetic field for TTS. This is a Waze problem that should be fixed by HQ.

Tangent: I’ve had the same problem with this editor. Sending multiple PMs on multiple dates on multiple topics – all marked as “read” in the PM section, so he/she is getting them, but just choosing not to respond. And this from a Level 4 “former” area manager.

Clearly violates this: https://wiki.waze.com/wiki/Common_editing_mistakes#The_worst_incorrect_edit.