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.
>From: Clint Rowe <address@hidden> >Organization: University of Nebraska-Lincoln >Keywords: 200009131309.e8DD9sb12051 ldm-mcidas LDM PNG pnga2area pqact.conf Clint, >Here's a copy of our quote. Thanks, this might be useful. >Since you've been working so hard on this, how about sending me the pqact >entries you've set up (I'm being lazy -- I haven't bothered to try to get >the png images yet. But I have updated software and grabbed those >derived products starting right when they came out!) Here is a "one-for-one" replacement pqact.conf pattern for users that file their images in the "McIDAS" manner: use of ROUTE.SYS to name the output AREA files: MCIDAS ^pnga2area Q. (..) (.*) (.*) (.*) (.*) (........) (....) PIPE -close pnga2area -a /usr/local/ldm/etc/SATANNOT -b /usr/local/ldm/etc/SATBAND -d /var/data/mcidas -r \1,\2 If you have McIDAS-X installed in /home/mcidas, you can eliminate the specifications of the '-a' and '-b' flags. You will, of course, have to change the output data directory to match your system. If you want to file your image products directly (for GEMPAK/GARP/NMAP) I can send out example pqact.conf entries that will do that. Thanks for the quote! Tom