Hi Blair,
We have this line:
NEXRAD3 ^SDUS[2345678]. ....
([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N[0-3CVET][QVRSULTPXCKHM]|RSL)(...)
STDIOFILE -overwrite -close
/home/ldm/nexrad/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3.nids
which writes the files out as:
/home/ldm/nexrad/<station>/<product>/<product>_YYYYMMDD_HHMM.nids
for the products that are selected by the regexp before the STDIOFILE
expression.
On 3/17/14 12:23 PM, Blair Trosper wrote:
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 mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
