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.
Hi Ziv, Sorry for the slow replies. We have been preparing for the AMS Annual Meeting that will be held next week in New Orleans, and so have been quite busy lately... re: > Another point of confusion: in the pqact.radars file you shared with me, in > the NEXRAD2 section instead of starting with "NEXRAD2" (as you wrote in > email from yesterday) the commands start with "CRAFT". Is that something I > should change? This is my fault. The example pqact.radars file that I provided originally used CRAFT (the historic name for the NEXRAD2 feed). I did a quick edit after copying the file to our FTP area and thought that I had change all occurrences of CRAFT to NEXRAD2. I recommend that you change all occurrences of CRAFT to NEXRAD2, but this is not actually necessary for things to work as they both indicate the same feedtype. re: > Also, does it matter that there are NEXRAD3 commands when I am not getting > that data product (i.e. should I comment them out). No, it does not matter that there are actions that won't be matched to the feed(s)+ProductIDs that will be processed. The overhead for keeping the additional actions in the file is negligible, so there is no need to to worry about them. re: > Thanks! No worries. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: BJM-438879 Department: Support IDD Priority: Normal Status: Closed