[EAS] CAP EAS Logging Question

[Darryl Parker]

Brian,

FIPS codes as used in EAS (and CAP) are specific and unique. FIPS codes are not grouped and do not exhibit sub-group characteristics. A FIPS code for a county (or city or parish or census district) is unique. A FIPS code for an entire state or territory is also unique and can be recognized as having the format of PSS000, where P is the portion code, and SS is the state or territory 2-digit designator. A list can be found at 11.31(c).

For example, for TFT EAS911 autoforwarding and for Geocodes for Omaha, Nebraska, the FIPS (or Geocode) for Douglas County NE (031055) and All Nebraska (031000) would need to appear in the autoforwarding and Geocode list.

Another way to think of it is to consider yourself an emergency manager and ask the question: What area is affected by this message? Is it all of the state (city or parish or census district or territory) or only a selected county or counties?

Regards,

Darryl E. Parker
TFT, Inc.

-----Original Message-----

My Point Exactly!

I do not know if this issue is manufacturer specific or not.

Would like to know the skinny on this, if the manufacturers would chime 
in please...

Thanks,
Brian

On 9/11/2013 2:00 PM, 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?
> If I'm not mistaken, our LECC is considering CAP-able gear to generate alerts locally.
>
> Dave
> ************************************************
> Dave Kline   UNO-TV / KVNO
> University of Nebraska at Omaha
> 6001 Dodge St. Omaha, NE  68182  CPACS 200