Open bhbraswell opened 6 years ago
@ircwaves if this looks like a real thing then you can assign it to me if you want.
The error messages here are lost in the noise but they are all about asking for AOD data before its latency window has passed. I believe we agreed that latency metadata should be ignored for fetch purposes, but maybe used to inform the error messages.
For MOD08, requested dates, 2018-05-31 - 2018-05-31, are not in the valid range of 2000-02-18 - 2018-05-28.
If you want to get into that, it seems like a reasonable change that might help NRT processing streams. The question becomes to bail on processing, or to use LTA(D) composites and march on? Seems like you'd want submit reprocessing jobs for each scene that was corrected with an LTA(D) once the AOD data was available.
If you don't want to get into that, I'd say this can be closed.
This is different from #490 I think.
And forgive the lengthy TS below but I believe that this case should produce a resulting product that is atmospherically corrected based on the composite long term means. The S2 data are available, but the AOD are not.
It calculates ref-toa then fails with trying to read too large an array from AOD.