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

20050210: 20050209: [Fwd: LDM Question]



Harry,

You can pull NGRID from idd.unidata.ucar.edu.
NWS has moved the final transition phase back to 3/31,
so it is still somewhat "test" state.

Steve Chiswell


>From: Harry Edmon <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200502102213.j1AMDKv2015991

>Is the NGRID feed available?
>
>Unidata Support wrote:
>
>>Harry,
>>
>>Yes, the CONDUIT file name conventions are provided here:
>>http://my.unidata.ucar.edu/content/data/conduit/ldm_idd/index.html
>>
>>
>>However, the quetion you have below asks about the 12km grid #218 that isn't 
>>on CONDUIT at this time. A subset is available in the HDS feed in grib1 forma
> t
>>(until NWS removes this duplicate data in March/April per their ADMIN notice)
> .
>>The 12km grids are availabel on the DVB-S Noaaport in GRIB2 format
>>(which we are putting into the NGRID) feed.
>>
>>The fields between the "!" characters will give the parameter names
>>(per the wgrib convention) and can be used to select the UWVN and VWND
>>grids (as would the TTAAII (T2) field of the WMO header for Noaaport.
>>
>>In the case the the ETA 12km grib2 grids on the tgftp server
>>in the ST.opnt directory, you will find that U & V are packed into
>>a single grib message. 
>>
>>Steve Chiswell
>>Unidata User Support
>>
>>
>>
>>  
>>
>>>From: Harry Edmon <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200502092224.j19MOHv2022461
>>>    
>>>
>>
>>  
>>
>>>This is a multi-part message in MIME format.
>>>--------------050007060008040103010405
>>>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>Content-Transfer-Encoding: 7bit
>>>
>>>Is there a place that describes the headers/keys for the CONDUIT feed 
>>>products?
>>>
>>>
>>>--------------050007060008040103010405
>>>Content-Type: message/rfc822;
>>>name="LDM Question"
>>>Content-Transfer-Encoding: 7bit
>>>Content-Disposition: inline;
>>>filename="LDM Question"
>>>
>>>Return-Path: <address@hidden>
>>>Received: from castor.3tiergroup.com (yssb.e0.border5s.pnap.net [206.253.195
> .2
>>>14] (may be forged))
>>>     by advect.atmos.washington.edu (8.13.2/8.13.2/Debian-1) with ESMTP id j
>>>19KqwZU015261;
>>>     Wed, 9 Feb 2005 12:52:58 -0800
>>>Received: from barbarossa (unknown [206.253.195.211])
>>>     by castor.3tiergroup.com (Postfix) with ESMTP
>>>     id 07E72116FA; Wed,  9 Feb 2005 20:52:58 +0000 (GMT)
>>>From: "Mark MacIver" <address@hidden>
>>>To: "'Harry Edmon'" <address@hidden>
>>>Cc: "'David Ovens'" <address@hidden>
>>>Subject: LDM Question
>>>Date: Wed, 9 Feb 2005 12:58:44 -0800
>>>MIME-Version: 1.0
>>>Content-Type: text/plain;
>>>     charset="us-ascii"
>>>Content-Transfer-Encoding: 7bit
>>>X-Mailer: Microsoft Office Outlook, Build 11.0.5510
>>>Thread-Index: AcUO4+J6FC5ezZUNT3ee5vPSpHgU/wABaOcg
>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>>>Message-Id: <address@hidden>
>>>X-Spam-Score: -2.485 () AWL,BAYES_00
>>>X-Scanned-By: MIMEDefang 2.48 on 128.95.89.50
>>>
>>>Harry/David,
>>>          Using the LDM, can I only get a couple fields(parameters) from a
>>>grib file e.g. u and  v from the 12km eta? I would like to only download
>>>part of the 12km Eta to save on bandwidth. Can this be done? - Thank you  -
>>>Mark
>>>
>>>
>>>--------------050007060008040103010405--
>>>
>>>    
>>>
>>--
>>**************************************************************************** 
>>Unidata User Support                                    UCAR Unidata Program 
>>(303)497-8643                                                  P.O. Box 3000 
>>address@hidden                                   Boulder, CO 80307 
>>---------------------------------------------------------------------------- 
>>Unidata WWW Service              http://my.unidata.ucar.edu/content/support  
>>---------------------------------------------------------------------------- 
>>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.