Re: [gembud] [GEMPAK #MGD-944158]: GDVINT: [GDVINT -15] Grid size is too large.

Hi Michael,

A reference to 2014012812_presvcord.gem exists in my working directory, but
it contains 0 grids:

GRID FILE: /home/rconnelly/Gempak_Scripts/2014012812_presvcord.gem


 GRID NAVIGATION:
      UNKNOWN GRID NAVIGATION
 GRID ANALYSIS BLOCK:
      UNKNOWN ANALYSIS TYPE

 Number of grids in file:     0

 Maximum number of grids in file:   5000

 [GDU 2]  Did not find any matching grids.



Here is the gdinfo for the input file I'm using for GDVINT:

GRID FILE: /home/rconnelly/Gempak_Scripts/2014012812_rap.gem


 GRID NAVIGATION:
     PROJECTION:          LCC
     ANGLES:                25.0   -95.0    25.0
     GRID SIZE:          451 337
     LL CORNER:              16.28   -126.14
     UR CORNER:              55.48    -57.38

 GRID ANALYSIS BLOCK:
      UNKNOWN ANALYSIS TYPE

 Number of grids in file:   686

 Maximum number of grids in file:   5000


Thanks,
Ryan

On Wed, Jan 11, 2017 at 11:47 AM, Unidata GEMPAK Support <
support-gempak@xxxxxxxxxxxxxxxx> wrote:

> Hi Ryan,
>
> * Does the file 2014012812_presvcord.gem already exist?
> * If so, what is its projection and navigation info (using gdinfo)?
> * What is the projection and navigation of the file 14012812_rap.gem (what
> RR domain is this?)
>
>
> Michael James
> Unidata Program Center
> Boulder, CO
>
> On Tue, Jan 10, 2017 at 3:52 PM, Ryan Connelly <
> support-gempak@xxxxxxxxxxxxxxxx> wrote:
>
> > New Ticket: GDVINT: [GDVINT -15] Grid size is too large.
> >
> > Hi,
> >
> > I'm trying to use GDVINT to convert a gem file of RAP data from its
> native
> > sigma coordinates to pressure coordinates.  Here is my input:
> >
> >  GDFILE    Grid file
> > /home/rconnelly/Gempak_Scripts/14012812_rap.gem
> >  GDOUTF    Output grid file                  2014012812_presvcord.gem
> >  GDATTIM   Grid date/time                    f000
> >  GVCORD    Grid vertical coordinate          sgma:10/pres
> >  GLEVEL    Grid level                        100-1000-50
> >  MAXGRD    Maximum number of grids           5000
> >  GAREA     Graphics area                     30;-100;50;-60
> >  VCOORD    Vertical coordinate type          none;hght
> >
> > However, I encounter this error:
> >
> >  [GDVINT -15]  Grid size is too large.
> >
> > I'm not really sure what this means, since I've tried reducing the GAREA
> > all the way down to a 1x1 lat/lon square, and MAXGRD to 1, and GLEVEL to
> > 900-1000-50, and even have run with all three of these minimalist
> settings
> > at once, yet encounter this error every time.  Which thing is too large,
> > and how do I make that thing smaller?
> >
> > Thanks,
> > Ryan
> >
> > --
> > Ryan Connelly
> > M.S. Student in Atmospheric Sciences, Stony Brook University
> > B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
> > University
> > rconne01@xxxxxxxxx
> > ryan.connelly@xxxxxxxxxxxxxx
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: MGD-944158
> > Department: Support GEMPAK
> > Priority: Normal
> > Status: Open
> > Link:  https://andy.unidata.ucar.edu/esupport/staff/index.php?_m=
> > tickets&_a=viewticket&ticketid=27845
> > ===================
> > 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.
> >
> >
>
>
>
> Ticket Details
> ===================
> Ticket ID: MGD-944158
> Department: Support GEMPAK
> Priority: Normal
> Status: Open
> ===================
> 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.
>
>
>


-- 
Ryan Connelly
M.S. Student in Atmospheric Sciences, Stony Brook University
B.S. in Meteorology with Minors in Mathematics and GIS, Valparaiso
University
rconne01@xxxxxxxxx
ryan.connelly@xxxxxxxxxxxxxx