Forum

Hi there! I’ve seen in the forum announcements that OB.DAAC is beginning to transition from on-site servers to cloud services. I’d attach a link but the announcement appears to come and go at random… Will the on-site to cloud changes impact the “file search api”? If so roughly when will these change...

Good Morning! I upgraded from OCSSW 2025.V0 to 2025.V1, after which I started getting a new error message. I'm calling a command of the form: l2gen maskland=0 proc_cloud=0 maskcloud=on cloud_thresh=0.1 maskhilt=0 maskstlight=0 resolution=1000 gas_opt=8 l2prod=rhos_NNNN,rhos_MMMM,rhos_PPPP ifile=S202...

I'm bumping this thread (I think it got lost over the holiday weekend)

Greetings Earth-data-lings! We’re consistently getting an error when we try to process NPP L1A to L2 data using l2gen. We’re trying to run a command of the following form: l2gen maskland=0 proc_cloud=0 maskcloud=on cloud_thresh=0.1 maskhilt=0 maskstlight=0 resolution=1000 gas_opt=8 l2prod=rhos_NNNN,...

I was able to find the issue with the help of friendly folks at laads-support (thank you guys!) nrt3 (and nrt4) don't recognize a token unless the earth data account "owning" it has been authorized. To get the authorization you need to log into nrt3 (and nrt4 separately) using your browser...

Thank you for looking into it! I replied to your email. If I find it is something I'm doing wrong I'll post it here so other people can be less stumped when it comes up

-Andrew L.

Sean - thank you, that worked perfectly!

I’m having an issue with downloading data from nrt3 that I’m hoping someone reading this can help with. When I use a newer earthdata token (expires on 6/9/2025) it fails with a response saying I need to be logged into earthdata: $ wget -v --no-use-server-timestamps --timeout=20 -O /scratch/lance-to-...

We are upgrading from a very old version of SeaDas / ocssw to a new one and are experiencing some trouble. When we call a command of the form l2gen maskland=0 proc_cloud=on maskcloud=on cloud_thresh=0.1 maskhilt=0 maskstlight=0 resolution=1000 gas_opt=8 l2prod=rhos_XXX,rhos_YYY,rhos_ZZZ ifile=S20250...

I'm getting the identical error when attempting to process the MODISA granule from 2025-01-01 20:15:00

Whatever the issue is it is still present. Do you have any further debugging suggestions, please?