Forum

SeaDAS does not provide a reader for L3b files. You can use l3mapgen to create L3m files from L3b, which SeaDAS can read -- https://seadas.gsfc.nasa.gov/help-8.4.0/processors/ProcessL3mapgen.html

See this post too -- viewtopic.php?p=12218&hilit=l3b#p12218

We have not had time to migrate the writeImage tool from SeaDAS 7.5 to 8. We will work on reviving the tool in SeaDAS 9

The real OCI data is out, so is SeaDAS 9. You can try it with the latest T tag T2024.16

It'll help if you can share the name of a L3m file that you can not open. Please also do Softwaer & System Info on SeaDAS, and share the result here.

Dirk,

Have you tried to put the same L1B file in two different directories, and see how l2gen behaves?

Bing

Sorry for the delayed reply. Now SeaDAS 9 is just released, could you please try docker 2.0 with it, see if the issue persists -
https://seadas.gsfc.nasa.gov/downloads/
https://seadas.gsfc.nasa.gov/client_server/

Sorry for the delayed reply. Now SeaDAS 9 is just released, could you please try docker 2.0 with it, see if the issue persists -
https://seadas.gsfc.nasa.gov/downloads/
https://seadas.gsfc.nasa.gov/client_server/

SeaDAS is not able to read l3b files, the output of l2bin. L3mapgen maps l3b files to l3m files, which SeaDAS can read.

Maybe l2gen needs an L1 file instead of L2 file as input?

"Input file PRM2017147131440.L1B.nc is a NetCDF4 PRISM L2 file" indicates that l2gen thinks that PRM2017147131440.L1B.nc is a NetCDF4 PRISM L2 file