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

Re: 19990114: Feed type for Nexrad level 2 data

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 19990114: Feed type for Nexrad level 2 data
  • Date: Fri, 15 Jan 1999 15:02:30 -0700 (MST)
On Thu, 14 Jan 1999, Unidata Support wrote:

> >To: address@hidden
> >From: Harry Edmon <address@hidden>
> >Subject: Feed type for Nexrad level 2 data
> >Organization: .
> >Keywords: 199901142147.OAA26761
> 
> Can the nexrad level 2 data be assigned an offical LDM feed type?  I am
> currently using EXP, but I use that for other data.  The level 2 data needs to
> be restricted to certain hosts, and I can only do that with a seperate feed
> type.  Thanks.
> 
Harry,

I think thers's  a good possibility of having a nexrad level 2 feedtype.
Since this is a coding/release of the LDM, it probably will not happen
until next LDM release. I expect there will be a LDM release in the near
future for the NOAAport feedtypes.   Maybe Glenn has alternative idea.
Also, I forwarded the other messages to Glenn for comment.

Robb...



> 
> --
> Dr. Harry Edmon                       E-MAIL: address@hidden
> (206) 543-0547                        FAX:    (206) 543-0308
> Dept of Atmospheric Sciences
> University of Washington, Box 351640, Seattle, WA 98195-1640
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================