Re: [awips2-users] Using full-disk full-resolution GOES-R NetCDF files from AWS

I looked at the pattern compared with the filename, and it looks like the 
pattern is for a netcdf file containing all channels.

On Wed, 2019-06-26 at 18:07 +0200, Devin Eyre wrote:
The same thing happened when I tried using an L2 file:

WARN  2019-06-26 16:05:08,451 6030 [Ingest.GOESR-2] GoesrNetcdfDecoder: No 
valid records were found in file: 
OR_ABI-L2-CMIPF-M6C14_G16_s20191771550234_e20191771559542_c20191771600038.nc

On Tue, 2019-06-25 at 21:06 +0000, deyr@xxxxxxxxxxxx wrote:
The L1b files are the Radiance files. The L2 files are pretty much the same as 
what they've been sending over the NOTHER feed on noaaport, where the data is 
in units of Kelvin. McIdas only works with the L1b files, as far as I know.
Excerpt from /awips2/edex/logs/edex-ingest-satellite-20190625.log:

WARN  2019-06-25 21:03:59,275 7842 [Ingest.GOESR-1] GoesrNetcdfDecoder: No 
valid records were found in file: 
OR_ABI-L1b-RadF-M6C14_G16_s20191762040228_e20191762049536_c20191762050004.nc

On Tue, 2019-06-25 at 14:03 -0600, Michael James wrote:

On Tue, Jun 25, 2019 at 1:32 PM Devin Eyre 
<Devin.Eyre@xxxxxxxxxxxx<mailto:Devin.Eyre@xxxxxxxxxxxx>> wrote:
I've been trying with the L1b version of the files, and in goesr.xml I noticed 
one of the patterns had L2 in it. Should I switch to L2 for awips2


I'm not sure I understand.  What have you been trying with the L1b files, 
exactly?  And what are the results?