[EAS] The words we use

[Mike McCarthy]

Art is right. The default configuration for each WFO sees polygons end at
their CWA county lines. They do not overlap...and never have.

However, each WFO backs-up other WFO's around them at varying extents
depending on radar coverage. And when that happens, that covering WFO
assumes warning responsibility outside their primary CWA. However, those
"foreign county" warnings are purposely different products from the
issuing WFO and remain under the "foreign county's" home WFO's identifier
to maintain consistency in distribution channels.

As the system currently operates, the product hazard polygon is first
drawn and duration defined, then the counties included are identified.
This is where the message flooding comes into play. Most forecasters stop
there and simply send the warning without considering the balance of the
county's exposure to the same event. Some of this is policy on expected
impact within the warning duration. Other factors include, but not limited
to working time in a busy WFO when a severe weather event occurs and
they're potentially dealing with any number of threats and hazards.
Particularly in the spring when both warm and cold weather severe hazards
can play out in extremes across a single WFO.

MM

On Tue, September 5, 2017 10:08 am, Dave Kline wrote:
>
> On Sep 4, 2017, at 7:19 PM, Sean Donelan wrote:
>
>> On Mon, 4 Sep 2017, Botterell, Arthur at CalOES wrote:
>> Even between different NOAA/NWS Weather Forecast Offices, polygons
>> almost never cross into the jurisdiction of a different weather