1 / 8

GDS Technical Advisory Group: GDS-TAG Done in collaboration with the DM-TAG

GDS Technical Advisory Group: GDS-TAG Done in collaboration with the DM-TAG. Specifications of level 4 data products Review and consensus on GDS-V1.7 document including L2P specs. L2P specifications and revisions. Major issues discussed Use of DT_analysis in L2P-core data products

kamaria-gyasi
Download Presentation

GDS Technical Advisory Group: GDS-TAG Done in collaboration with the DM-TAG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GDS Technical Advisory Group: GDS-TAGDone in collaboration with the DM-TAG • Specifications of level 4 data products • Review and consensus on GDS-V1.7 document including L2P specs

  2. L2P specifications and revisions • Major issues discussed • Use of DT_analysis in L2P-core data products • Consensus DT analysis will be part of L2P, but not L2P_core • Consensus on gridding resolution for L2P_GRIDDED data sets (more on this later in L3 discussions) • Specification of time units (long versus short) • Deciding on specific conventions • Eg: signed versus unsigned bytes

  3. L4 specifications • Specification of filenaming conventions complete • Optional part of L4 filename is now required. RDAC provider to refer to a unique (OSTIA) product. : • Revisions of all tables to reflect standard naming conventions

  4. Future modifications to GDS should include • L3P products • DT_analysis • Addition of experimental fields • Eg: Diurnal Warming?

  5. DT_analysis • Decision made to keep DT_analysis in delayed mode products, but not necessarily in the L2P_core. • Discussion point. Is there a reason for DT_analysis to be consistent? Currently based on previous day’s analysis. If that is unavailable, based on climatology for that day.

  6. ISSUES • Signed versus unsigned byte convention • Experimental fields • Uniformity of SSES across all products. • Review of confidence versus rejection flags • Eg: Land mask embedded in confidence fields and not rejection fields.

  7. Level 4 Time Tag for Analyzed Field • The value should be chosen to most closely represent the time at which the analysis is valid. This may be the mid-point of the nominal time window for observations from which the analysis has been derived, but is dependent on the L4 analysis system. Essentially L4 time should be defined as the reference time of the analysis, and should be the beginning of the nominal time window for observations from which the analysis represents.

  8. Conclusions • DT analysis • Users keep asking two questions: • Where is temperature measured (depth) • Does it have a diurnal correction • Experimental Fields • One focus area for GDS_V2.0 should be L3 specifications • Collated and super collated • Naming convention L3P versus L2P_GRIDDED

More Related