NMDA & NTDA Readouts

The readouts for the NMDA & NTDA are one of the biggest improvements for these products. It adds the objective analysis I would want out of these products with users ability to (1) pull them up at will thus reducing screen real estate and (2) has them linked to each individual storm/icon so I can easily relate the objective analysis to the storm under investigation. The 1 advantage of a table format highlighting the most intense circulations are solved with color attributes of the icons, which is better in my mind because it relates the severity of the rotational signatures to climatology versus a ranking of storms on any given day.

The drawback of the readouts is that size and the massive amount of information thrown out at once, there is so much in these tables that it’s hard to point out any one thing to follow. In my opinion, each readout should be cut in half to optimize the deluge of information. In addition, the value behind multiple fields should be combined where possible and some organization can help cut down on redundancies between titles thus reducing the amount of space in the product descriptions. For example:

AzShear Max
          Strength: 19.4 * 10(-3)/s || <Med> || ↘
          Diameter: 2.0 km || <Med> || ↗
          Height/Tilt: 2.2km / 1.8 deg
Avg Bottom 3 Tilts
          AzShear: 18.2 * 10(-3)/s || <Med> || ↗
          Diameter: 2.7 km || <Med> || ➝
Meso Depth (bottom – top)
          Distance: 2.7 km (1.7 -4.4 km)
          Tilts: 5 (0.5 – 2.4 deg)
Storm Attributes
          ID (lat/lon): 19 (14.01 / -73.46)
          Speed/Dir: 40.6 kts @ 158
          Duration: 31.2 min (since 18:43Z)

…etc. While I wouldn’t advocate for all these fields, this could be a more organized way to organized the information in the NMDA, that would allow user to find information faster. If awips can handle Unicode, special arrows could also be used as symbols.

KENX @ 19:12Z

#ProtectAnd Dissipate