20010110: 20010110: papagayo LDM filing of NOAAPORT NEXRAD Level III products (cont.)

Clint, 
There is no problem with creating different levels of "platform" directories 
under $RAD for GEMPAK....same as the different GOES directories under sat.  
Same might be useful for separating the NMC3 floaters from the NEXRAD feed
sites you always request, etc.

Chiz


>From: Clint Rowe <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200101101655.f0AGtro15454

>--Sute_of_Bloodhounds_905_000
>Content-Type: TEXT/plain; charset=us-ascii
>Content-MD5: OBcLD9fkgrZpcx6IkKsJJA==
>
>Tom,
>
>>>I may try to figure out a better way of filing it (probably change
>>>the NIDS part of the gempak directory structure) so they're all together, bu
> t
>>>separate from the stations for which we are getting all the available
>>>products.
>>
>>What you have looks good to me, and it looks like the "typical" setup for
>>GEMPAK users.  Why muck with it?
>
>The selection widget on nsat, for example, means you have to wade through
>all the stations to find those few local stations for which we will have 
>more data (i.e., N0S, N0V, NCR, NTP, NVL).  I thought I could put all the base
>  
>reflectivities under something like $GEMDATA/nexrad/RADAR so that they
>would appear as a separate button at the top of the selection widget.
>
>
>>>Thanks again for making that change and, especially, for taking the time to 
>>>do the cleanup!
>>
>>No problem.  I trust you got my note this morning about needing to address
>>scouring for the NEXRAD data.
>
>Yes, I did.  Thanks for catching that for me.  I added the needed cron entry.
>But I do have another question.  Are you saying that my request should key 
>on the pil?  My entry is based on what Russ told Gilbert (see attached).  I
>just looked at what Russ wrote for the web page and see that he does show it
>keying on the pil.  I'll make the change!
>
>>
>>Also, the way you are requesting certain stations:
>>
>>request NEXRAD  "^SDUS5. (KOAX|KUEX|KLNX|KFSD|KTWX|KGLD|KCYS)"  
>stokes.metr.ou.edu
>>
>>makes me wonder if this is what you really want.  Do you want to receive
>>all of the reports from the stations OAX, UEX, LNX, FSD, TWX, GLD, and CYS
>>or do you want all of the stations issued from the centers KOAX, KUEX, KLNX,
>>KFSD, KTWX, KGLD, and KCYS?
>
>
>====================================================================
>Clinton M. Rowe
>Associate Professor 
>Meteorology/Climatology Program                  phone:(402)472-1946
>Department of Geosciences                          fax:(402)472-4917
>University of Nebraska-Lincoln                        address@hidden
>
>
>--Sute_of_Bloodhounds_905_000
>Content-Type: TEXT/plain; name=saving_radar; charset=us-ascii; x-unix-mode=066
> 4
>Content-Description: saving_radar
>Content-MD5: CKP+3Xq98yKU51gFiZa/FA==
>
>
>X-PH: V4.4@newcso
>To: Gilbert Sebenste <address@hidden>
>Cc: address@hidden, address@hidden
>Subject: Re: Data Available on NEXRAD feed 
>Date: Fri, 29 Dec 2000 11:22:37 -0700
>From: Russ Rew <address@hidden>
>
>Hi Gilbert,
>
>> Hurray! Now, one question. With the latest version of the LDM (5.1.3),
>> are the rules still the same for requesting data vs. other versions?
>> For instance, what if I only want to get all products from, say, KARX,
>> KLOT, KDVN, KILX, KARX and KLSX? *In addition* to that, I want to get all
>> BREF1 products from every site. Can I use multiple request lines to the
>> upstream site to grab these?
>
>Yes, that works fine in earlier versions also.  For example, to do what you
>want, you could include these two lines in your ldmd.conf:
>
>request NEXRAD "^SDUS5. (KARX|KLOT|KDVN|KILX|KLSX)" your.nexrad.site
>request NEXRAD "/pN0R" your.nexrad.site
>
>--Russ
>
>
>--Sute_of_Bloodhounds_905_000--
>