Re: [gembud] GEMPAK NAWIPS Functionality

Hi Linda..

A few additional items..

ALL grid diagnostics currently in GEMPAK - deterministic and ensemble - should be considered critical Contour to grid conversion (graph to grid) Tracking tools Ability to read and write to grib files Export of displays to various output formats (gif, ps, etc) Scriptable annotation capabilities (ability to easily annotate an image with text, shapes, or other images) Converstion tools for radar/sat images to grid Dump tools - such as vgftoascii Ability to mark grid points with lables, markers, or literal grid values Ability to easily display geo-referenced data sets like counties, rivers, user generated datasets
Automatic ability of handling missing data stored in grids

PEte

Linda Miller <lmiller@xxxxxxxxxxxxxxxx> Sent by: gembud-bounces@xxxxxxxxxxxxxxxx
09/10/2008 11:57 AM
Subject [gembud] GEMPAK NAWIPS Functionality

All-

Your feedback is solicited!

*GEMPAK NAWIPS Functionality*

Below is information that the Unidata Users Committee has compiled about functionalities that are not currently available, but are desirable in the IDV.

GEMPAK will remain available for the indeterminate future, but at some point, sites will have to migrate from GEMPAK to another package. It is important that the community identify critical functionalities of the current GEMPAK software that must be retained (or enhanced) in future incarnations of AWIPS-II, IDV, or other packages. Which capabilities could be handled by IDV, and which would not make sense to roll into IDV? Which functionalities are most critical to the user community?

The following features are available in the Unidata NAWIPS suite. This includes a set of programs that utilize data in GEMPAK format, and in most cases use GEMPAK programs to manipulate and display data. These programs include NMAP2, NSHARP, GARP, and GEMPAK.

This list is ****not** in order of priority. If you have thoughts on how to rank this list, or have additional items, please share them in the NAWIPS Migration forum:

http://www.unidata.ucar.edu/forums/forum.jspa?forumID=21

1) Objective analysis of raw observations to form evenly spaced grids (In my view, this need has been mitigated by modern DA systems and reanalyses to a large extent)

2) Ability to link object libraries to data manipulation programs written in FORTRAN or other languages. This allows efficient storage and easy i/o for diagnostic computations.

3) Ability to draw manual analyses (contours) using mouse, do shading, annotate with text, etc. (currently utilized in NMAP2, used by National Centers and synoptic classes)

4) Ability to save a manual analysis in gridded digital form (available in NMAP2)

5) Ability to construct meteorograms for surface station data or other data sources

6) Display and contouring of observed sounding cross sections

7) Replace trajectory capability (GPTRAJ) and enhance to allow full 3-D trajectories if possible

8) Easy ability to generate graphics (e.g., for web pages) in Unix/Linux scripts. The ability to write scripts quickly and easily that will allow one to setup web pages so data can be accessed from remote locations where a datafeed is not possible (Sweden, Antarctica, Australia).

9) Ensemble model features (displays and diagnostics)

10) SVG/PS output (publication quality)

11) Additional grid diagnostics

12) Careful checking of map-scale factors and other computations

13) Ability to interpolate between different vertical coordinates. Especially critical is analysis in isentropic coordinates, and ability to interpolate data between isentropic and other coordinate systems.

14) Time matching of data, such as radar overlay with surface obs- set one display as the base time, retrieve other data based on that. Needs to work in bundles

15) Sounding overlays ? ability to plot observed soundings, ACARS soundings, model-forecast soundings, etc.

16) Sounding analysis package, such as currently available in NSHARP, computation of hodographs, stability indices, etc.

17) Need to add the functionality needed to read all data distributed by the IDD locally (e.g., GINI) and identify the "most recent" data files regardless of data type.

18) If it is not there already, be able to set user preferences for radar imagery, satellite imagery, etc., so that one doesn't need to adjust map types, color scales, etc. If this functionality is already built in, then we need to find a better way to communicate to new (and old!) users.

19) NWS text data is also very important as well as soundings. An NWX replacement is needed along with an NSHARP replacement. Display of MOS, raw text obs, forecast discussions, in point-and-click interactive format


20) Ability for quick and easy display and overlay of 2-D model output, raw observations, satellite and radar.

21) Ability to have satellite and radar loops update without manual intervention is critical.

22) Display of Profiler Winds that are more than 24 hours old.

23) Missing Data:

- surface station model data (efficient access through TDS)
- lightning data
- watches/warnings
- ships/buoys


--
Linda Miller - lmiller@xxxxxxxxxxxxxxxx
Community Services, Unidata
University Corporation for Atmospheric Research
P.O. Box 3000
Boulder, CO 80307-3000
303-497-8646 fax: 303-497-8690

_______________________________________________
gembud mailing list
gembud@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/