Forum

Great minds think alike

That worked great! I figured it was something obvious to someone who is more of an expert than me.

Thank you Sean!!!!!

Thank you for your reply! It's good to know that you're planning to keep the file search API working. I also definitely understand not being able to predict impending changes, especially with the current situation in the federal government. Thank you for all that you do to help us users, it is very ...

Sean, Thank you for your reply, I'll try it once I get some VIIRS data far enough through the system to be able to test it. I'd like to make a suggestion, please, that future versions of l2gen by default look for the most recent calibration files in the appropiate directory rather than it being set ...

Thank you Sean! I tried running the command calibrate_viirs ifile=S20250423143600-L1A-NPP-OBPG.nc l1bfile_img=S20250423143600-L1B-NPP-OBPG.nc Then the usual l2gen maskland=0 proc_cloud=0 maskcloud=on cloud_thresh=0.1 maskhilt=0 maskstlight=0 resolution=1000 gas_opt=8 l2prod=rhos_MMMM,rhos_NNNN,rhos_...

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...