AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
banished wrote:AlanOfTheBerg wrote:I saw a street sign today for a "Terrace" which used "TR" as the abbreviation. This would conflict with "TR" for "Trail."
I am uncertain if spelling or standard abbreviations is taught at Street Sign School.
Normally, Trail would be Trl, Terrace would be Ter
https://www.usps.com/send/official-abbreviations.htm (click on the Street Suffixes tab).
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?
jasonh300 wrote:How about "Int'l"?
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.
Users browsing this forum: No registered users