[IDD #UDG-536221]: GEFS

Hi Justin,

re:
> Nothing wrong with CONDUIT specifically. There appears to be an issue with
> the LDM pattern and how edex decodes it. Michael James explains below...

OK.  If the problem really is one of an incorrect LDM pattern-action file
action, then switching feed types would not solve your problem.

re:
> "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."

I will touch base with Michael about this when I return to Boulder on
Friday.

re:
> So I wanted to see if there were alternative sources for this same type of
> data. He had mentioned NGRID, so I wanted to inquire further.

Even if the GEFS fields were in another feed, a problem caused by a
pattern-action file action would likely persist.  But, I can't be
100% sure until I touch base with Michael.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: UDG-536221
Department: Support IDD
Priority: Normal
Status: Closed