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

20040910: 20040910: Extended grib header on IDD.



Stonie,

We set aside the NTEXT, NGRID, NPOINT, NIMAGE, NNEXRAD feedtypes for
NOAAPORT, but due to the initial compatibility with the FOS
convention, have continued to use the HDS and IDS/DDPLUS feeds.
Since the GINI products were not part of the FOS, it was straight forward
to assign those to NIMAGE, and the unencryption of NIDS made a
clear break for those products to NNEXRAD though the Product Header of
those NEXRAD products in the NOAAPORT broadcast has never been used.
Some 5+ years ago, my assumption was that the PDH would be used to
assign the feedtype, but NWS has never completely implemented that protocol.
Since the redbook products were part of the FOS stream the HDS feed is the
location at this time.

My idea of canonicalization would be that following the "!" would be the
description type of product data, eg: sat (now satz for zlib gini), grib, 
redbook,
bufr, etc, which would make pqact piping of all "grib" very straight forward,
versus combining WMO patterns ^[HOLMYZ] with other source naming
conventions like CONDUIT, NOGAPS, GEM etc.

Steve






>From: Stonie Cooper <address@hidden>
>Organization: Planetary Data, Incorporated
>Keywords: 200409102045.i8AKjsnJ016672

>Steve,
>
>Thank you very much; it makes perfect sense . . . I just didn't want to go off
>  
>and create something on a guess for those that might stream data back to the 
>IDD from our NRS solution.
>
>I was curious to note that there was a use of "!redbook" instead of setting 
>the feedtype to NGRAPH.  I have been setting the feedtype to NGRAPH - would 
>it be more appropriate for us to set to HDS, as I saw, and have the !redbook?
>
>Stonie
>
>On Friday 10 September 2004 20:33, Unidata Support wrote:
>> Stonie,
>>
>> The description is provided on the CONDUIT information page:
>> http://my.unidata.ucar.edu/content/data/conduit/ldm_idd/index.html
>> (the section between the "!" characters is what you are interested in).
>>
>> The derivation of fields is aided by the publically available wgrib.c
>> routine from NWS.
>>
>> This stems from my desire to provide a more informative description of the
>> data than the WMO header alone.
>>
>> Steve Chiswell
>> Unidata User Support
>>
>> >From: Stonie Cooper <address@hidden>
>> >Organization: Planetary Data, Incorporated
>> >Keywords: 200409101243.i8AChnnJ016295
>> >
>> >Steve and Steve,
>> >
>> >I apologize for this intrusion, I just got a note this morning wanting to
>> > know
>> >
>> >when we'll update our IDD header replication for the extended GRIB data. 
>> > As we don't have IDD, I didn't know what they were talking about at
>> > first.
>> >
>> >We had done, a long time ago, extensions for "/m" - for example,
>> > "/mETA_84" - but the example sent to me this morning was:
>> >
>> >ZPBL98 KWBE 100600
>> > /mETA_84!grib/ncep/ETA_84/#218/200409100600/F027/PRES/sfc/
>> >
>> >Do you guys have an ICD or format documentation on this?  I want to keep
>> >things as close to what you have for those customers of ours that do act
>> > as a node on the IDD . . . so the MD5 deduplication and other aspects
>> > work correctly for your delivery.  If this information is not available,
>> > just let me know . . .
>> >--
>> >Stonie R. Cooper
>> >Planetary Data, Incorporated
>> >(402) 727-6599
>>
>> --
>> ***************************************************************************
>>* < Unidata User Support                                    UCAR Unidata
>> Program < (303)497-8643                                                 
>> P.O. Box 3000 < address@hidden                                  
>> ---------------------------------------------------------------------------
>>- < Unidata WWW Service             
>> ---------------------------------------------------------------------------
>>- < NOTE: All email exchanges with Unidata User Support are recorded in the
>> Unidata inquiry tracking system and then made publicly available
>> through the web.  If you do not want to have your interactions made
>> available in this way, you must let us know in each email you send to us.
>
>-- 
>Stonie R. Cooper
>Planetary Data, Incorporated
>(402) 727-6599
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.