[EAS] CAP EAS Logging Question

[Harold Price]

At Sage, we do treat FIPS codes as multilevel.

A county code of 000 is taken to mean all counties in that state.

In a filter,

Allegheny County, PA will match an incoming alert that includes the 
specific county, 042003, and it will also match an incoming alert 
with the all of state code 042000.

The intent is that, as a receiving user, you only ever need to 
specify your counties of interest, and you can ignore the "all of 
state" as it takes care of itself.

If an alert is issued to one of your counties, you get it.  If the 
alert is issued to all of a state in which you have a county, you get it.

For that to work, the issuer needs to code the alert properly.

If it is an alert for a particular country, just use that county.

If it is an alert for all of a state (that is, every county in the 
state), the use the "all of state" coding.

If the one county that is going to issue a state wide RMT next week 
wants to test that feature, it can issue a state wide RWT as a 
test.  That should not be the typical case though.  They should not 
issue an RWT for all of state each week.  And once they've done the 
RWT for all of state once, they never need to do it again.  You don't 
want each of the 67 counties In Pennsylvania issuing a state-wide RWT 
each week.

As a user, the only time you want to put in a filter that has "all of 
state" is if you really want to match an alert send to any single 
county or group of counties in that state.  A state-wide relay 
network station might want that.  Almost no one else will.

Harold

At 05:00 PM 9/11/2013, Dave Kline wrote:

>If cap cannot work on a county level, then what is the point of all 
>of this monkeying around we've been doing over the last couple of years?
>Does that mean it would be pointless to issue an weather related EAS 
>alert on anything less than an "ALL STATE" level?