Earthdata Forum

I'm trying to process some raw VIIRS data, correct the bow-tie effect by using the default flags in l2bin, and run l3mapgen to create an image.
Here is my code:

l2gen ifile=SVM01.h5 geofile=GMTCO.h5 ofile=SV_L2_file.L2_1KM \
l2prod1="sst qual_sst l2_flags chl_oc3" \
resolution=1000 \
ctl_pt_incr=1 ctl_pt_incr=1 proc_ocean=1 \
proc_sst=1 proc_land=0 sline=3 atmocor=1 maskcloud=1 \
maskland=1 maskhilt=0 maskstlight=0

l2bin infile=SV_L2_file.L2_1KM ofile=SV_L2_binned \
resolve=1 \
suite=SST \
l3bprod=sst \
prodtype=regional \
qual_max=2 \
verbose=1

l3mapgen ifile=SV_L2_binned ofile="ao1.sst.$1.tiff" \
product=sst \
projection=mercator \
resolution=1100 \
interp=area \
north=36.274 \
south=19.0 \
east=-72.735 \
west=-87.75 \
oformat=TIFF \
palfile=default-black



Unfortunately, it fails at the l2bin step and doesn't fill any bins total_filled_bins: 0

Taking a look at the output from l2gen in seadas, there seems to be plenty of data to run l2bin (see sst.png and qual_sst.png).

Anyone see a problem in my code resulting the failure of l2bin? I also tried l2binning through seadas, but was unsuccessful. Again, my motivation for using l2bin is to remove the bowtie effect from VIIRS.

Thanks!

You seem to be using "IDPS-derived" VIIRS SDR inputs (i.e. NOAA generated).  The l2gen reader for those has not been updated to properly set the BOWTIEDEL flag. 
I'm not sure what l2gen would spit out for that flag given those inputs.  You could check the L2 (use the Masks feature in SeaDAS to display the BOWTIEDEL flag).

BTW, resolution=1000 is a MODIS-only input option for l2gen.  You don't need to set it. Most of the other options you've set are default values and also don't need to be set.

Sean

How would you recommend generating the Level 1 files from the raw VIIRS files?

Our workflow is running:
1) RT-STPS
2) C-SDR_SPA

and then we begin running l2gen. Do you guys use a different workflow for VIIRS files?

Thanks!
James

James,

Yes, we do.  We receive Level-0 VIIRS data from EDOS from which we generate the NASA-formatted Level-1 files (which we also distribute).    I'd recommend you just grab the L1 data we distribute.  You can also set up a subscription to receive data that cover your region of interest.

Sean

Hi Sean,

I guess my question now becomes; how do you generate the Level 1 NASA-formatted files?

We have our own receiving station where we collect raw VIIRS data, generate level 0, 1 and then use l2gen for level 2. We use SeaDAS for the processing. We'd like to use our own raw data instead of EDOS to cut down on latency time, but we're running into processing issues hence the initial post. Are the EDOS files different than ours? Or is there a level 1 to level 2 processing step that you guys use that is different?

Thanks!

James

James,

Well, that's a DRL question...According to the DRL IPOPP v2.6 documentation, it can do it:

"This document provides instructions for installing and operating the IPOPP software. IPOPP can
ingest JPSS and SNPP Raw Data Record (RDR), JPSS and SNPP Visible Infrared Imaging
Radiometer Suite (VIIRS) and Ozone Mapping Profiler Suite (OMPS) Production Data Set (PDS) files,
and Terra/Aqua PDS files. "

(The data we get from EDOS are PDS files)

Just out of curiosity, what is you perceived latency requirement? 

Sean