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

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
Post Reply
olliegator
Posts: 4
Joined: Tue Jun 28, 2005 1:53 pm America/New_York
Answers: 0

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

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

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

Filters:

OB.DAAC - SeanBailey
User Services
User Services
Posts: 1485
Joined: Wed Sep 18, 2019 6:15 pm America/New_York
Answers: 1
Been thanked: 5 times

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

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

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

Post Reply