Forum

I believe the Mosaic may internally use GPT, so you might also compare the files: [SEADAS_HOME]/bin/gpt.vmoptions with [SNAP_HOME]/bin/gpt.vmoptions

Perhaps change the line for virtual memory to:
-Xmx8192m

Since it works in SNAP, you could compare the SNAP preference Performance settings with the SeaDAS preference Performance settings.

I'm not familiar with these L2 files, their sizes etc. You mention that you can mosaic a single band, but with all bands it fails. Likely it could be a memory issue. To boost virtual memory go in Preferences to Performance. If this doesn't work, one route would be that Mosaic is a tool developed by ...

SeaDAS likely doesn't support those files. You would need to determine if SeaDAS can recognize the geocoding. If you view a file and click the map gridlines, this is a good way to determine whether the geocoding is being recognized. If gridlines appear with sensible coordinate labels then the geocod...

Please post a screenshot of the "Input/Output" and the "Parameters" section of the Pixel Extraction GUI.

It should write a file called "pixEx_measurements.txt" in whatever is your "Output directory" as defined in the Pixel Extraction GUI.

Danny

One possible issue may be that you are using an incompatible font. Make sure the font in gridlines is supported on your system. In "Layer Manager" click "Map Gridlines" then click the pencil icon to the right. Then in "Layer Editor" change "Labels Font Type" t...

The missing coastal data pixels are likely compromised quality due to detected/suspected presence of aerosols.

You could try using different aerosol models which are governed by aer_opt. For an example see:
https://www.youtube.com/watch?v=oGwupIMKvdw&t=5422s

Danny

I have never seen this behavior before. Please send what SeaDAS version you are using and your operating system info.

Please post more specifics. Post a screenshot of your pixel extraction parameters, box size etc.

If you are getting heap dump crashes then possibly you need to decrease the box size.

There were some filenaming issues in previous versions of SeaDAS where the Pixel Extraction Tool appended file meta (which may contain spaces) to the file name and this oftentimes resulted in a file which was hard to locate on the system. This issue was fixed in SeaDAS 9.0.0. Most likely that is wha...