Forum

Josep, Seems we missed a required modification to the LutUtils.py code. For the previous reprocessing, JPSS1_VIIRS did not require an xcal file, so LutUtils.py didn't look for them to pull down. Until we can get the change into a tag, you can make the following change to $OCSSW_BIN/seadasutils/LutUt...

NOAA provides a surface reflectance product that includes the I-bands: https://www.ospo.noaa.gov/Products/land/sr/

Not yet. We are working on it, but I cannot give a date. Well, I could, but it very likely wouldn't be a realistic one
OK...here's one: Dec 2023.

It is my *hope* to have some of our data available in the Earthdata Cloud by the end of 2023...but no promises.

Sean

Quite the loaded question ;) The Southern Ocean is big and most of it is quite far from civilization. This makes obtaining in situ validation data a challenge to say the least. As a result, the spatial and temporal sampling is rather skewed and probably not applicable to the entire Southern Ocean. T...

That flag will become "OPSHAL" (optically shallow water). It is not fully validated yet, so it's still "hidden" as SPARE23...apparently not well hidden

Sean

This is not unexpected. The same issue exists with the MODIS filenames. Both MODIS and VIIRS L1 files are "chopped" into 5 (or 6) minute granules, but the scan rate for the sensors does not fall exactly on the 5 (or 6) minute boundaries. The L2 filenames are derived from the actual time of...

The Rrs values are typically reported as 10nm wide square band values. The F0 values on the rsr_tables page are fully convolved with the sensor spectral response function. This is not the nominal 10nm square band value. So, the value in the metadata of the L2 file in question is the one to use, as i...

You can get the old LUTs back (see my response here: https://forum.earthdata.nasa.gov/viewtopic.php?p=12674#p12674), but if you want to update, go with R2022.14. The 'R' series is the new 'V', and once we get through ALL the missions we're reprocessing, a new 'V' tag will be defined (which will be e...

Yuyuan, If your LUTs were updated (and since the error reports it can't find the v3.0.0.2 lut, I'd say they were), your options are to update to a compatible R tag (R2022.12 or later ...best to use the current latest R2022.14) or restore the older LUTS to your $OCVARROOT/viirsn/cal/OPER tree. You ca...

Did you apply the scaling factor? The SST mapped product is stored as a scaled short integer. To get the correct floating point value, you need to apply the scale_factor and add_offset (although the offset is zero for this product): short sst(lat, lon) ; sst:long_name = "Sea Surface Temperature...