Welcome to the Earthdata Forum! Here, the scientific user community and subject matter experts from NASA Distributed Active Archive Centers (DAACs), and other contributors, discuss research needs, data, and data applications.
by captlen » Mon Aug 01, 2022 8:10 am America/New_York
Prior to July 29,22 my 616 subscription produced Modis Aqua K490 such as the following for years: A2022201074500.L2_LAC_OC.NC Now on 7-28-22 files have changed to:
AQUA_MODIS.20220724T165001.L2.OC.NRT.nc. These files are unusable with my octave and Matlab scripts. Was this changed an error?
This is not an error. NRT files (...OC.NRT.nc) are near real-time and provide a quicklook of data before the ancillary files needed to refine the data are available. After the ancillary files are available, they are used to create the refined product which is named "...OC.nc". Regarding the beginning of the filenames, that is not an error either. We are changing our filenaming convention. As data are reprocessed, they will be named by the newer convention of Mission.Sensor.yyyyThhmmss... (Aqua.MODIS.20220724T165001).
by captlen » Mon Aug 01, 2022 11:37 am America/New_York
I am now receiving NRT data from my subscription 616. Will these data be reprocessed into similar data that were usable with my octave and matlab scripts or do I have to rewrite these scripts to extract the K490 data?
Your script will need to be ready to accept the new naming convention if you intend to pull data that has been reprocessed to R2022. Before that reprocessing, the previous naming format should be expected by your script.
oc.nc files are always generated after ancillary files are ready. This has nothing to do with reprocessing, so the NRT files (oc.nrt.nc) are available 'now' but there will also be an oc.nc file generated as soon as possible. If you are changing your script to accept NRT files, but you *need* the refined product, you should wait for the refined product, rather than change your script to accept NRT files.