NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
We're pulling the firehose feed of NEXRAD3 on one of our servers to feed/relay to several people, but I'd also like to store some of them on disk. However, going by the documentation, I can't seem to get pqact.conf set up correctly to write the data to a file in a similar manner to how we "stash" NEXRAD2 scans. Can someone help me translate the NEXRAD3 equivalent of this (from our pqact.conf file): # Data blocks are received...but we don't have all the parts. > NEXRAD2 ^L2-BZIP2/(....)/([0-9]{8})([0-9]{4})[0-9]{2}/([0-9]{1,4}).*/[SI] > FILE nexrad2/\1/\1_\2-\3.nexrad2 > # The last piece of the scan is received. We now have the whole scan. > NEXRAD2 ^L2-BZIP2/(....)/([0-9]{8})([0-9]{4})[0-9]{2}/([0-9]{1,4}).*/E > FILE -close nexrad2/\1/\1_\2-\3.nexrad2 This outputs in this format: ~/data/nexrad2/KXXX/KXXX_YYYYMMDD_HHMM.nexrad2 (We have a folder for each site and then files inside that folder with the Ymd_HM date format (and just an arbitrary extension.) Any help would be greatly appreciated...the documentation appears to be sort of thin and out of date on this topic. -- ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ Blair Trosper Weather Data / Updraft Networks NOC: 469-844-5440 ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙
ldm-users
archives: