Forum

The next planned reprocessing for MODIS Aqua ocean color data will not take place until the mission has reached its end. NASA budgets and priorities are still not finalized, so I cannot provide a reliable estimate as to when that reprocessing will be accomplished. That said, I can say that changes i...

The optically shallow flag (OPSHAL) is actively being populated in the current version of the code. Here is what is output in the current L2 files: int l2_flags(number_of_lines, pixels_per_line) ; l2_flags:long_name = "Level-2 Processing Flags" ; l2_flags:coordinates = "longitude lati...

Andrew, I can't speak to issues with LANCE, but there shouldn't be an issue accessing MODIS Terra L1A data from the OB.DAAC. Can you provide the endpoint you're having issue with? BTW, plans are in flux about the decommissioning of the Terra, Aqua and Aura missions. So far, data are still being coll...

It has nothing to do with the "latband" coefficients. There is an explicitly defined geographic box where that test is applied: const float equatorialNorth = 30.0; // the ranges where SST diff tests are applied const float equatorialSouth = -10.0; const float equatorialWest = -105.0; const...

l2gen has a filtering feature (defined by filter_opt and filter_file). There is a default filter file for MSI, but I don't think it is enabled by default (i.e. filter_opt=0 is set). You can try enabling it to see if that improves the result (filter_opt=1). You can also try modifying the filter_file ...

To add to Minwei's response... rhos also accounts for gaseous absorption (in addition to simple Rayleigh scattering). It does not require "atmospheric correction" (really, aerosol correction...we're bad at being clear about what the parameters do), so you can set atmocor=0 to speed up the ...

This is most definitely an artifact of the cloud screening algorithm. There is an explicit test applied to the region you identified. That test sets the quality flag to a minimum of 2 (and sets the SSTREFDIFF bit in the flags_sst for that pixel) if the computed SST value is significantly less than t...

Yes, a test tag with this fix is being prepped and should be available sometime next week. It will take a little longer to get into a release tag, but as SeaDAS is planning another release in October, it shouldn't be too long of a wait

Regards,
Sean

Roger,

Yep, that was discovered recently by Alex as well and will be corrected in an upcoming release. The wee bit o'code whoopsie that caused the woe was introduced in August 2024 (in the source code),which jives with Fred's report that the slowness began with V2025.1.

Regards,
Sean

Yes, this was a temporary issue. The service has been restored.
Regards,
Sean