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

[GEMPAK #RGI-969779]: Gempak Decoders

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: [GEMPAK #RGI-969779]: Gempak Decoders
  • Date: Thu, 05 Jun 2014 15:49:26 -0600
Hi Flavio, 

I received your file and decoded it and do not see the errors that you report.  
In fact, the file appears to be decoded correctly:

dcgrib2 cosmo.gem < cosmo_met5_00_20140514000

-rw-r--r--   1 mjames ustaff 285395456 2014-06-05 15:33 cosmo.gem

 GRID FILE: cosmo.gem                                                           
                                
     PROJECTION:          MER                 
     ANGLES:                 0.0     0.0     0.0
     GRID SIZE:              601     721
     LL CORNER:           -49.9000  -71.9550
     UR CORNER:            14.9000  -17.9550
 Number of grids in file:   329
 Maximum number of grids in file:   5000


This seems to be an issue with your environment.  From the log file it appears 
that GEMTBL is not set or found:

[8502] 140603/0000[DC 3] Version 6.6.0
[8502] 140603/0000[NA -1] cntrgrib1.tbl
[8502] 140603/0000[DCGRIB -51] can't open grib tables [NA -51], set GEMTBL


* If you are running dcgrib2 from the command line as user LDM, it's likely 
that the Gemenviron file is not being sourced - you will need to source 
~gempak/NAWIPS/Gemenviron to your shell and run dcgrib2 again.

* If you are running dcgrib2 from an LDM pattern action EXEC, then the command 
should include the option "-e GEMTBL=/home/gempak/NAWIPS/gempak/tables/" as 
mentioned at http://www.unidata.ucar.edu/software/gempak/man/prog/dcgrib2.html

    When using with the LDM, the GEMPAK grib routines must be able
    to access the grib tables located in the gempak distribution.
    This is done through the GEMTBL environmental variable.
    If the the LDM process does not have the GEMTBL variable set,
    then you must use the "-e GEMTBL=path" option.

    The following tables files are expected to be found:
        $GEMTBL/grid/cntrgrib[X].tbl
        $GEMTBL/grid/vcrdgrib[X].tbl
        $GEMTBL/grid/wmogrib[X].tbl
        $GEMTBL/grid/[CENTER]grib[X].tbl
        $GEMTBL/grid/dcgrib.tbl
        $GEMTBL/grid/gribkey.tbl






> Hi Michael, thanks for the attention.
> Regarding the GRIB file I tried to use the dcgrib 2 with these parameters
> cosmo_met5_00_20140514000
> 
> You can find the log with the error messages attached.
> I could see three main problems
> 
> [19588] 140517/0116[NA -1] wmogrib203.tbl
> [19588] 140517/0116[NA -1] wmogrib201.tbl
> [19588] 140517/0116[NA -1] grib2.tbl
> [19588] 140517/0116[DCGRIB 3] unknown projection 10
> 
> In the grid folder I could not find the files wmogrib203.tbl,
> wmogrib201.tbl and grib2.tbl.
> 
> Can you tell me what is wrong?
> 
> 

Ticket Details
===================
Ticket ID: RGI-969779
Department: Support GEMPAK
Priority: Normal
Status: Open