[EAS] CAP EAS Geography Problem

[Don Heppelmann]

Adrienne,

Curious if Nevada EM received COG authorization from California through IPAWS authorization process? Perhaps there is a two-step process, one for Nevada and the other for California. In either case, the application(s) defining the types of alerts they intend to issue and the extent of their geographic warning area should have been specified. 

This is raising a very interesting situation for EAS participants near state borders. I hope this gets resolved fairly soon. 
 
Don Heppelmann
MN SECC

-----Original Message-----
From: eas-bounces at radiolists.net [mailto:eas-bounces at radiolists.net] On Behalf Of Adrienne Abbott

Another EAS "hairball".FEMA's aggregator has apparently developed a geography problem and cannot handle CAP EAS messages for multiple states. In other words, if station KKUD is licensed to a California border community which is considered part of the Nevada EAS Operational Area and has offices, studios and transmitter in Nevada, the station won't receive CAP EAS messages because it is licensed to California. If a Nevada official tries to send a CAP EAS message with a FIPs code for any state other than Nevada, the aggregator will kick it back even if the COG originally included California FIPS codes. Has anyone else had this problem? 

 

Adrienne Abbott

Nevada EAS Chair

 

__________________________________________________________
The EAS Forum Discussion List is hosted by the BWWG (Broadcast Warning Working Group). http://eas.radiolists.net Please invite your friends to join our Forum! The sign up is at: http://lists.radiolists.net/mailman/listinfo/eas
___________________________________________________________