200 likes | 380 Views
US IOOS DMAC Update. Derrick Snowden System Architect Presentation to the DMAC Steering Team 2011-01-17. U.S. IOOS: Program Overview. Global Component Coastal Component (EEZ to the head of tide). 12. 7 Goals, 1 System Improve predictions of climate change and weather
E N D
US IOOS DMAC Update Derrick Snowden System Architect Presentation to the DMAC Steering Team 2011-01-17
U.S. IOOS: Program Overview Global Component Coastal Component (EEZ to the head of tide) 12 • 7 Goals, 1 System • Improve predictions of climate change and weather • Improve the safety and efficiency of maritime operations • Improve forecasts of natural hazards • Improve homeland security • Minimize public health risks • Protect and restore healthy coastal ecosystems • Sustain living marineresources Enhances science and improves decision making
The IOOS program has an architecture of its own to organize and focus efforts. Modeling & Analysis Data Management and Communications Research and Development Outreach and Education Governance and Management Observing Systems IOOS Blueprint for Full Capability v1.0, www.ioos.gov/library/us_ioos_blueprint_ver1.pdf
Major Subsystems within US IOOS Modeling & Analysis • Cross-cutting Considerations • Standardization • Governance/Policies • IT Security/Info Assurance • Configuration Management • Metadata • Data Quality • Service-Level Agreements • Capability Maturity Levels IOOS Data Management and Communications (DMAC) Utility Services Data Access Services Data Assembly Centers Observing Systems 16 components of DMAC identified in the US IOOS Blueprint
At the simplest level, IOOS is trying to help people find and use data. Data/Service Registry Discover Data/Service Register Data/Service Use Data/Service Data/Service Consumer Data/Service Illustrates the Publish, Find, Bind Pattern. OGC Reference Model (OGC 08-062r7)
The model looks easy enough, but what goes inside each oval? How do we do this? Data/Service Registry Discover Data/Service Register Data/Service Use Data/Service ???? Data/Service Consumer Data/Service Illustrates the Publish, Find, Bind Pattern. OGC Reference Model (OGC 08-062r7)
At our last meeting we presented the plan by which we would build/buy the components we felt we needed to implement DMAC. A relatively high level overview of the requirements. Described a hierarchy of components or capabilities that would realize those requirements. Phasing or high level dependencies between the components. Who/When with respect to building the components. How are we doing??? http://www.ioos.gov/library/dmac_implementation_v1_0.pdf
Data Access Service, and the data providers that implement them, form the foundation for the whole network. Sensor Observation Service - SOS Web Map Service - WMS Web Coverage Service - WCS How/Capabilities
The SOS has been our primary focal point for data access services for in situ data types. As is: 3 federal data providers, most RA’s have basic services. Data Formats vary, Server code varies 2012 Expectations: Migration to new data format (SWE 2.0) Investment in commercial software configured to IOOS specifications: reference implementation.
OPenDAP in general and THREDDS in particular have proven very successful as data servers for gridded data types. Regular gridded data well tested, significant recent developments for unstructured grids. Plugin architecture provides for an extensible system: ncISO, ncWMS, WCS, ncSOS, NetCDFSubset, ncStream
The Climate and Forecast conventions for netCDF are designing solutions for in situ sampling geometries making THREDDS viable for more than just gridded data.
Registry and catalog tools enable discovery by users and form the foundation for other central services such monitoring and reporting functions. Relevant technologies: ISO 19115-2 ncISO harvesting Web Accessible Folders ESRI Geoportal Server
Data Catalogs provide a basic browse capability and links back to original data services. Enterprise level view of the system. Support for business functions like our annual inventory. Foundation for more advanced convenience functions like integration across services.
As the system edges toward being operational, monitoring and reporting functions will be important. Basic system monitoring tools now in place. Need some thought on just what we’re monitoring and what we can do about it if there are failures IDEAS?
Client applications and toolkits we will be engaging with in the near term future.
Pilot project plus extensions dealing with biological data. (Species presence absence, and abundance)
Ocean Gliders within IOOS • Significant capability within the IOOS RAs • Activities focused on developing a community • Data standards will be fundamental to the community development
New opportunity with the GHRSST/MISST project. Task 3. Applications within IOOS to improve decision making – Task 3.1. Coral health – Task 3.2. Outreach to IOOS Regional Associations and Users – Task 3.3. Ocean fronts – Task 3.4. Ocean Forecasts – Task 3.5. NWP – Task 3.6. Coupled Modeling and data impact studies
IOOS/DMAC is multifaceted; how best can we utilize the expertise of the steering team? Capabilities Content Governance