Forum

Hi @LP DAAC - afriesz

Thanks for the update! Is this fix related to the "oops" error? I am still getting that when calling the STAC api.

Hi Alicia would you happen to have any updates on the "oops" issue in this thread: viewtopic.php?t=5922

I'm still encountering this issue currently, which makes the LPCloud STAC unusable. Happy to provide any data points, etc.

Thank you, is there an ETA on the STAC fixes? It would help inform whether to proceed with the workaround, or wait for updates. Cheers.

@dgolon I tested various search param settings. I noticed the same behavior - that longer periods (> 6 months) will result in the "oops" API error. My MRE (small section of Central park, 9 months): results = catalog.search( bbox=[-73.9819, 40.7681, -73.9580, 40.7851], collections=["HL...

I am facing the same issue, seeing most datetime ranges returning the same API error. Additionally, was there some recent change that resulted in the search API datetime param type changing from array to string? Would be great to know where I can stay up to date with these API changes. Thanks for ki...