[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[CONDUIT #CLX-227004]: Re: 20120424: re: upcoming RUC2 -> RAP change in CONDUIT and NGRID
- Subject: [CONDUIT #CLX-227004]: Re: 20120424: re: upcoming RUC2 -> RAP change in CONDUIT and NGRID
- Date: Mon, 30 Apr 2012 08:24:26 -0600
Hi Becky,
re:
> I did the diff between my table and the new one and I got the "hack" you
> said I should expect. I also got 4 entries for an unknown covariance
> entry that I don't think you had mentioned -- are these fine?
Yes, the unknown covariance entries are another hack for products that
are not in standard GRIB tables. If I remember correctly, I added
these for NOAAPort products that our NOAAPort ingest code didn't know
how to create LDM/IDD Product IDs (our 'gribinsert' and NOAAport ingest
packages share the same GRIB tables).
> < ! Hack for 'gribinsert' for CONDUIT field not properly tagged
> < 000 019 242 000 RH with respect to PW %
> RHPW 0 -9999.00
> < !
> 266,273d262
> < ! covariance category (category 192)
> < !D# CT# ID# PD# NAME UNITS
> GNAM SCALE MISSING
> !23|123|123|123|12345678901234567890123456789012|12345678901234567890|123456789012|12345|123456.89
> < 000 192 192 000 Unknown covariance product -
> COV192 0 -9999.00
> < 000 192 192 009 Unknown covariance product -
> COV192 0 -9999.00
> < 000 192 194 000 Unknown covariance product -
> COV194 0 -9999.00
> < 000 192 194 009 Unknown covariance product -
> COV194 0 -9999.00
Again, no worries on these entries.
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: CLX-227004
Department: Support CONDUIT
Priority: Normal
Status: Closed
