This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Daryl (and Kevin), 1) The Unidata release can be downloaded as source or binary from our web site. I would have to double check in linking against the NCEP distribution as to the specific error (you may have a problem with a different IMGDEF.CMN). Here is the particulars I sent to Gregg Groshans: ************************************************************************* Gregg, You can get the distribution via the web. If you are running Linux, then the easiest way would be to grab the binary and take the programs from bin/linux. Also, you will need the $GEMTBL/unidata directory for nex2image to place the appropriate platformID and calibration numbers in the GINI header (Also grab the entries from $GEMTBL/sat/imgtype.tbl and the color enhancements from $GEMTBL/luts mentioned in the imgtype.tbl file). With NCEP's plotting, you won't get a calibration bar for the images. Our distribution has additional code to create image calibration bars. ******************************************************************************* As for 2), A composite of radial velocity is not really meaningful. It is only the radial component. The tangential wind is not provided. This is not a dual-doppler analysis - which can be done with the level II data-- NIDS images are just data bins. You could estimate U & V components along the bisection of the overlap regeion, but otherwise would be indeterminant (note that "away" values from one radar would be "toward" values in an adjacent image. Since I have to create my status reports for user and policy committees this week, your comments are welcomed and well timed. Steve Chiswell >From: Daryl Herzmann <address@hidden> >Organization: UCAR/Unidata >Keywords: 200309231418.h8NEIek1011225 >Hiya UNIDATA! > >I have gotten a lot of positive feedback on your nex2img program and have >accumulated a few questions and suggestions... > >1. I have gotten a few requests from folks in the NWS/NOAA that are > having problems compiling nex2img with their NCEP(?) supplied > GEMPAK environment. Kevin Slover (cc'd) wrote to me with issues > compiling against version 'L'. He would like to try UNIDATA's > release of GEMPAK or find out how to get nex2img into their > version. Any insights here? > >2. Does nex2img 'do the right thing' when it comes to velocity > products? I realize compositing them is a beast, but most folks > just want to generate a single site geotiff. Looking at the > nex2gini.tbl, I notice a lack of velocity products. Can I > just add them in there? > >I currently have 5-10 hosts routinely downloading the nationwide composite >I generate every 5 minutes. The response has been very good. Thanks for >creating the nex2img program to make this possible. > >Thanks, > Daryl > >-- >/** > * Daryl Herzmann (address@hidden) > * Program Assistant -- Iowa Environmental Mesonet > * http://mesonet.agron.iastate.edu > */ > >