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

[AWIPS #BNN-794861]: edexgrib bug report

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: [AWIPS #BNN-794861]: edexgrib bug report
  • Date: Fri, 05 Jun 2015 14:56:01 -0600
I think this is the important error message:

> g2_info: '7777'  not found at end of GRIB message.

From the grib specs:


SECTION 5: END SECTION.

  The end section serves a human readable indication of the end of a GRIB 
record. It can also be used for computer verification that a complete GRIB 
record is available for data extraction. It should not be used as a search 
target since a '7777' bit combination could exist anywhere in the binary data 
stream.


So it seems that the file that is being decoder is not complete.  So I have to 
guess about this, but it may be that the file is incomplete when EDEX begins 
decoding, and it may be due to the pattern action being used.  I can't say for 
sure until I test CONDUIT GEFS myself, but I know that the GEFS on the NOAAport 
NGRID feed decodes without any error.  So my suggestions is to switch to NGRID 
GEFS for the time being.

-Michael

Ticket Details
===================
Ticket ID: BNN-794861
Department: Support AWIPS
Priority: Emergency
Status: Open