Page 1 of 2
File naming convention change
Posted: Tue Oct 22, 2019 12:09 pm America/New_York
by jstum
Hello,
Following the ocean color announcement by Sean Bailey on file naming change this day, I would like to know if you could provide a date for the presence of the new filenames on the Direct Data Access as far as the Real time processing is concerned.
I'm particularly interested in near real time processing of VIIRS L1A, and MODIS SST.
Thank you,
Jacques
File naming convention change
Posted: Wed Oct 23, 2019 9:28 am America/New_York
by OB.DAAC-EDL - SeanBailey
Jacques,
The VIIRS SST names will change with the reprocessing which is scheduled to begin on 28 Oct 2019.
There is no date set for the L1A. It will not happen until the next release of the VIIRS L1 code, but no schedule is set for that.
Sean
File naming convention change
Posted: Mon Oct 28, 2019 10:16 am America/New_York
by btupper
Ahoy,
Would you clarify for us the timestamp convention described in following?
https://oceancolor.gsfc.nasa.gov/docs/filenaming-convention/ The docs say "YYYYMDD[THHMMSS]: ISO8601 time format" (which I think maybe is missing an "M"). On the other hand, the (nice!) examples shown in the table for Level 3 look like they are "YYYYjjj". Should we be switching to YYYYMMDD? Or do we stick with YYYYjjj?
Thanks!
Ben
File naming convention change
Posted: Mon Oct 28, 2019 1:59 pm America/New_York
by OB.DAAC-EDL - SeanBailey
Ben,
Nice catch :) Yep, we missed an 'M' and buggered most of the L3 examples. Those responsible have been flogged.
The page has been corrected.
The new format is YYYYMMDD - the YYYYjjj format is going away.
Sean
File naming convention change
Posted: Mon Oct 28, 2019 3:57 pm America/New_York
by btupper
Thanks, Sean.
I confess that my inner sloth hoped that the dates would remain in the "classic" style making the transition pretty easy. Ah, well.
Cheers,
Ben
File naming convention change
Posted: Mon Oct 28, 2019 7:34 pm America/New_York
by btupper
Hi again,
The THREDDS catalog is currently organized by day of year ala "
https://oceandata.sci.gsfc.nasa.gov/opendap/MODISA/L3SMI/2011/001/catalog.xml". Is it safe to assume that the resource paths will stay the same even if the filename convention changes?
Thanks!
Ben
File naming convention change
Posted: Wed Oct 30, 2019 10:21 am America/New_York
by OB.DAAC-EDL - SeanBailey
Ben,
'Tis rarely safe to assume, and in this case it would be an incorrect assumption. The paths on the OPeNDAP server will change to be YYYY/MM/DD when the filenames change to the ISO8601 date format.
Sean
File naming convention change
Posted: Wed Oct 30, 2019 11:01 am America/New_York
by btupper
Thanks, Sean. I'm glad I asked - it's back to the drawing board for me.
File naming convention change
Posted: Wed Oct 30, 2019 3:30 pm America/New_York
by btupper
Hmmmm. Is there any chance a test THREDDS catalog could be set up before the transition? It wouldn't need to host much data - just enough to allow piloting the new paradigm.
File naming convention change
Posted: Wed Oct 30, 2019 4:53 pm America/New_York
by OB ODPS - jgwilding
Ben,
Are you just looking for a sample directory on our OpenDAP server that is organized by year-month-day? It would actually be set up like this:
MISSION/L3SMI/YYYY/MMDD
ex:
VIIRS/L3SMI/2018/0703
Would such a sample directory need to contain files with the new naming convention or would it not matter?
john