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.
Chris, I'm cleaning up our files on this topic. I believe we have addressed #1 below. The second part regarding scour is yes, you can use scour to clean out the products you store with png2area....I suppose you've already done that. Once all the satellite products are changed over in the broadcast, you can store the products with names that Gempak likes, so you won't need nsat_links any longet to create human readable directory names for Garp rather than AREAxxxx file names. Steve Chiswell Unidata User Support >From: "C. Vandersip" <address@hidden> >Organization: UCAR/Unidata >Keywords: 200007032358.e63NwbT07967 >Back again with two more questions... > >1. Since these new CIMSS products are producing fields that are other >than brightness temperature, is there any way to get Garp or Nsat to >display a proper scale for the fields (e.g. CAPE, LI, SST values)? Under >the current config, every CIMSS image displayed in Garp/Nsat shows the >standard brightness temp. scale. Judging from what I've seen from the >CIMSS web site images, I know McIDAS does this, and does it well, but I'd >like to know if Garp/Nsat also can do it. I've checked all the archives >and the Garp_defaults file but can't find anything related to this, except >that Garp_defaults allows you to choose among several default temp. and >distance scales. Am I missing something? > >2. Can I use scour.conf to scour the new CIMSS data directories? >Currently, nsat_links does this for the standard AREA files. > >Thanks and Happy Independence Day, > >Chris >