[EAS] Wish List

[Tom]

I could see this being done in software, similar to how RDS data is originated (and why isn't RDS addressed in the wish list?  The CAP messages are supposed to be text, right?)  The station receives the general CAP alert, and the local box (dedicated or convert-to-legacy) appends the station data (voice and/or text) from a local flash drive or other source before broadcast.  Of course, the legacy EAS box should be transmitting the EAS header anyway - which includes the facility relaying the message (the up to 8 characters at the end of the header - "LLLLLLLL") as defined in 11.31(c).

And the length of the "what the listener should do in the emergency" does need to be delimited somewhere.  Although some of these "action advisories" could be pre-recorded and saved outside the normal store-and-forward memory, selected by the header content.

For example, the NWS advisories about thunderstorms, tornadoes, blizzards, etc., are canned; those could easily be saved as text, voice, or both and get added to the message locally.  This would also save bandwidth that might go away in the middle of transmitting a lengthly alert.

Just my $0.20 (inflation)


Tom Taggart wrote:

>Paragraph 40: "... call sign/location of transmitting station & what listener
>should do in emergency."
>
> Who the hell is going to do all this--when you through in
>call letters this automatically becomes the responsibility
>of the broadcaster not the message originator. 
-- 
Tom Spencer