Forum

SeaDAS does not support OCM3.

Sean

Yes, rhos is Rayleigh corrected reflectance.

Sean

You seem to be attempting to process a L2 file. This will not work, as l2gen expects a L1 file as input.

Sean

Fabio, When the Hu algorithm is above 0.25 mg m^-3, but below 0.35 mg m^-3, we blend Hu with OCx. As Lachlan pointed out: The decision point in the function chl_oci that selects chl_hu, chl_ocx, or a blend of the two, is dependent only the magnitude of chl_hu (i.e., chl1). The code is correct. Sean

Julien,

Indeed, there is a discrepancy with the VIIRS PIC flaguse parameter. The good news is that the impact is insignificant. There is an extremely small number of pixels flagged as ATMWARN that are not also flagged by another of the flags in use as masks for the product.

Regards,
Sean

Sami, Geolocation of the Hawkeye imagery is a bit of a challenge: https://oceancolor.gsfc.nasa.gov/data/hawkeye/geolocation/ While we do our best to minimize the geolocation errors, we cannot completely eliminate them. Some scenes are worse than others. (or if you take an optimistic view, some scene...

Fabio, This issue is related to the change in filename for the MLAC data with the recent reprocessing. Unfortunately, there is no longer a direct link (by way of the filename) between the L1 files and the L2 files and the old browser was expecting that, at least for the data ordering. Unfortunately,...

Make sure you are using the same ancillary inputs that were used in the OBPG processing. With NRT files, the OBPG processes with the best available at the time of processing. If you process a file later, is it possible - actually quite likely - that the ancillary files obtained via getanc will not b...

The data are stored as signed short integers, so, if you are seeing floating point values, the function you used to read the PIC product applied the scale and offset values. The scale_factor and add_offset values are applied to the data using this simple equation: geophysical_value = scale_factor * ...

The issue stems from how the filenames are defined, and for SeaWiFS this most impacts the MLAC data. MLAC are merged files with all of the HRPT (direct broadcast) and on board recorded LAC (local area coverage) data. When the MLAC files were developed, we needed a way to ensure we didn't have duplic...