Well, Google will be handling that for us for the foreseeable future. So no real worries there. The real issue is with the system by which the Google result is matched to the Waze address — for search issues, that is.

For navigation, the street name should match the sign as closely as possible. This has been Waze's guiding principle for a very long time, even for ramps. If the sign says "Louis XIV", Waze should say "Louis XIV."

Search is more flexible than navigation. Worst case, someone searches for "1034 Second St" and gets the Google pin instead of the Waze address point for 1034 on "2nd St". They'll still get there.

dbraughlr wrote:I favor eliminating all Roman numerals as abbreviations. The disadvantages far outweigh any advantages. Pronunciation of "XIV" can be addressed when the pronunciation of "Louis" is addressed.

Unless "Louis" is pronounced neither the English nor the French way, it cannot be "fixed". In some places one will be right, and in others the other, but no universal fix is possible.

Now, on the other hand, there is no reason why "Iberville" should be pronounced "d'Iberville"...

dbraughlr wrote: Another proposal in another thread addressed this; I'm pretty sure you were there.

Unless it was to give us a manually-controlled pronunciation field, I don't recall it.

AlanOfTheBerg wrote:

driving79 wrote:On a ramp in Jacksonville, FL this is saying STREET: to I-295 S St. Augustine.

That looks like a malformed segment name. Shouldn't it be either "to I-295 S / St. Augustine" or "to I-295 / S St. Augustine"?

I agree, but should it matter? Wasn't the point to take position awareness out of the "Saint"/"Street" dichotomy entirely, making every "St." "Saint" and every "St" "Street"? So, did only the latter actually happen?

AlanOfTheBerg wrote: If you check the TTS testing file in the OP, "Br" is supposed to be "Branch" as a USPS standard. "Brg" is supposed to be used for Bridge.

If there are enough "Branch" roads out there I guess I'll keep quiet, but it's a bit weird that we follow the USPS and not the MUTCD for this, since Waze is more sort of a "traffic control device" in a way. The MUTCD standard is "Br" for "Bridge" – but then, the MUTCD doesn't include several of the less-common street name suffixes.

I think this is the only instance of an MUTCD abbreviation that is expanded to something different in Waze.

Rest assured "Br" is certainly used. One of the exits nearest my house serves "Huey Long Br", and a wayfinder-ish sign near downtown says "Miss River BR" (I'm not sure why the caps). As for "branch", I can't attest to that necessarily. I'm not familiar with any such roads, but it's possible I've come across them.

That would be seriously unusual, considering normal interstate names are pronounced "i" (like I-10, "i ten").


Sent from my iPhone using Tapatalk 2

I still think the two letter state abbreviations on their own (not followed by a hyphen) should be removed from the custom abbreviation list. Have we asked for that yet? Too much potential for conflict.


Sent from my iPhone using Tapatalk 2

I just think there's a better way. BGSes usually use the old-fashioned abbreviations, and I think it'd be nice to include those, with periods only, as TTS abbreviations – for example Ala. for Alabama, La. for Louisiana, Calif. for California, Penna. and/or Pa. for Pennsylvania, and so forth. We just need to come up with a definitive list.

PesachZ wrote: I believe all the two letter abbreviations for the 50 states are active.

I think (hope) that Nebraska's abbreviation was reverted to "Northeast".