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: Eirh-Yu Hsie <address@hidden> >Organization: CU/CIRES >Keywords: 200101111813.f0BIDHo04324 LDM pqact.conf ldmd.conf Hsie, >Could you send me an example pqact.conf entry for save GINI data (diretory >structure, feed type ... etc) in UNIDATA. Here goes the various pieces: -- ldmd.conf entry to request GINI imagery -- request NIMAGE ".*" motherlode.ucar.edu -- pqact.conf entry to decode GINI imagery -- # NOAAPORT GINI Images NIMAGE ^sat/ch[0-9]/.*/(.*)/([12][0-9])([0-9][0-9])([01][0-9])([0-3][0-9]) ([0-2][0-9])([0-5][0-9])/(.*)/(.*km)/ PIPE -close decoders/readpng -n -l logs/png.log /data/pub/raw/gini/\8/\9/\1/\1_\2\3\4\5_\6\7 (Be careful to put tabs where appropriate and not accidentally clip these lines.) You can see that you need the 'readpng' routine to decode (unpng) the images. Assuming that the machine that is running your LDM is a Solaris SPARC box, I put a binary of readpng that is running on motherlode: SunOS motherlode.ucar.edu 5.8 Generic sun4u sparc SUNW,Ultra-80 in the pub/ldm directory of anonymous FTP on our FTP server, ftp.unidata.ucar.edu for you to grab. I also put a C shell script that can be used to scour the files, prune_gini.csh, in the same directory. You must copy readpng and prune_gini.csh to a directory in the PATH of the user running your LDM. Both of these files need to be made executable (chmod +x readpng prune_gini.csh). You must edit prune_gini.csh and set PATH and areadir to match your setup. PATH must contain the directory where you put prune_gini.csh. areadir must be the directory path under which you store your GINI iamges. We can talk about this setup tomorrow if you like. Also, I verified that the BLIZZARD dataset is now setup correctly for ADDE access. Thanks! Tom