US IOOS DMAC Update

Derrick SnowdenSystem Architect

Presentation to the DMAC Steering Team 2011-01-17

U.S. IOOS: Program Overview

12

Global ComponentCoastal Component (EEZ to the head of tide)

2Enhances science and improves decision making

7 Goals, 1 SystemImprove predictions of climate change and weatherImprove the safety and efficiency of maritime operationsImprove forecasts of natural hazardsImprove homeland security Minimize public health risks Protect and restore healthy coastal ecosystemsSustain living marine resources

The IOOS program has an architecture of its own to organize and focus efforts.

3

Observing Systems

Modeling & Analysis

Data Management and Communications

Gov

erna

nce

and

Man

agem

ent

Res

earc

h an

d D

evel

opm

ent

Out

reac

h an

d E

duca

tion

IOOS Blueprint for Full Capability v1.0, www.ioos.gov/library/us_ioos_blueprint_ver1.pdf

Major Subsystems within US IOOS

4

IOOS Data Management and Communications (DMAC)

Observing Systems

Data Assembly Centers

Data Access Services

Utility Services

Modeling & Analysis

16 components of DMAC identified in the US IOOS Blueprint

Cross-cutting Considerations • Standardization• Governance/Policies• IT Security/Info Assurance• Configuration Management• Metadata• Data Quality• Service-Level Agreements• Capability Maturity Levels

At the simplest level, IOOS is trying to help people find and use data.

5Illustrates the Publish, Find, Bind Pattern. OGC Reference Model (OGC 08-062r7)

Discov

er D

ata/S

ervic

e Register Data/ServiceData/Service Registry

Use Data/Service

Data/ServiceData/Service Consumer

The model looks easy enough, but what goes inside each oval? How do we do this?

6Illustrates the Publish, Find, Bind Pattern. OGC Reference Model (OGC 08-062r7)

Use Data/Service ????

Discov

er D

ata/S

ervic

e Register Data/ServiceData/Service Registry

Data/ServiceData/Service Consumer

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???

7http://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.

8

How/Capabilities

Sensor Observation Service - SOSWeb Map Service - WMSWeb Coverage Service - WCS

The SOS has been our primary focal point for data access services for in situ data types.

9

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.

10

Plugin architecture provides for an extensible system: ncISO, ncWMS, WCS, ncSOS, NetCDFSubset, ncStream

Regular gridded data well tested, significant recent developments for unstructured grids.

The Climate and Forecast conventions for netCDF are designing solutions for in situ sampling geometries making THREDDS viable for more than just gridded data.

11

Registry and catalog tools enable discovery by users and form the foundation for other central services such monitoring and reporting functions.

12

Relevant technologies:ISO 19115-2ncISO harvestingWeb Accessible FoldersESRI Geoportal Server

Data Catalogs provide a basic browse capability and links back to original data services.

13

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.

14

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.

16

Pilot project plus extensions dealing with biological data. (Species presence absence, and abundance)

Ocean Gliders within IOOS

17

• 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.

18

Task 3. Applications within IOOS to improvedecision making– Task 3.1. Coral health– Task 3.2. Outreach to IOOS RegionalAssociations and Users– Task 3.3. Ocean fronts– Task 3.4. Ocean Forecasts– Task 3.5. NWP– Task 3.6. Coupled Modeling and data impactstudies

Quality Control Placeholder

19

IOOS/DMAC is multifaceted; how best can we utilize the expertise of the steering team?

20

Capabilities

Governance

Content