[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #VDF-558272]: Problem getting the NEXRAD

Hi Michel,

> 1-   All our problems ended all of a suddent in the afternoon of june 20th 
> (missing
> exact time).

Very good.  Just so you know, nothing was changed on our end.

> 2-   I activated the  "rtstats" a few minutes ago... I think it was commented
> because this ldm application was used with the noaaport software a while ago
> So I put it back on.

Excellent!  I suspect that the name of your machine is noaaport3.cmc.ec.gc.ca
since I now see that in the list of machines reporting real-time stats
in the ca.gc.ec.cmc block in:


> 3-   We are getting NEXRAD level III products...

Yes, I can see that now.

> We are newly interested in the NEXRAD level II...

OK, you should already be ALLOWed for the NEXRAD2 feed.

> I had a few request for getting them
> Do I need a special setup to get them ...?
> I think I can see them... :   Is this enough !?

Yes, this is enough.  I am glad that you know how to use the LDM 'notifyme'
utility to determine if an upstream host is configured to ALLOW feed
REQUESTs from you!

> notifyme -vl- -f NEXRAD2 -h idd.unidata.ucar.edu
> Jun 22 18:59:59 notifyme[18490] NOTE: Starting Up: idd.unidata.ucar.edu: 
> 20120622185959.668 TS_ENDT {{NEXRAD2,  ".*"}}
> Jun 22 18:59:59 notifyme[18490] NOTE: LDM-5 desired product-class: 
> 20120622185959.668 TS_ENDT {{NEXRAD2,  ".*"}}
> Jun 22 18:59:59 notifyme[18490] INFO: Resolving idd.unidata.ucar.edu to 
> took 0.002789 seconds
> Jun 22 18:59:59 notifyme[18490] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
> Jun 22 19:00:00 notifyme[18490] INFO:    17575 20120622185959.904 NEXRAD2 
> 612068  L2-BZIP2/KCBW/20120622185536/612/68/I/V03/0
> Jun 22 19:00:00 notifyme[18490] INFO:    46688 20120622185959.766 NEXRAD2 
> 888025  L2-BZIP2/KMKX/20120622185751/888/25/I/V06/0
> Jun 22 19:00:01 notifyme[18490] INFO:    45998 20120622190000.215 NEXRAD2 
> 426039  L2-BZIP2/KDTX/20120622185816/426/39/I/V03/0
> Jun 22 19:00:01 notifyme[18490] INFO:    18624 20120622190015.086 NEXRAD2 
> 426001  L2-BZIP2/KMSX/20120622190012/426/1/S/V03/0
> Jun 22 19:00:01 notifyme[18490] INFO:    42219 20120622190000.134 NEXRAD2 
> 815011  L2-BZIP2/KDOX/20120622185903/815/11/I/V07/0
> Jun 22 19:00:01 notifyme[18490] INFO:    64227 20120622190000.129 NEXRAD2 
> 865013  L2-BZIP2/KTLH/20120622185918/865/13/I/V03/0
> Jun 22 19:00:01 notifyme[18490] INFO:    39882 20120622185959.943 NEXRAD2 
> 318033  L2-BZIP2/KCRP/20120622185620/318/33/I/V03/0
> Jun 22 19:00:01 notifyme[18490] INFO:    43587 20120622190000.346 NEXRAD2 
> 659015  L2-BZIP2/KFCX/20120622185920/659/15/I/V03/0
> So I guess if I do this :
> ldmd.conf
> Request NEXRAD2 ".*" idd.unidata.ucar.edu


> And
> Pqact.conf
> ^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])
> FILE    data/raw/level2/\1/\1_\2_\3
> I would get them ... right !?

You will get the products, yes.  You may have some difficulties in using them, 
The reason for this is that the full volume scans are split into lots of pieces 
(by the
U.S. National Weather Service, not by us or the LDM) which are sent 
individually, AND
there is no guarantee that the pieces will be received in order.  One must 
the pieces into get a viable, full volume scan.

In case they might be useful to you, I have attached the pattern-action file and
associated Perl script that we use for our THREDDS processing of NEXRAD Level 2
data.  The files are:

pqact.threddsradar - the pattern action file we use for NEXRAD2 and NEXRAD3 
                     for use in THREDDS

hhmmssRadarII.pl   - the Perl script that is run from pqact.threddsradar to 
                     the NEXRAD2 pieces

We put 'hhmmssRadarII.pl' in the ~ldm/util directory (and make sure that this 
is in the PATH of the user running the LDM) and pqact.threddsradar in the 
directory.  The actions in pqact.threddsradar are executed by the following line
in ~ldm/etc/ldmd.conf:

# THREDDS radar processing
exec    "pqact -f NEXRAD2|NEXRAD3 etc/pqact.threddsradar"

Please let us know if you have questions about either of these files.

> Thanks for your help

No worries.


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: VDF-558272
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.