90 likes | 221 Views
PO.DAAC MEaSUREs Report: Best Practices. David Moroni PO.DAAC Data Engineer david.f.moroni@jpl.nasa.gov With input from the PO.DAAC Data Engineering Team and Andrew Bingham (Project Manager). Background: What is PO.DAAC?.
E N D
PO.DAAC MEaSUREs Report: Best Practices David Moroni PO.DAAC Data Engineer david.f.moroni@jpl.nasa.gov With input from the PO.DAAC Data Engineering Team and Andrew Bingham (Project Manager)
Background: What is PO.DAAC? • PO.DAAC is the NASA Data Center for Physical Oceanography. Over 600 datasets primarily related to: • Sea Surface Temperature (AMSR-E, MODIS, TMI, Pathfinder AVHRR) • Ocean Topography (TOPEX, Jason-1, OSTM/Jason-2) • Ocean Winds (NSCAT, QuikSCAT, ASCAT) • Ocean Surface Currents (OSCAR) • Gravity (GRACE/Tellus) • PO.DAAC has recently developed a distribution model to enable community evaluation and approval for a dataset • Known as “Preview” • PO.DAAC is also the Global Data Assembly Center (GDAC) for the Group for High Resolution Sea Surface Temperature (GHRSST) • International consortium of SST data providers • Common data assembly standards and formats • Pixel-level error estimates
Recent Developments • Data Management and Archive System (DMAS) deployed in operational phase in 2009. • Product Roll-Out GUI tool to facillitate dataset and collection-level metadata for DMAS, GCMD/DIF, and ECHO/WIST. • Level 2 Subsetter/Dataminer Deployed in Beta (June 2010) • New Web Portal enables faceted dataset search capabilities and consistent dataset metadata browsing through DMAS database. • Exploring enhanced interoperability through VODC (Rob Raskin), OPeNDAP, and metadata standardization (CF, ECHO/WIST, GCMD, ISO 19115). • Recent aim to facilitate the climate and research community through improved and more standardized documentation, metadata, and traceability (DOI).
MEaSUREs Datasets Available • Cross-Calibrated Multi-Platform (CCMP) Ocean Surface Wind Velocity • PI – Bob Atlas (NOAA/AOML); Co-I – Joe Ardizzone (GSFC). • Distributed in “Preview” under REASON in August 2004. • Transitioned to MEaSUREs in February 2009; Released as “Open” in May 2009. • Multi-sensor Ultra-high Resolution (MUR) Global SST • PI – Mike Chin (JPL), GHRSST • North American regional coverage, released June 29, 2010 • Global coverage to be released in late 2011 • ISO 19115-2 metadata model to be implemented (2011) • GRACE Tellus Products for Hydrology and Oceanography • GRACE PI – Victor Zlotnicki (JPL) • Transitioned from REASoN to MEaSUREs in January 2009.
MEaSUREs Datasets Incoming • Integrated Multi-Mission Radar Altimeter Data for Climate Research • PI - Richard Ray (GSFC) • Provides cross-calibrated multi-instrument sea surface height data beginning from TOPEX-era • Data delivery is underway • Expected availability is December 2010
Best Practices • Automated metrics collection. • Providing a path for new PI-provided datasets to become evaluated by the user community. • An in-house team of scientists to assist in evaluating data products, metadata/documentation practices, and serving as proxy-user feedback (meeting bi-weekly). • An annual User Working Group (UWG) to assess overall scope of PO.DAAC’s accomplishments and future goals. • Staying in regular contact with the dataset providers to ensure satisfaction on current and future developments. • Dataset updates via email and web portal. • Annual user feedback surveys.
Areas for Improvement • An optimized dataset roll-out procedure to ensure quality and continuity is maintained for documentation, metadata, interoperability, and traceability. Work is underway. • A new/improved way to provide standardized identification for specific datasets and documents to support citation in scientific journals for enhanced traceability. Exploring DOIs. • Improved metrics reporting capabilities to extend beyond FTP usage. • Improved timeliness on metrics reporting.
Lesson Learned: GRACE/Tellus • GRACE/Tellus (PI: V. Zlotnicki, JPL) • Data not directly distributed by the DAAC • A majority of data is distributed through HTTP, rather than FTP. • Metrics collection less straightforward, attempted using Google Analytics, which couldn’t resolve unique host names and HTTP usage; resulted in metrics delayed by 1 year (November 2009 until present) • Data to be migrated to DMAS by 2011; should solve most of metrics collection issues