[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #OAO-873149]: Re: RPCCDS LDM Feedtype Enhancement
- To: Virginia.Galvin@xxxxxxxx
- Subject: [LDM #OAO-873149]: Re: RPCCDS LDM Feedtype Enhancement
- From: "Unidata LDM Support" <support-ldm@xxxxxxxxxxxxxxxx>
- Date: Tue, 25 Mar 2008 16:58:22 -0600
- Delivered-to: support-ldm@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id 5FCCBCB18B; Tue, 25 Mar 2008 16:58:22 -0600 (MDT) id 394E7D5116; Tue, 25 Mar 2008 16:58:22 -0600 (MDT)
Gini,
> Can you please advise on how to use a new feedtype, eg, NEXRD3, for
> testing purposes?
>
> thanks
>
> Gini Galvin
> Computer Specialist
> NWS/TOC/TSB
>
> David S Alden wrote:
> > Hi Gini,
> > I am atempting to submit some Level III products to LDM on the development
> > systems and I have immediately run into a problem. I've looked over the
> > feedtypes already defined in the LDM and, of course, I don't want to use any
> > that others are already using for other data. However, it would appear that
> > a new feedtype "NEXRD3" would be appropriate for our purposes. What does
> > Unidata say about an LDM feedtype enhancement for our purposes. What would
> > it take to enhance the LDM-6.6.5 release to add "NEXRD3" for our testing
> > purposes? Please advise. Thanks.
The number of feedtypes is very limited, so use the EXP feedtype for
experimenting. Be sure that the product-identifiers are easily
distinguishable from anything else (they could, for example, start
with "NEXRAD3" or some other easily-selected token). And don't allow
the hosts that receive those data-products on the general IDD.
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: OAO-873149
Department: Support LDM
Priority: Normal
Status: Closed
