Page 1 of 1

Time in file name doesn't match the time coverage start metadata

Posted: Wed Feb 12, 2020 10:38 am America/New_York
by olliegator
Hi,

I have noticed that for some files (e.g. https://oceandata.sci.gsfc.nasa.gov/ob/getfile/AQUA_MODIS.20020704T032005.L2.SST.nc) the time in the file name doesn't match the time_coverage_start global attribute in the metadata: the seconds are different. For other files the match is OK.
Is there a reason for this?

Best regards,
Miguel

Time in file name doesn't match the time coverage start metadata

Posted: Fri Feb 14, 2020 2:47 pm America/New_York
by OB.DAAC - SeanBailey
Miguel,

During the SST reprocessing, we took the opportunity to update the metadata in our database to add new information.
This is a case (and likely not an isolated one) where the reprocessed metatdata run resulted in a more correct start time for the scene (which is reflected in the time_coverage_start attribute), but the filename generation had already grabbed the previously recorded start time.  If that file were reprocessed now, it would have a filename consistent with the time_coverage_start attribute.

Sean