One big improvement will be the ability to layer imagery products. N-AWIPS only allows one image layer at a time. In AWIPS-2 you can load as many layers as you want (hmmm... so how many layers does it take to crash an AWIPS-2 system? I'm sure our forecasters will find out!). Several WFO forecaster participants showed one way to take advantage of this:
![]() |
| 20160818 1700 UTC Visible satellite imagery with IR tops below -30C; WPC surface analysis and METARs overlaid |
This type of flexibility shows the potential of the display system for aviation weather. Additional aviation products can be used instead, such as cloud bases.
![]() |
| 20160818 1430 UTC Visible satellite imagery and Cloud Base Heights |
To WFO forecasters this is old hat but National Center forecasters are just discovering all these functionalities.
However, there is one functionality that could take this potential one step further and benefit all forecasters. It is the idea of assimilating satellite data into GFE. Grid editing across the NWS is a tricky process as we have seen this week. There is an overwhelming plethora of grids and models to pick through and utilize, but often times a dose of reality is needed as a basis for this process. It has been suggested that one way to do this is to use observations like satellite as a starting point. In the AWT we have taken a baby step in that direction by displaying some satellite datasets in GFE.
![]() |
| Sample of Cloud Base Heights in GFE |
This is where GFE would come in. The goal? Creating smart tools to pull out certain satellite data in various environments and situations. For example, radiation fog along the east coast. The behavior of satellite data and cloud properties could be leveraged as a first guess or perhaps even integrated into the initialization of the model guidance within GFE. Some WFO offices have toyed with this in the past, but the concept -at least at the National Centers- is just being realized.
In future evaluations of the grid editing process at the AWT, we will be exploring this functionality in much more detail!



No comments:
Post a Comment