[EAS] Overlap/monitoring issue

[Paul Campbell]

This subject was discussed at length with my local NWS guru. My suggestion was to make all transmissions that involve Surry County identical coming out of both of his NWS transmitters. So for example, if a TOR was rolling through that affected Chesterfield (not one of mine), Henrico (also not one of mine), Surry (both of ours), and Isle of Wight (mine), both alerts on the two NWS transmitters would be encoded TOR for Chesterfield, Henrico, Surry and Isle of Wight. Sure, WGH-FM doesn't serve Chesterfield or Henrico, nor does WRVA serve Isle of Wight, but the alert that got forwarded from WRVA while I was in the middle of forwarding my TOR would simply be treated as a duplicate. Easier said than done unfortunately, as I was told since the NWS system is automated for TOR's and the like, they wouldn't have time to make sure this duplication happened, which I totally understand...they've got enough happening during lousy weather to worry about my problem here. My next move was to!
  contact Sage and ask if a filter could be created based on Input, but was told no (this has already been mentioned, but I'm just adding my $.02 at this point). 

I don't automatically forward TOR's. I've got my hold delay set to one minute to try to give my folks at least a slight chance to air it seamlessly. I thought about possibly increasing the hold time to three minutes, the idea being that this would allow enough time for any new alerts with my overlap county to pour in and overwrite anything I was about to air, but these alerts are going to come in whenever they come in, so neither holding the TOR longer or even airing it immediately would really prevent this. (Plus, holding a TOR longer is a pretty sh**ty  thing to do.) Wow, long reply. Thanks. (I tried posting this earlier, but it got poo-poo'd because I didn't snip it, sorry!)