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

20030521: 20030521: Question about RUC Grid #

Kevin,

Use KXKY = 151;113 to specify the GRID SIZE. That is the number of
points in the X and Y direction (eg, what specifies the spacing
of the grid points between the LL and UR corners of the grid).

Steve Chiswell

>From: "Kevin Polston" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200305211510.h4LFA2Ld024783

>Steve,
>
>Here is the info I got from the RUC grid I am downloading using the
>GDINFO program.
>
>GRID NAVIGATION:
>     PROJECTION:          LCC
>     ANGLES:                25.0    -95.0   25.0
>     GRID SIZE:           151 113
>     LL CORNER:             16.28   -126.14
>     UR CORNER:             55.48    -57.38
>
>GRID ANALYSIS BLOCK:
>     UNKNOW ANALYSIS TYPE
>
>Number of grids in file:     535
>
>Maximum number of grids in file:     5000
>
>[GDU 2] Did not find any matching grids
>
>
>So when I am using GDCFIL to try and create a new grid with those
>specifications this is how I enter the information:
>
>GDOUTF = /usr1/nawips/metdat/gempak/grids/sfcoagrid_test
>PROJ = LCC/25.0;-95.0;25.0
>GRDAREA = 16.28;-126.14;55.48;-57.38 
>KXKY = 
>MAXGRD = 4999
>CPYFIL = 
>ANLYSS = 
>
>I didn't see any inof on the KXKY option so I left it blank. When I try
>to create the new grid file I get an error message saying:
>[GDCFIL -6] Grid size is invalid
>
>So I don't know if it is Operator Error in inputing the data or what.
>But I have tried fooling around with it by not having anything in the
>GRDAREA or taking the angles out of the PROJ but each time I keep coming
>up with the Grid size is invalid message.
>
>As I said earlier..when I tried using the CPYFIL = #RUC option the RUC
>entry in my grid navigation table was not the same as the RUC #236 grid
>so that was giving me the error of "Grid navigations need to be the
>same"...when I was using GDDIAG to try and copy certain grids into my
>new grid. 
>
>So, what am I doing wrong....?
>
>Kevin Polston
>Senior Instructor, NWSTC
>Kansas City MO 64152
>
>816-880-9314 ext 273
>
>
>----- Original Message -----
>From: Unidata Support <address@hidden>
>Date: Wednesday, May 21, 2003 12:51 pm
>Subject: 20030521: Question about RUC Grid # 
>
>> >From: "Kevin Polston" <address@hidden>
>> >Organization: UCAR/Unidata
>> >Keywords: 200305210632.h4L6WQLd028434
>> 
>> >Hi,
>> >
>> >I am trying to do an hourly LI using the RUC 500 MB temps in place of
>> >the observed 500 mb Temps. according to my pqact.conf file I am
>> >downloading RUC grid #236 (or option [w]).  The problem is in my grid
>> >navigation table I don't see the 236 grid information. I was 
>> hoping you
>> >might have that and be able to send it to me. I was able to use 
>> the 6 hr
>> >ETA 500 MB temp forecast and create an hourly sfc ETA LI but I 
>> want to
>> >be able to do it with the RUC as well. So I would appreciate it if 
>> you>could send me that info. Currently all I have for the RUC is 
>> grid #87
>> >and that is not compatible with the RUC data I am downloading. 
>> >
>> >Thanks.
>> >
>> >Kevin Polston
>> >Senior Instructor, NWSTC
>> >Kansas City MO 64152
>> >
>> >816-880-9314 ext 273
>> >
>> 
>> Kevin,
>> 
>> you can use gdinfo to print out the navigation information of the 
>> decoded grid
>> #236. The grib decoders will use the GDS block within the data to 
>> definethe grid, so they don't need the information to be in 
>> grdnav.tbl.
>> If you are creating a file in gdcfil, you can copy the navigation 
>> from a decoded
>> ruc file to a new file in CPYFIL by specifying the RUC- or you can 
>> specify the
>> projection and bounds information using the values output by gdinfo.
>> 
>> Steve Chiswell
>>
>****************************************************************************
><
>> Unidata User Support                                    UCAR 
>> (303)497-8643                                                  P.O. 
>> address@hidden                                   Boulder, 
>> --------------------------------------------------------------------
>> Unidata WWW Service              
>>
>****************************************************************************
><
>> 
>