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

20020305: hosting ADDE access to Unidata NEXRAD composite imagery (cont.)



>From: "Thomas L. Mote" <address@hidden>
>Organization: University of Georgia
>Keywords: 200203051400.g25E0BK05321 McIDAS ADDE NEXRAD composite

Tom,

>I think I have all of this. I would appreciate any feedback you can 
>give on the ldmConnect if/when you get a chance.

OK, I will touch base with Robb Kambic about the ldmConnect things
tomorrow if he is in.

>I have also added the 
>crontab entries to do ldm-mcidas and ldm log rotation as you suggested. 

Good, I think that this was needed.

>Finally, you mentioned that I might want to change the location where 
>these files are saved, and gave me the procedure for changing these 
>file locations. You indicated I might want to do this to access the 
>data in GEMPAK. I probably wouldn't worry about this right now, but do 
>you know where GEMPAK typically expects these files to reside? Just 
>wondering...

That is hard to say since one can setup the data directory hierarchy
in a number of different ways.  The way that GEMPAK is setup here in
Unidata for the image component is to have a directory like:

/data/ldm/gempak

which is the same thing as ~ldm/data/gempak (done through appropriate
links).  The various directories for GEMPAK files would then fall
under /data/ldm/gempak.  In the case of the NEXRAD composites, you
might have a directory like /data/ldm/gempak/nexrad/NEXRCOMP/...
So, the difference would be somewhat minor (and perhaps uneeded)
from what you have now: /data/nexrad/NEXRCOMP.  Also, you can
setup GEMPAK to use the directory structure that I put in place.
I tried to have the structure look as much like what I see in our
GEMPAK setup as possible.  But, then again, I am no GEMPAK expert
so this may be more of a problem than I think.

If you do already have a GEMPAK data tree setup, please let me know
what it is so I can make more astute comments on where the NEXRAD
composites would better fit.

Tom