Forum

Thanks for the reply. If I include the relevant archiveSets I do get a valid response now, which resolves my problem for now. However, I might be overlooking something, but from the API-V2 specification it is totally unclear to me that some constraints parameters are apparently mandatory instead of ...

Just to add, I notice that the same api for NRT3 at https://nrt3.modaps.eosdis.nasa.gov/api/v2/ is still giving responses as expected.

We are using a Python script to routinely find and download VIIRS level 1 data (V??02MOD and V??03MOD specifically) from LAADS DAAC. We use api-v2 as specified at https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/api-v2/specs/content to find which files to download and subsequently use wget ...

Thank you! It seems this has indeed resolved the issue of empty responses. Opening the dataset using xarray turned out to be a different issue related to the groups in the netcdf file and my used version of xarray. For the record: I am now able to open the dataset using updated versions of `pydap` a...

Thanks for letting me know and thanks for looking into this! Please let me know if there is anything I can do from my side.

I am trying to access VIIRS L1B data using OPeNDAP from the LAADS DAAC, as being able to subset the data would greatly reduce the amount of data we need to download for our workflow. (Currently we download full granules using API-V2) Running Python3.10, pydap 3.4.0, xarray 2023.6.9, on a linux machi...