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, re: Level2_KCXX_20210921_2205.ar2v > on the 21st the mentioned product was downloaded from idd.unidata.ucar.edu > or iddb.unidata.ucar.edu and the file downloaded was 6.9 MB. The client > checked out this file on AWS and the file was 3.055 MB. And on another > machine I support (sources radar2ldm.ncep.noaa.gov and > radar3ldm.ncep.noaa.gov) > the file size is 3.6 MB. > > was there an issue? The NEXRAD Level 2 products that one can find on AWS are put there by an LDM that is relaying the same NEXRAD2 datastream that is feeding CMC. Because of this, the most likely explanation for a file that is about twice as large as it "should" be is the action in the user's LDM pattern-action file is set to append products to output files, and the same product was received more than once. To prevent new products being appended to an output file created by a FILE action in an LDM pattern-action file, the '-overwrite' flag should be specified to the FILE action. 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: XYF-604373 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.