[EAS] CAP Polling Interval Questions

[Alex Hartman]

Up here in MN, 1 minute is all it takes sometimes for a tornado to
drop out of the sky, but predicting the weather up here (or anywhere
for that matter) is impossible. But 1m would i think be a good
interval, 30s would be a LOT of traffic on the server loads. 5m is far
too long, a lot can happen in 5 minutes.

But i have a question about this "federal aggregator" thing... first
i've heard of such a thing. Why is it even needed? For a tornado
warning, i'd sure as heck hope the alert is coming from my local NWS
office for activation, not the feds! If anything, it should be
reversed, the state servers should poll the fed server for messages,
not the other way around. If the whole CAP system is dependent upon a
federal "centralized" server, whomever designed the system should be
shot.

--
Alex Hartman
KVSC Radio

On Tue, May 10, 2011 at 11:47 PM, Richard_Rudman <rar01 at mac.com> wrote:
> I have a question for Al:
>
> How much time will it take for a CAP message from a state input to get to the federal aggregator server and prepare it for "polling"?
>
> As far an answer to one of Al's questions:
>
> If we are talking about tornado or other highly time-critical warnings, I would submit that a five minute polling interval is too long. It would be interesting to see how people feel about this after the recent spate of serious tornadoes. For tornado-prone areas, maybe CAP-EAS boxes in those areas should poll every minute -- or more?
>
> Richard Rudman