Forum

The issue is that valid_min and valid_max for ipar are not defined in product.xml, and l2gen assigned 0 to valid_min and valid_max by default. We'll fix the issue for the next V tag. In the mean time, you can change valid_min and valid_max in product.xml, so l2gen will create L2 files with valid_min...

I have valid ipar data after running l2gen on A2023164100000.L1A_LAC. I noticed l2gen is defining the wrong "valid_max" attribute for ipar, both "valid_min = 0" and "valid_max = 0". I looked at ipar in ocssw/share/common/product.xml, but did not see "valid_max=0&qu...

There is probably something wrong with ocssw/var/log/ancillary_data.db. You can run modis_atteph -r A2023164010000.L1A_LAC That'll download the att1/eph1 file. Then modis_GEO would work. Also, MODIS TERRA GEO file is available for download here -- https://oceandata.sci.gsfc.nasa.gov/directdataaccess...

What product name did you use for "chlor_a"? The default products for Landsat 8 are "Kd_490 Rrs_vvv angstrom aot_865 chlor_a". Make sure it's "chlor_a" with an underscore. Can you take a screenshot of your l2gen GUI "Products" tab, and post it here? Can you al...

I got the same error you got -- /Users/dshea/ocssw/oel_util/libpiutils/productInfo.cpp Line 948: need a default chlorophyll algorithm for this sensor running $ ~/ocssw/bin/ocssw_runner --ocsswroot ~/ocssw ~/ocssw/bin/l2gen suite=OC ifile=JPSS2_VIIRS.20230608T110600.L1A.nc geofile=JPSS2_VIIRS.2023060...

Unfortunately, I can't replicate your error. Can you update OCSSW to V2023.2? However, l2gen will complain that it can't open $OCVARROOT/viirsj2/cal/OPER/VIIRS_J2_CAL_STATIC_LUT_v3.2.3.1_20221202_vcst.nc and $OCVARROOT/viirsj2/cal/OPER/VIIRS_J2_CAL_RSB_DYNAMIC_LUT_20221129_20230430_v3.2.3.2_20230216...

For GOCI, you can download L1B files here -- https://oceandata.sci.gsfc.nasa.gov/directdataaccess/Level-1B/GOCI or here -- https://oceancolor.gsfc.nasa.gov/cgi/browse.pl?sen=amod And you can do l2gen (SeaDAS processor) on GOCI L1B files with product sena (satellite azimuth angle) and senz (satellite...

Please do SeaDAS-Toolbox -> Software & System Info and post the output here.

Please also share the name of your JPSS2 L1 File, and I assume that you provided a corresponding GEO file

It's always nice to be acknowledged

Here is the link to "how to cite" -- https://oceancolor.gsfc.nasa.gov/resources/how-to-cite/

It turns out that the metadata information in LANDSAT 8/9 OLI files that start with "LO" have changed, so obpg_file_type returns "OLI: Level 1B " instead of "OLI L8: Level 1B". That is causing the problem. $ obpg_file_type LO08_L1TP_130044_20230423_20230425_02_T1/LO08_L...