Search found 270 matches
- Wed May 18, 2022 10:03 am America/New_York
- Forum: Questions/Comments
- Question: contours of bathymetry required
- Replies: 12
Re: contours of bathymetry required
You can add contours in SeaDAS as described in the previous post. Note that you can only make contours on the selected band. So since you want contours of Bathymetry overlaid on chlor_a, you will need to: 1. Load VIIRS file. 2. Create bathymetry (which creates a band called "bathymetry" 3...
- Tue May 17, 2022 5:50 pm America/New_York
- Forum: Questions/Comments
- Question: L8 - OLI
- Replies: 1
Re: L8 - OLI
Amita,
Your OCDATAROOT should be set to /usr/local/cb/ocssw/share while your OCSSWROOT is /usr/local/cb/ocssw/
Bing
Your OCDATAROOT should be set to /usr/local/cb/ocssw/share while your OCSSWROOT is /usr/local/cb/ocssw/
Bing
- Mon May 16, 2022 3:42 pm America/New_York
- Forum: Questions/Comments
- Question: contours of bathymetry required
- Replies: 12
Re: contours of bathymetry required
You don't need OCSSW to calculate Bathymetry, so you can ignore the warnings for now.
Are you able to create Bathymetry with newly installed SeaDAS?
Are you able to create Bathymetry with newly installed SeaDAS?
- Mon May 16, 2022 11:26 am America/New_York
- Forum: Questions/Comments
- Question: contours of bathymetry required
- Replies: 12
Re: contours of bathymetry required
To install and process SeaDAS OCSSW in Windows, you need to set up the client-server configuration following the instructions here https://seadas.gsfc.nasa.gov/client_server/
If you have issues with client-server model, please start a new question on the forum.
If you have issues with client-server model, please start a new question on the forum.
- Fri May 13, 2022 3:37 pm America/New_York
- Forum: Questions/Comments
- Question: contours of bathymetry required
- Replies: 12
Re: contours of bathymetry required
What version of SeaDAS are you using? Please do SeaDAS-OCSSW -> SeaDAS/System Info and post the result here.
There is a copy of ETOPO1_ocssw.nc in $OCDATAROOT/common. You can manually copy it to ~/.seadas8/seadas-bathymetry-operator/auxdata. That might work.
There is a copy of ETOPO1_ocssw.nc in $OCDATAROOT/common. You can manually copy it to ~/.seadas8/seadas-bathymetry-operator/auxdata. That might work.
- Thu May 12, 2022 1:25 pm America/New_York
- Forum: Questions/Comments
- Question: contours of bathymetry required
- Replies: 12
Re: contours of bathymetry required
You can browse VIIRS L2 files here -- https://oceancolor.gsfc.nasa.gov/cgi/browse.pl or directly download the files here --https://oceandata.sci.gsfc.nasa.gov/directaccess/ 1. load the L2 file (eg. V2019096034800.L2_JPSS1_OC.nc) in SeaDAS and open the chlor_a band 2. click the Bathymetry icon on the...
- Mon May 09, 2022 2:28 pm America/New_York
- Forum: Questions/Comments
- Question: Custom ancillary tree and db
- Replies: 1
Re: Custom ancillary tree and db
Thanks for your suggestion. We'll add an --ofile option to getanc, so users can name their *.anc files. It will be in the next tag of OCSSW
- Thu May 05, 2022 1:15 pm America/New_York
- Forum: Questions/Comments
- Question: modis_atteph.py is downloading the wrong ATT/EPH pair
- Replies: 7
Re: modis_atteph.py is downloading the wrong ATT/EPH pair
Dmitry,
I have to clarify that ocssw/scripts/modis_atteph.py (V2019.3) calls an old api that returns 1 when ATT files are non optimal.
The new ocssw/bin/modis_attpeh (V2022.0) calls a new api that returns 0 even when ATT/EPH files are non optimal.
Bing
I have to clarify that ocssw/scripts/modis_atteph.py (V2019.3) calls an old api that returns 1 when ATT files are non optimal.
The new ocssw/bin/modis_attpeh (V2022.0) calls a new api that returns 0 even when ATT/EPH files are non optimal.
Bing
- Wed May 04, 2022 4:31 pm America/New_York
- Forum: Questions/Comments
- Question: modis_atteph.py is downloading the wrong ATT/EPH pair
- Replies: 7
Re: modis_atteph.py is downloading the wrong ATT/EPH pair
Yes, an exit status < 4 indicates the presence of some kind of ATT/EPH data, sometimes NRT, less than optimal.
- Mon May 02, 2022 3:11 pm America/New_York
- Forum: Questions/Comments
- Question: Mismatch between input geographic limits and output of l2gen for MODISA using V2022.0
- Replies: 10
Re: Mismatch between input geographic limits and output of l2gen for MODISA using V2022.0
Hello bijaylaxmi, I tried your file A2005335192500.L1A_LAC with V2022.0. Here is what I did 1) modis_GEO on A2005335192500.L1A_LAC -> AQUA_MODIS.20051201T192500.GEO.hdf 2) extractor on A2005335192500.L1A_LAC with (SWlon=-92.5, SWlat=26, NElon=-87.5, NElat=31) -> AQUA_MODIS.20051201T192500.L1A.sub.nc...