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 Bongchul, re: > I think that I am randomly missing an end piece for some timestamps > and the pieces of a Level II are not assembled. > Have you ever seen this? Yes, we have seen situations like this in the past. I can not say that we are seeing this same thing now for Iowa radars since we do not monitor the NEXRAD2 data that carefully. As far as your observation "and the pieces of a Level II are not assembled", what process are you using to reassemble pieces back into a full volume scan? I ask because we moved away from a Perl script that we used for years because we found that it was not thorough enough to piece together volume scans when there were some pieces missing, mainly the beginning or ending pieces. The procedure we went to here to reassemble volume scans from NEXRAD2 pieces is a Python script named l2assemble.py, and this script can be found in the ldm-alchemy repository of the Unidata part of github: https://github.com/Unidata/ldm-alchemy The pattern-action file action we use to run l2assemble.py is: # # --------------------------------- # - NEXRAD Level II Radar WSR-88D - # --------------------------------- # NEXRAD2 ^L2-BZIP2/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9][0-9][0-9])/([0-9]*)/[0-9]*/(S|I|E) PIPE -metadata etc/TDS/ldm-alchemy/l2assemble.py -g -t 960 -d /data/ldm/pub/native/radar/level2 -f raw --threads 20 NB: I cut and pasted this action out of an LDM pattern-action file, so the places where tabs are needed instead of spaces have been lost. If you decide to use this script and corresponding action, you will need to make sure that the syntax of the action is correct. 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: LQF-497474 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.