WarnGen and Hazard Service Default Polygon Differences and Warning Interoperability - Hazard Services

Purpose:

Tasks:

AT-A-GLANCE:

• What? During the transition from WarnGen to Hazard Services, forecasters may still use WarnGen to issue updates to short-fused hazards. This interoperability only works when a forecaster uses WarnGen to follow up a product issued by Hazard Services using a Severe Weather Statement (SVS). It is not possible to use Hazard Services to SVS a WarnGen product. It is recommended that forecasters issue products using one platform consistently and do not mix SVS'ing events between WarnGen and Hazard Services.

• Polygons There are differences in the default polygon sizes between WarnGen and Hazard Services. Tornado and severe thunderstorm polygons were the same sizes in WarnGen; however in Hazard Services the defaults are narrower for tornado polygons.

This first section summarizes the differences between WarnGen and Hazard Services products.

1. In WarnGen the Tornado Warning and Severe Thunderstorm Warning polygons are the same width at the back of the polygon.
   
   

2.   In Hazard Services those polygons are different sizes by default. The initial polygon size is configurable in the StormTrackTool.py localization.
   1. Tornado Warning polygons in Hazard Services have a back end width of 12 km by default.
   2. Non-tornado warning polygons in Hazard Services have a back end width of 20 km by default.
   3. All polygons have an 8 km padding distance from the end of the track arrow to the front end of the polygon.
   4. All polygons have a 5 km rear extension distance from the tracking dot to the back end of the polygon.
       
   

This second section focuses on issuing a short-fused warning with Hazard Services and following up with an SVS through WarnGen.

1. Make sure you are in AWIPS practice mode. In this exercise we will start with issuing a warning with Hazard Services. In D2D click the Hazard Services short-fuse icon with the H and red tornado. Run through the process of issuing a Severe Thunderstorm Warning (SV.W) through Hazard Services. After issuing the warning keep Hazard Services open and visible on the screen.
   
   

2. Before advancing remember to open up a Text Workstation, then click on the WarnGen icon at the top of D2D to start WarnGen. Notice how when WarnGen starts up, Hazard Services automatically displays “Hazard Services is not Editable” in the Console.
   
   
   We will be following up on the Severe Thunderstorm Warning we just issued with Hazard Services. In the WarnGen product type section, select Severe Weather Statement (SVS). In the collection box there will be options to CON or CAN the SV.W. Select CON to continue the warning.
   
   

3. The options usually presented in WarnGen when continuing a warning should appear after clicking CON. The threat magnitudes and types should carry over from Hazard Services. Fill out the CTAs or any other options for the SVS. Click Create Text to preview the text product and select Send.

4. The thunderstorm warning SVS should have been issued. In the Hazard Services Console you will notice that the User Name for the warning that had an SVS issued through WarnGen has changed. The new user name is Interoperability. This is a handy signal that the product has been issued/modified through WarnGen. Highlight the hazard event that was edited with WarnGen in the Hazard Services Console.

5. The HID will display an announcement that states the hazard was created or modified in WarnGen. Because Hazard Services uses metadata but WarnGen is merely text based, this event cannot be edited any longer through Hazard Services because the metadata no longer exists. Therefore, it is important to stick to one warning platform through the lifecycle of the hazard event if at all possible. Do note that even if your office fully switches to Hazard Services Convective, some of your service backup offices may still be using WarnGen to issue products. So being familiar with interoperability is important.
   
   

Congratulations, you've learned about the WarnGen and Hazard Services interoperability and limitations!