Hi Matthew,
Please see below from a data manager:
Infrequent and unexpected data gaps can be caused by a number of issues, including delays in being able to access the input and/or ancillary data needed to generate the products. Since the provider, in this case HLS, is getting its input data upstream (Sentinel and Landsat), any delays or production issues in those data streams will directly affect HLS processing. The LP DAAC receives reports containing a list of the files sent to us by the SDS and placed on their https server or in their s3 bucket. The frequency of these reports may vary by provider. HLS sends them daily. Other providers may choose a different schedule. These reports will list the granule files that have been sent to the LP DAAC since the last report was generated. The reports will contain information including collection short name, collection version ID, granule id, granule filename, file size, timestamp and (optional) checksum value.
Although these data gaps are quite infrequent, in the case that they persist over a larger period of time, the provider generally alerts the LP DAAC and we are able to alert user’s via news announcements. In this case, we reached out to the HLS team and they acknowledged the gap and that it would be filled in momentarily.
Thanks,
Brett
Please see below from a data manager:
Infrequent and unexpected data gaps can be caused by a number of issues, including delays in being able to access the input and/or ancillary data needed to generate the products. Since the provider, in this case HLS, is getting its input data upstream (Sentinel and Landsat), any delays or production issues in those data streams will directly affect HLS processing. The LP DAAC receives reports containing a list of the files sent to us by the SDS and placed on their https server or in their s3 bucket. The frequency of these reports may vary by provider. HLS sends them daily. Other providers may choose a different schedule. These reports will list the granule files that have been sent to the LP DAAC since the last report was generated. The reports will contain information including collection short name, collection version ID, granule id, granule filename, file size, timestamp and (optional) checksum value.
Although these data gaps are quite infrequent, in the case that they persist over a larger period of time, the provider generally alerts the LP DAAC and we are able to alert user’s via news announcements. In this case, we reached out to the HLS team and they acknowledged the gap and that it would be filled in momentarily.
Thanks,
Brett
Statistics: Posted by LP DAAC - lien — Thu Mar 28, 2024 9:26 am America/New_York