Forum

You are right that SeaDAS 9.1.0 cannot read OCI L1B V3 files. We expect the next release of SeaDAS 9.2.0 can.

Glad that you have figured it out! Thanks for reporting back

Hello Dan, Unfortunately, SeaDAS 9 has issues with GPT, and SeaDAS 8.3.0's GPT behaves the same as SNAP 10's GPT. For some reason, SeaDAS 8.3.0 could only get the OCI (V3) bands up to Rrs_688, and I suspect that's why GPT (SeaDAS 8.3.0 and SNAP) fails with any bands above Rrs_689. We are trying to f...

Dan,

Thanks for reporting the gpt issue!

Could you please do SeaDAS-Toolbox -> Software & System Info and post the results here? We would like to replicate the issue first?

Bing

Besides 8DAY, you will also find MONTH and YEAR binned data for AQUA MODIS CHL data here - https://oceandata.sci.gsfc.nasa.gov/directdataaccess/Level-3%20Binned/Aqua-MODIS/2015/01-Jan-2015/ for 2015. You can bin them together with l3bin - https://seadas.gsfc.nasa.gov/help-9.1.0/processors/ProcessL3b...

There is no issue with the command. I just successfully ran As you noticed, it's a network problem. It could be on your side, on our side or in between. Please try agian.

Sorry that we have not had time to revive writeImage.

When you do l2bin, the output file names will be DAY, 8D(means there is a 7 day difference between the start day and stop day), CU(custom day range), such as L3b.DAY or L3b.CU, or whatever name you specify. When you do l3mapgen on the L3b file, the file name will be L3m.DAY, L3m.8D or L3m.CU accordi...

Thanks for the tip on flaguse= NONE for l2bin

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

Please also share the name of your MODIS L1B file that you wanted to do l2gen on, so we can try to replicate the error