OLCI support disappeared?
OLCI support disappeared?
I recently installed SeaDAS 7.4, and see that there is no support for downloading OLCI processors (it doesn't show up in the GUI). I understand that it was in 7.3.2, and that it was possible to process OLCI L1 to L2 data. Am I missing something, or was that removed from SeaDAS 7.4? I tried installing 7.3.2 instead to see if that would provide the processor, but it fails to find the code when I try simple things like "install_ocssw.py --git-branch=v7.3 --olci" (or the same with 7.4).
I thought it was still in Github but I haven't attempted to download/compile everything manually since I would prefer (for teaching) to be able to use the standard GUI interface, etc.
Thanks!
I thought it was still in Github but I haven't attempted to download/compile everything manually since I would prefer (for teaching) to be able to use the standard GUI interface, etc.
Thanks!
Tags:
OLCI support disappeared?
You will need to compile with a bug fix (OLCI mapping offset) or just wait for the next update.
Here too, olci is missing from "Update OC Processors" in the GUI. It is, however, present (and "works for me") in the command-line:
Here too, olci is missing from "Update OC Processors" in the GUI. It is, however, present (and "works for me") in the command-line:
$ install_ocssw.py -h
Usage: install_ocssw.py [options]
Options:
--version show program's version number and exit
-h, --help show this help message and exit
-v, --verbose Print more information while running
-i INSTALL_DIR, --install-dir=INSTALL_DIR
destination directory for install. Defaults to
$OCSSWROOT or "$HOME/ocssw" if neither are given.
-g GIT_BASE, --git-base=GIT_BASE
web location for the git repositories
-b GIT_BRANCH, --git-branch=GIT_BRANCH
branch in the git repositories to checkout
-a ARCH, --arch=ARCH set system architecture (linux, linux_64,
macosx_intel)
-s, --src install source code
-l LOCAL, --local=LOCAL
local directory containing previously downloaded
bundles
-c, --clean Do a clean install by deleting the install directory
first, if it exists
--curl use curl for download instead of wget
--aquarius install Aquarius files
--avhrr install AVHRR files
--czcs install CZCS files
--goci install GOCI files
--hico install HICO files
--meris install MERIS files
--aqua install MODIS Aqua files
--terra install MODIS Terra files
--mos install MOS files
--ocm1 install OCM1 files
--ocm2 install OCM2 files
--octs install OCTS files
--oli install Landsat 8 OLI files
--olci install Sentinel-3A OLCI files <<<<<<<<<<<<
--osmi install OSMI files
--seawifs install SeaWiFS files
--viirsn install VIIRSN files
--direct-broadcast install direct broadcast files
--eval install evaluation sensor files
-
- User Services
- Posts: 1468
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 5 times
OLCI support disappeared?
OLCI support in the OCSSW processing code hasn't gone away, but as you discovered, it is not listed in the GUI interface.
Manual installation with the install_ocssw.py script will work for both v7.3 (assuming you are updated to v7.3.2) and v7.4
If time permits, we may add the checkbox to the GUI with the v7.5 release.
BTW, the geolocation offset issue is really only a problem for processing inland water bodies with significant elevation.
The impact to ocean processing (and geolocation) is quite small...not a lot of terrain to correct there :wink:
Sean
Manual installation with the install_ocssw.py script will work for both v7.3 (assuming you are updated to v7.3.2) and v7.4
If time permits, we may add the checkbox to the GUI with the v7.5 release.
BTW, the geolocation offset issue is really only a problem for processing inland water bodies with significant elevation.
The impact to ocean processing (and geolocation) is quite small...not a lot of terrain to correct there :wink:
Sean
OLCI support disappeared?
Thanks to both of you. I cleaned up some stuff, reinstalled 7.4, and got OLCI data to load. I then rebooted and started the GUI. However, when I point to the xfdumanifest.xml file as input in a downloaded ERR file, I get an error that it is not a valid input mission. I saw another post suggesting to use Oa1_radiance.nc, doesn't work either.
# # WARNING!!! file [path]/S3A_OL_1_ERR____20170617T173647_20170617T182112_20170618T220913_2665_019_041______LN1_O_NT_002.SEN3/Oa01_radiance.nc is not a valid input mission: Mission=null
Should I be starting l2gen some other way? Or does it need to be processed from command line only? Probably a naive question, and I assume there's some simple fix.
Thanks in advance.
# # WARNING!!! file [path]/S3A_OL_1_ERR____20170617T173647_20170617T182112_20170618T220913_2665_019_041______LN1_O_NT_002.SEN3/Oa01_radiance.nc is not a valid input mission: Mission=null
Should I be starting l2gen some other way? Or does it need to be processed from command line only? Probably a naive question, and I assume there's some simple fix.
Thanks in advance.
-
- Subject Matter Expert
- Posts: 259
- Joined: Thu Mar 05, 2009 10:25 am America/New_York
- Been thanked: 2 times
OLCI support disappeared?
the GUI does not support OLCI yet. You have to use l2gen from the command line.
OLCI support disappeared?
Now, as they said, the GUI hasn't support processing of OLCI. You should process OLCI in command-line mode like its installation.
For example, you can use 'l2gen ifile=xfdumanifest.xm ofile=.....'(see the help of l2gen) in terminal in Linux or Mac OS.
Regards
zhigang
For example, you can use 'l2gen ifile=xfdumanifest.xm ofile=.....'(see the help of l2gen) in terminal in Linux or Mac OS.
Regards
zhigang