[EAS] What is the solution for the TTS problem?

Harold Price hprice at sagealertingsystems.com
Fri Jan 20 10:49:37 CST 2012


One standard TTS program at the end points isn't likely.  Hardware 
and software platforms are different across vendors.

What is more likely is a standard set of abbreviation handling, and a 
best practices document for emergency managers on how to deal with 
TTS.  I don't think it will be hard to get ECIG to consider working on this.

For example, we can decide that 911 always means nine one one, and if 
you want nine hundred eleven, you have to spell it out.

TTS seems easy.  Try "East of I405 it will be 105 degrees".  There 
are lots of ways to get that wrong.  When you have to mentally 
re-parse what you hear, you tend to miss the next part.

Now that almost all other aspects of CAP and EAS have been worked 
out, I think the EAS/CAP vendors need to get some agreement on a 
standard rule set for tts abbreviations.

Something else that needs agreement is how to handle NOAA 
messages.  Sometimes "..." is used as a hypen, sometimes as a comma, 
sometimes it is just superfluous.

A WINTER STORM WARNING MEANS THAT SNOW...SLEET...OR ICE WILL MAKE 
TRAVEL HAZARDOUS OR IMPOSSIBLE. REPORT SNOW OR ICE ACCUMULATION TO 
THE NATIONAL WEATHER SERVICE BY CALLING TOLL FREE...1-877-633-6772.

Harold

At 02:02 PM 1/19/2012, Barry Mishkind wrote:
>At 11:22 AM 1/19/2012, Tom Taggart wrote:
> >The big boxes (Sage, Dasdec, Tri-lithic) are all computers.
> >I am assuming if heads were beat together to use a
> >standardized text-to-voice program it could be made to work
> >on all three & just downloaded at a later date.
>
>         Well, that was my unstated concept.
>         Are we afraid of some idiotic conspiracy,
>         or collusion?  Or can we accept that
>         Perfect Paul (or some other file) be
>         made the "standard?"
>
>         Does the government own PP, or
>         would that create (oh my, lawyers
>         salivate) royalty issues?
>
>         Maybe the EAS manufacturers could
>         combine efforts in an "open software"
>         effort to make a standard?
>



More information about the EAS mailing list