Data Assembly & Systems Technical Advisory Tag (DAS-TAG) Breakout Session Tues 22 nd June.

Group for High Resolution Sea Surface Temperature Issues that need resolving 1.GDS 2.0 document layout 2.GDS 2.0 version control 3.GDS 2.0 external review 4.netCDF 3 or 4? 5.ISO implementation 6.Metrics 7.GDAC interface issues 8.MDBs 9.Filename convention 10.Missing data + Book Captain’s issues

Group for High Resolution Sea Surface Temperature Issue 1: GDS 2.0 Layout - Current GDS 2.0 Technical Spec (Casey/Donlon) –Overview (Robinson) –Conventions (Casey) –L2P specification (Donlon) –L3 specification (Le Borgne) –L4 specification (Gentemann) –GMPE specification (Martin) –Metadata specification (Armstrong) User Manual (Jorge/Andrea) ICD (Bingham)

Group for High Resolution Sea Surface Temperature Issue 1: GDS 2.0 Layout - Proposed Vol 1: Project Overview (Donlon) Vol 2: Technical Product Specification (Casey/Donlon) –How data providers make core products Vol 3: Data Services (Bingham) –How software system interoperate & common approach User Manual ( PO? AU-TAG? Need more input from real-life users! ) Vols 1, 2 and 3 conform to same (current) layout User Manual – no constraint on format (wiki or pdf/doc)

Group for High Resolution Sea Surface Temperature Issue 2: Version Control How should we control the version? Proposal: Hand off Vols 1-3 to GHRSST- PO. All updates coordinated through PO and approved by Volume Lead Author. User manual maintained as a wiki –Editable by anyone or just members of the science team?

Group for High Resolution Sea Surface Temperature Issue 3: External GDS 2.0 Review How should we conduct the external review? Open questions: –Who are the stakeholders? –Coordinated through the PO? –Single sent to stakeholders? –What level of detail are we requesting? –Do we need a template for collecting input? –Timeline Sep 30 send out for comment Dec 31 receive feedback Feb finalize –How should we respond to inputs?

Group for High Resolution Sea Surface Temperature Issue 4: NetCDF 3 or 4? Need to decide Per Dave Poulter – do we need to reformat specs for improved efficiency? (e.g. float to short) Related issue – Chelle notes L4 can be very large for 1km datasets –Would NetCDF 4 resolve this issue? –Recommendation from Chelle: For the error field, it seems like a byte will suffice rather than short, should we change to byte? Mask variable specifies ice mask, is sea_ice fraction still necessary?

Group for High Resolution Sea Surface Temperature Issue 5: ISO implementation How will we implement this? Any impact on data search and access interfaces?

Group for High Resolution Sea Surface Temperature Issue 6: Metrics collection What metrics do we need? –How often? Monthly? –Number and volume of granules downloaded by FTP, OpenDAP and other services by each dataset. –Number of unique users (for data and information) –Should we (can we) be sharing/comparing ip-address? Who needs to provide the information? –GDAC and LTSRF for sure –RDACs, PO Should GHRSST-PO be the maintainer of the consolidated metrics? –Should the PO be reporting metrics on a monthly basis to stakeholders? Is MetricCasting the right approach? –How would RDACs want to send information each month?

Group for High Resolution Sea Surface Temperature Issue 7: Multiple files sent to the GDAC GDAC requests that DAS-TAG takes a stance on REMSS sending multiple files.

Group for High Resolution Sea Surface Temperature Issue 8: MDBs Nice report from Steiner that identifies 7 MDBs, the content, formats and access mechanisms Impossible for GHRSST to define a common approach to MDBs. Suggestion: –Write a best practices document –Recommend a data access web service interface spec –Document all available MDBs

Group for High Resolution Sea Surface Temperature Issue 9: Filename convention - - _GHRSST v -fv NAVO-L2P_GHRSST-SSTblend-AVHRR17_L-SST_s0123_e0135-v02.0-fv01.0.nc REMSS-L3C_GHRSST-SSTsubskin-TMI-tmi_ rt-v02.0-fv01.0.nc UKMO-L4_GHRSST-SSTfnd-OSTIA-GLOB-v02.0-fv01.0.nc When multiple files exist for a given day the “Additional Segregator” makes a file unique Strong preference by AU-TAG to include time as a required field in in the filename

Group for High Resolution Sea Surface Temperature Issue 10: Missing Data Reports that data are missing at the GDAC –Are they also missing at the LTRSF? –Do we have tools that scrape the master repositories to perform gap analysis and ensure valid data urls?

Group for High Resolution Sea Surface Temperature Anything else?