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

20041206: 20041203: 20041203: 20041202: 20041201: GEMPAK trouble with non-standard domain

Brian,

You have to delete the old file gempak grid file before running
the new dcgrib2 decoder, since the old file has the wrong navigation,
and you won't be able to decode the corrected projection to that
file.

After running the updated decoder on your test data, I get:
 GEMPAK-GDINFO>r

 GRID FILE: testme.fsl                                                          
                                                            

 GRID NAVIGATION: 
     PROJECTION:          LCC                 
     ANGLES:                25.0  -169.0    25.0
     GRID SIZE:          301 225
     LL CORNER:              16.00    160.00
     UR CORNER:              55.22   -131.41


Also, make sure you are executing the new dcgrib2 decoder if
you still have problems.

Steve Chiswell
Unidata User Support






>From: Brian Jamison <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200412061724.iB6HOTlI007571

>Hi Steve,
>
>I'm still having trouble, even after using the new decoder.
>Here's the output from gdinfo:
>
>  GDFILE    Grid file                          
>/home/mab/jamison/gempak/0104800000000.gem
>  LSTALL    Full list flag                    yes
>  OUTPUT    Output device/filename            t
>  GDATTIM   Grid date/time                    f000
>  GLEVEL    Grid level                        500
>  GVCORD    Grid vertical coordinate          all
>  GFUNC     Scalar grid                       all
>  Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
>  GEMPAK-GDINFO>r
>
>  GRID FILE: /home/mab/jamison/gempak/0104800000000.gem
>
>  GRID NAVIGATION:
>      PROJECTION:          LCC
>      ANGLES:                25.0  -169.0    25.0
>      GRID SIZE:          301 225
>      LL CORNER:              16.00    160.00
>      UR CORNER:             -36.88    150.08
>
>  GRID ANALYSIS BLOCK:
>       UNKNOWN ANALYSIS TYPE
>
>  Number of grids in file:   745
>
>  Maximum number of grids in file:   5000
>
>  [GDU 2]  Did not find any matching grids.
>  Parameters requested: GDFILE,LSTALL,OUTPUT,GDATTIM,GLEVEL,GVCORD,GFUNC.
>
>
>It appears that the UR corner is still not coming out right.
>Do you have any ideas about what's going wrong?
>
>
>Brian
>
>
>
>On Dec 3, 2004, at 4:11 PM, General Support wrote:
>
>>
>>
>> Brian,
>>
>> Disregard the first message.
>>
>> Here is the updated solaris executable.
>>
>> Steve CHiswell
>> *********************************************************************** 
>> *****
>> 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
>> *********************************************************************** 
>> *****
>>
>> On Fri, 3 Dec 2004, Brian Jamison wrote:
>>
>>> Thanks for the new dcgrib2, Steve, but I tried to use it and it
>>> wouldn't run.  I talked with our system administrator, and we
>>> found out that I need it to be compiled on a Sun machine.
>>> Would you be able to do that and send me a new executable?
>>>
>>>
>>> Brian
>>>
>>>
>>> On Dec 3, 2004, at 1:49 PM, Unidata Support wrote:
>>>
>>>>
>>>> Brian,
>>>>
>>>> The problem you are having is the LoV (central longitude) is in a
>>>> different
>>>> hemisphere than the Lo1 (lower left longitude). This is a general
>>>> limitation of
>>>> the gblamb.c routine I mentioned, so you will have the same problem
>>>> using
>>>> the GEMPAK program NAGRIB.
>>>>
>>>> From your previous mention of asking about source code, I'm assuming
>>>> you had downloaded a binary distribution, so I've posted a Linux
>>>> binary at
>>>> http://my.unidata.ucar.edu/content/software/gempak/download/patches/
>>>> binary/linux/dcgrib2
>>>> If you need a different platform, let me know.
>>>>
>>>> Steve Chiswell
>>>> Unidata User Support
>>>>
>>>>
>>>>
>>>>> From: Brian Jamison <address@hidden>
>>>>> Organization: UCAR/Unidata
>>>>> Keywords: 200412031924.iB3JOalI013936
>>>>
>>>>> Hi Steve,
>>>>>
>>>>> I'll take you up on your offer.  I tried to email the grib file,
>>>>> but I'm limited to 25MB on outgoing mail.  So I put the file
>>>>> on a web page:
>>>>>
>>>>> http://www-frd.fsl.noaa.gov/mab/jamison/steve/
>>>>>
>>>>> Just right-click and download.  Let me know if you have any
>>>>> trouble.
>>>>>
>>>>> Thanks so much for helping me with this!
>>>>>
>>>>>
>>>>> Brian
>>>>>
>>>>>
>>>>> On Dec 3, 2004, at 11:26 AM, Unidata Support wrote:
>>>>>
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> The Lambert projection code is part of the GEMPAK libraries,
>>>>>> and not specific to dcgrib2. The routine is
>>>>>> $GEMPAK/source/gemlib/gb/gblamb.c
>>>>>> which is available in the source code distribution.
>>>>>>
>>>>>> The dcgrib2 program is in the source distribution under
>>>>>> $NAWIPS/unidata/ldmbridge/dcgrib2.
>>>>>>
>>>>>> If you want to send me a single (or small) example of
>>>>>> your grib, I can pass it through the debugger and see where
>>>>>> things are getting fouled.
>>>>>>
>>>>>> Steve Chiswell
>>>>>> Unidata User Support
>>>>>>
>>>>>>
>>>>>>
>>>>>>> From: Brian Jamison <address@hidden>
>>>>>>> Organization: UCAR/Unidata
>>>>>>> Keywords: 200412031643.iB3GhWlI024668
>>>>>>
>>>>>>> Hi Steve,
>>>>>>>
>>>>>>>> Brian,
>>>>>>>>
>>>>>>>> Since this is not grid #252, that value should be set to 255
>>>>>>>> just for correctness, but since the dcgrib2 decoder will use the
>>>>>>>> GDS
>>>>>>>> when present, that shouldn't be your problem here.
>>>>>>>>
>>>>>>>> One possibility is that the Lo1 angle is not in the range 0 to  
>>>>>>>> 360,
>>>>>>>> eg your wgrib output shows 520. Can you change this to a more
>>>>>>>> conventional 260? That way, the (Lo1 - Lov) difference in
>>>>>>>> computing the upper right point should be in the correct  
>>>>>>>> distance.
>>>>>>>
>>>>>>> I don't know of an easy way to "edit" a grib file to change this
>>>>>>> value.  I wasn't the person that created these grib files, so it's
>>>>>>> not easy for me to re-create them with this change, either.
>>>>>>>
>>>>>>> Would it be possible to get the code for creating the dcgrib2
>>>>>>> executable, so I can make the changes to handle the 520
>>>>>>> value?
>>>>>>>
>>>>>>>
>>>>>>> Brian
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> ******************************************************************* 
>>>>>> **
>>>>>> **
>>>>>> ***** <
>>>>>> 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.
>>>>>
>>>> --
>>>> ********************************************************************* 
>>>> **
>>>> ***** <
>>>> 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.
>> <dcgrib2>
>
--
**************************************************************************** <
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.