I'm not sure how waze plans to handle regional/national/language diffences, but I am assuming that currently we are dealing with US English. If that is the case I would add in the state abbrieviations. For instance "MD" is pronounced "emm-dee" by waze. "Penn" is a problem and is pronounced "Pennsylvania."
I would also add the following:
Alternate - ALT
Bound - BND
Crossing - X-ING
Expressway - EXPWY
International - INTL
National - NATL
Route - RT
Throughway - THWY
I would also note that some abbrieviations are ambiguous: ST for Saint or Street and DR for Doctor or Drive. Also some streets are lettered thus there are "E St (or Ave, Blvd etc.)," "N St," "S St" and "W St" out there. Ultimately, there will need to be a method for distinguishing "St" when it means Saint and "St" when it means Street and "N" when it means North and "N" when is should just be "N." If this is done with punctuation then we need to test "St" and "St." etc. If this is done by parsing the phrase, that is "N" is N if followed by a road designation, but north otherwise, then we will need to indicate the different results depending on the phrase.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 18.104.22.168