ERDDAP Transition Project DMAC Annual Meeting 2018 May
- Slides: 8
ERDDAP Transition Project DMAC Annual Meeting 2018 May 22
ERDDAP Transition Background ● IOOS is looking to ERDDAP as the platform of the future for distributing ocean observations ● SOS services will continue to be endorsed as DMAC-compliant, but plan for migration from SOS to ERDDAP in the future ● ERDDAP allows a degree of flexibility in implementing data services; project goal is to narrow sufficiently in order provide client interoperability ● This project will develop guidance and requirements for data formatting and metadata, and plan for a future transition from SOS to ERDDAP 2
ERDDAP Transition High Level Goals ● Interoperability of ERDDAP services across the DMAC enterprise ● Understand ERDDAP limitations for data types and plan to mitigate ● Minimize transition impact to end users of IOOS services ● Develop clear guidance and requirements for service configuration ● Improve automation of national DMAC system ● Reach new users ● Collaborate as a community to overcome issues and implement solutions 3
ERDDAP Transition Project 4
IOOS DMAC Data Distribution 5
Extra Slides 6
DMAC Data Discovery 7
ERDDAP Data Server Project ERDDAP Strengths: ● Act as broker between clients (R, Python, Matlab) and source data formats (CSV, net. CDF) ● Query and request the same source dataset, with same filters, in a variety of output formats by simple parameter change ● Standard query interface, regardless of source data format, with ‘fuzzy’ or interpolated parameters (eg. give me the time closest to ‘ 2017 -10 -17: 10: 00’, or ‘now - 5 minutes’) ● Users don’t need to spend time converting downloaded datasets from one format to another ● Data publishers using ERDDAP can enhance native data set metadata in the configuration/load process 8