R4CLucky14 wrote:With all this conflicts, why are we doing this? Wouldn't it be better to simply ask Waze to implement a TTS field, so we can actually follow the goal of making it simple to the user: matching the BGS?
sketch wrote:For the record:
"Intl" is pronounced like "Entull". It would be nice to have it pronounced as "International".
The example that led me here is doubly problematic, in fact: an exit is signed as "N.O. Intl Airport". If I label it "N.O. Intl", it'll say "North Oh Entull", but if I say "NO" it'll just be "No Entull". I'm going to label this segment "New Orleans International" for now, but it would be nice to have it somehow workable.
sketch wrote:Have you tried "Thwy" yet? That's how it's abbreviated up on the exit signs up in Baton Rouge.
BrianCanFixIT wrote:I've just encountered a sign with "Drwy" for Driveway. so I guess the other permutation for this would also be valid: drwy, drway.
CBenson wrote:I see that "Pr" has been added to the spreadsheet. Please note that the entries I have heard are for "Pr." - with the period (if that makes a difference).
DonJ2 wrote:Does anybody know if "Par" is announced as "Parade" via TTS?
I did not see it in the spreadsheet. I'm asking because of a UR that says "Par St" is not "Parade St". Not a single segment along "Par St" is or ever has been "Parade St", so I'm wondering if TTS says "Parade St" instead?
CBenson wrote: I would also note I was somewhat surprised (not having any use for the "Manual on Uniform Traffic Control Devices" except for waze map editing) at how much each state might change that list. Here is Maryland's for example.
Users browsing this forum: No registered users