[EAS] CAP EAS Geography Problem

[Al Kenyon]

Adrienne,

I don't see significant difficulties resolving the problem that you have
described.

1.) The FEMA IPAWS OPEN aggregator can obviously handle CAP EAS messages for
multiple states as that is how the weekly RWT messages are processed.

2.) If KKUD, licensed to Somewhereville, CA, is part of Nevada EAS plan then
they should configure the filters in their CAP EAS device to accept messages
specifying NV and the correct NV counties along with any CA counties that
may be in their service and EAS Operational Area. CAP EAS devices that I
have personally programmed were able to accept more than one state code in
their filter set.

3.) If a Nevada official is authorized by the State of California to
originate alerts for adjacent areas in CA then the areas specified may be
added to their origination certificate.  (Here I am simplifying the process,
however the results are what are important to the EAS community.) This was
an early design feature of OPEN to allow adjacent jurisdictions to back each
other in alerting in a similar fashion to mutual aid agreement.

Given the above, am I missing something else?

Al Kenyon