SeaDAS/OCSSW cannot process NetCDF4 GOCI-II L1B: getanc fails and l2gen reports "Can't find sensor directory for ID -1"

[haoyurose]

Hello,

I am testing SeaDAS + OCSSW for processing GOCI-II original L1B NetCDF4 data on Windows 11 + WSL Ubuntu.

My setup:
- SeaDAS GUI installed on Windows
- OCSSW installed in WSL Ubuntu
- both `getanc` and `l2gen` are available in the Ubuntu terminal
- I installed the GOCI mission during OCSSW installation
- the GOCI mission directory exists at:

/home/User/ocssw/share/goci

So this does not seem to be a missing GOCI mission installation.

Input file:
GK2_GOCI2_L1B_20240704_011530_LA_S010.nc

The file global attribute is:

:instrument = "GOCI-II" ;

I also generated a GEO file separately.

1) `getanc` on the original file fails

Command:
getanc -v "/mnt/d/PATH/GK2_GOCI2_L1B_20240704_011530_LA_S010.nc"

Output:
ancillary_data.db
Determining pass start and end times...
GOCI-II
Traceback ...
File "/home/User/ocssw/bin/seadasutils/ProcUtils.py", line 442, in check_sensor
return senlst[(fileattr['instrument'])].strip()

This suggests that `getanc` reads the instrument as "GOCI-II", but fails during sensor mapping.

2) I created a test copy and changed the global attribute

I changed:
:instrument = "GOCI-II"

to:
:instrument = "GOCI"

using `ncatted`.

After that, `getanc` proceeds a bit further, but still fails:

Command:
getanc -v "/mnt/d/PATH/GK2_GOCI2_L1B_20240704_011530_LA_S010_test_goci.nc"

Output:
ancillary_data.db
Determining pass start and end times...
GOCI
Traceback ...
File "/home/User/ocssw/bin/seadasutils/timestamp_utils.py", line 50, in goci_timestamp
return start_time, end_time, sat_name

So changing the instrument name alone is not sufficient. It seems the GOCI timestamp parser does not match this GOCI-II file structure/metadata.

3) `l2gen` also fails on the original GOCI-II file

Command:
l2gen ifile="/mnt/d/PATH/GK2_GOCI2_L1B_20240704_011530_LA_S010.nc" geofile="(my GEO file)" ofile="/mnt/d/PATH/GOCI2_NNAC/test/test_L2.nc"

Output:
Input file /mnt/d/PATH/GK2_GOCI2_L1B_20240704_011530_LA_S010.nc is a NetCDF4 GOCI-II L1B file.

Loading characteristics for (null)

-E- Can't find sensor directory for ID -1

This suggests that `l2gen` recognizes the file as NetCDF4 GOCI-II L1B, but does not map it to a valid supported sensor directory.

My questions are:

1. Is NetCDF4 GOCI-II L1B currently supported by SeaDAS/OCSSW `getanc` and `l2gen`?
2. If yes, is there a required metadata convention, preprocessing step, or additional mission package beyond `goci`?
3. If not, is there any recommended workaround for using SeaDAS/OCSSW with GOCI-II data?

Thank you.

[OB ScienceSW - alex]

You can use SeaDAS to view/inspect GOCI-II L1B files but the mission is not supported by our processing software (l2gen, getanc, etc).