[EAS] ALL state FIPS CODE
Dave Turnmire
eassbelist at cableone.net
Mon Sep 29 12:24:21 CDT 2014
Idaho has routinely used the All Idaho code for years and I have never
heard of a problem, with the exception of the ambiguity that Sean
mentioned. Until such time as their is standardization on that matter,
it is a fairly easy issue to work around as it only affects how
broadcasters configure their decoders. It would be nice if the various
vendors explicitly addressed this issue in their documentation, but that
doesn't appear to be the case. So... it is up to us "old hands" to
mentor people new to EAS regarding whether they need to include the "All
State" code in their particular decoder's configuration or not.
Last I knew, you didn't need to on a SAGE ENDEC and DID need to on the
Monroe products. Those are the two I have the most experience with. My
impression, however, is that the SAGE is the oddity and that most or all
of the rest of the vendors require an explicit match. The SAGE approach
always made more sense to me, but apparently not to others... :-)
It should be noted, however, that it would seem the same question would
rise for the "national code" as has occurred for the "all state" code.
So we probably should get this resolved once and for all...
Dave
More information about the EAS
mailing list