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

20020328: GEMPAK grid limits

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020328: GEMPAK grid limits
  • Date: Thu, 28 Mar 2002 09:07:14 -0700 (MST)
The current maximum number of grids is 30,000. That will be a very large file
for the 1 degree AVN where each grid is 30 to 100KB, and eventually you may hit
the 2GB file size limit on most systems. How many grids did you define in MAXGRD
in NAGRIB? What is the decoded file size when you hit the limit, and how many
grids does GDINFO show in the file?

Alternatively, you can use dcgrib2 with the file templates and store each
forecast hour in a separate file.

I plan on making a new release shortly and will look at the current limits- but
the operating system limits of filesize are another issue that the larger
grids will run into (eg 12km ETA, .5 degree AVN, 384 hour AVN runs etc.)

Steve Chiswell
Unidta User SUpport



On Thu, 28 Mar 2002, Nelson, Michael wrote:

> Hi,
>       I was wondering if there is any plan to release a new binary version
> of GEMPAK with the capability for an increased number of grids.  The NWS
> started releasing the AVN on one degree grids to 180 hours yesterday.
> Currently nagrib can only decode out to the 17th grid in the 144 hour
> forecast file.
> 
> Thanks for any info,
> 
> Mike Nelson
> address@hidden
> 
> 
> ******************************************************************
> This email and any files transmitted with it from the ElPaso 
> Corporation are confidential and intended solely for the 
> use of the individual or entity to whom they are addressed. 
> If you have received this email in error please notify the 
> sender.
> ******************************************************************
>