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

[IDD #TAQ-497422]: Radar level 3 distribution

Hi Wilson,

re:
> We at the National Weather Service Telecommunication Gateway is looking
> into redesigning how the radar level 3 data could be disseminated.  With
> the turn on of the High Resolution data this Spring, some customers are
> experiencing bandwidth issues. The Dual Polarization data coming this
> winter will certainly cause even more bandwidth issues.

Yup, more data all the time :-)

re:
> Currently we package all data into tarfiles (wsr88...) and customers
> must take all data.   We are looking into making each radar product
> available as a separate file so customers can choose what they want.

That is the way we distribute Level III files contained in the NOAAPort SBN.
Breaking the offerings into individual products allows the end user to
pick and choose what s/he really wants.

re:
> Each file likely will be named SDUS.. file.

Our convention for naming products is easily seen by running the LDM
'notifyme' utility.  For instance:

<as 'ldm'>
notifyme -vl- -f NEXRAD3 -h idd.cise-nsf.gov
Jul 20 22:27:35 notifyme[2484] NOTE: Starting Up: idd.cise-nsf.gov: 
20100720222735.972 TS_ENDT {{NEXRAD3,  ".*"}}
Jul 20 22:27:35 notifyme[2484] NOTE: LDM-5 desired product-class: 
20100720222735.972 TS_ENDT {{NEXRAD3,  ".*"}}
Jul 20 22:27:35 notifyme[2484] INFO: Resolving idd.cise-nsf.gov to 
192.12.209.62 took 0.000722 seconds
Jul 20 22:27:36 notifyme[2484] NOTE: NOTIFYME(idd.cise-nsf.gov): OK
Jul 20 22:27:37 notifyme[2484] INFO:    14315 20100720222736.059 NEXRAD3 
13100109  SDUS52 KILM 202222 /pDVLLTX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:    34217 20100720222736.059 NEXRAD3 
13100110  SDUS24 KLIX 202224 /pN2ULIX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:    24557 20100720222736.665 NEXRAD3 
13100111  SDUS21 KGYX 202225 /pNBUGYX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:     2284 20100720222736.665 NEXRAD3 
13100112  SDUS36 KLOX 202219 /pN1PVTX
Jul 20 22:27:37 notifyme[2484] INFO:     2289 20100720222736.665 NEXRAD3 
13100113  SDUS56 KLOX 202219 /pNTPVTX
Jul 20 22:27:37 notifyme[2484] INFO:    32307 20100720222736.666 NEXRAD3 
13100114  SDUS25 KSLC 202225 /pNBUMTX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:      995 20100720222736.666 NEXRAD3 
13100115  SDUS56 KLOX 202219 /pDSPVTX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:      165 20100720222736.667 NEXRAD3 
13100116  SDUS32 KILM 202222 /pNMDLTX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:    11524 20100720222736.667 NEXRAD3 
13100117  SDUS56 KLOX 202219 /pDHRVTX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:      165 20100720222736.668 NEXRAD3 
13100118  SDUS35 KGJT 202223 /pNMDGJX !nids/
Jul 20 22:27:37 notifyme[2484] INFO:    25217 20100720222736.668 NEXRAD3 
13100119  SDUS55 KGJT 202223 /pNCRGJX
Jul 20 22:27:38 notifyme[2484] INFO:    11885 20100720222736.669 NEXRAD3 
13100120  SDUS24 KOHX 202224 /pN2QOHX !nids/
Jul 20 22:27:38 notifyme[2484] INFO:     7316 20100720222736.669 NEXRAD3 
13100121  SDUS51 KCLE 202222 /pNCRCLE
Jul 20 22:27:38 notifyme[2484] INFO:     2193 20100720222736.669 NEXRAD3 
13100122  SDUS24 KOHX 202224 /pN2ROHX
Jul 20 22:27:38 notifyme[2484] INFO:    13238 20100720222736.670 NEXRAD3 
13100123  SDUS52 KFFC 202226 /pTR0ATL
^C

As you can see, the Product IDs we use contain the WMO ID (e.g., SDUS35, 
SDUS55, etc.), the
date and time (e.g., 202223 -> day 20, time 2223Z), _and_ information about 
what the
product is and what station it is for (e.g., NCRGJX -> NCR product for GJX).  
We find
that this kind of granularity is very useful for our users.

re:
> Unidata has been distributing radar level 3 for a long time.  Any good
> suggestions from your experience on what works best?

We would be very happy if you chose to implement a product naming convention
that uses what we have been using for over a decade.  This would make life
easier for users who feed directly from you and from the IDD.

Speaking of access... a long time ago we requested that we be given free
access to the full set of Level III products so that we could deliver them
to the IDD community.  Is there any update on if/when this will be possible?

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: TAQ-497422
Department: Support IDD
Priority: Normal
Status: Closed