[EAS] The coming evolution of CAP-EAS

Gary Timm gteas at sbcglobal.net
Sat Nov 3 19:20:08 CDT 2012


Great discussion over the last couple days.
I think we're finally reaching a consensus:
IPAWS CAP EAS is the doorbell.
IPAWS CAP non-EAS is for important follow-on information.
The issue I see is that there is no accepted way for EM to get IPAWS CAP non-EAS messages to broadcasters.  The only IPAWS CAP messages that appear on the EAS Atom Feed are those fully coded for EAS and are thus meant for immediate broadcast.
How do we provide EMs with a way to send us non-EAS maps, etc. when our current EAS/CAP units only pull down EAS-coded messages?
One way as Richard points out below is the next generation of smarter appliances.
One other option I see is a nationwide agreement that something like the ADR Administrative Message shall be for non-immediate-broadcast EAS messages.  These would be the "non-EAS" messages in essence, but still need to carry a valid EAS code to get through the system.
I'm not sure what the avenue would be to enshrine ADR or some other code for this purpose, but do others have alternate ideas to get CAP messages and their enhanced content to broadcasters without setting off the EAS bells and whistles?
 
Another idea is that FEMA does provide a second CAP message feed for PUBLIC alerts (meant for use by 3rd parties like Google to relay the alerts to the public, not for the public itself to access).  This feed has all IPAWS CAP messages on it, not just EAS.  I think I heard on a webinar that those PUBLIC messages are actually available on the EAS Atom feed but our units don't access them.  Maybe one of the vendors can speak to that.  That PUBLIC CAP message category might be another way for EM to issue non-EAS messages we could access.
Maybe the vendor and FEMA eyes on the list can lend an opinion on that.
I suppose EAS/CAP units would violate FCC certification if they pulled down anything other than EAS messages?  And how would they decide which PUBLIC messages to pull down?  Still some issues to work out with that idea as well.
 
Other ideas?
 
Gary Timm

--- On Sat, 11/3/12, Richard_Rudman <rar.bwwg at gmail.com> wrote:

>From: Richard_Rudman <rar.bwwg at gmail.com>

>__________________________________________________________
>Recent posts on this and other lists prompted me to write the following:

>Looking far down the road, my EAS/CAP wish list starts off with CAP-aware end user warning appliances that can receive fully enabled CAP messages without the current need to always fully interrupt main audio or video on-air program streams. Such "appliances" might be part of the next generation of radio RDS, radio HD, and cable video display technology. How about CAP-aware car and portable radio receivers that can store or display information?

>Support information such as Frank suggests could not only be delivered to such devices, but this information could trigger user-programmed alarms at 3 AM, activate external devices to warn people with hearing or sight impairment, and eventually link to language translators specially written and  "trained" for warning messages.

>Richard Rudman
>Core BWWG Member
>Vice Chair, CA SECC



More information about the EAS mailing list