1. Jeff de La Beaujardière, PhD Carmel Ortiz NOAA IOOS Program Office Integrated Ocean Observing System (IOOS)

2. IOOS program overview IOOS high-level architecture –Observing Systems –Data Assembly Centers –Data Access Services Supported Standards & Formats –Utility Services –Modeling and Analysis Tools IOOS - NextGen WIDB linkages Schedule & milestones Outline 2

3. IOOS is a system of systems, including: –data assembly centers/data providers –archives –regional associations –service providers Add one or more standardized services at (or near) each system –cf. NextGen service adapter alternative approaches Implement shared registry/catalog/portal components Leverage existing infrastructure –public internet, WMO GTS, NOAAnet? IOOS is not building a new system 3

4. 8 5 6 11 2 4 10 3 7 9 1 IOOS Partners: Regional Associations (RAs) IOOS Regional Component A network of 11 regional coastal ocean observing systems that meet national and regional needs for local ocean observations, data management, and modeling 1 national partnership providing sensor validation/verification 1.Alaska Ocean Observing Systems (AOOS) 2.Caribbean Regional Association (CaRA) 3.Central and Northern California Coastal Ocean Observing System (CeNCOOS) 4.Gulf Coastal Ocean Observing System (GCOOS) 5.Great Lakes Observing System (GLOS) 6.Mid-Atlantic Coastal Ocean Observing System Regional Association (MACOORA) 7.Northwest Association of Networked Ocean Observing Systems (NANOOS) 8.Northeast Regional Association of Coastal Ocean Observing Systems (NERACOOS) 9.Pacific Islands Ocean Observing System (PacIOOS) 10.Southern California Coastal Ocean Observing System (SCCOOS) 11.Southeast Coastal Ocean Observing System Regional Association (SECOORA) 12.Alliance for Coastal Technologies (ACT) {Sensor V & V} 12 Meeting National missions through: –Expanded observations and modeling capacity –Connections to users and stakeholders –Implementation of national data standards –Sensor validation/verification –Products transitioned to other regions and to National operations

5. IOOS Partners: Federal Agencies 5 Legislation: Integrated Coastal and Ocean Observation System Act Directs President to establish a National Integrated Coastal and Ocean Observation System Identifies NOAA as Lead Federal Agency Authorizes appropriation of “such sums as are necessary” through 2013 Agency partners: closest ties with NSF (OOI/CI) USACE (WL data) USGS (WaterML 2.0) Navy (METOC) EPA (NWQMN)

6. IOOS is part of a global framework We are starting to establish technical linkages to ensure interoperability –Australia: IMOS (Integrated Marine Observing System) –Europe: MyOcean –WMO: WMO Information System (desired) IOOS Partners: International 6 Global Ocean Observing System GEOSSGOOSIOOS

7. DMAC Data Management and Communications Data Management Modeling & Analysis Web Portal Client Libraries Analysis Tools System Monitor Forecast Models Observing Systems Moored Buoys Fixed Stations Samples Moving Platforms RadarSatellite Data Assembly Centers Real-Time Biological Archives Model Outputs Utility Services Visualization Conversion Data Integration Catalog Registry Computational Viewpoint from Reference Model for Open Distributed Processing (RM-ODP) Component Types Needed for IOOS Data Access Services SubscriptionAlertPull Individual Features Regular Grids Unstructured Grids Undersea Imagery … … … … … Service Gateway Maps & Images Workflows Notification Surveys GIS Framework

8. Observing Systems 8 Direct support for –in situ sensors at regional associations: buoys, fixed stations, gliders (AUV: autonomous underwater vehicle) –Real-time data from RAs onto WMO GTS via NDBC –Regional-scale models –Coastal high-frequency radar (HFR) Access to observations from –NWS Met/Ocean buoys –DART (Deep Ocean Assessment & Reporting of Tsunamis) –TAO (Tropical Atmosphere/Ocean) –NWLON (National Water Level Observing Network) –PORTS (Physical Oceanographic Real-Time System) –MODIS ocean color –HFR surface currents Observing Systems

9. IOOS Core Variables 9 Temperature Salinity Water level Currents Waves Surface Winds Ocean color Dissolved oxygen pH pCO2 Heat flux Bottom character Pathogens Bathymetry Ice distribution Contaminants Stream flow Dissolved nutrients Optical properties Total suspended matter Colored dissolved organic matter Fish species Fish abundance Zooplankton species Phytoplankton species Zooplankton abundance List could be expanded based on identified needs... Observing Systems

10. IOOS DACs at NOAA Satellite Ocean Color (Aqua MODIS) National Environmental Satellite, Data, and Information Service (NESDIS) CoastWatch National Water Level Observation Network (NWLON) Physical Oceanographic Real- Time System (PORTS) National Ocean Service (NOS) Center for Operational Oceanographic Products and Services (CO-OPS) NWS Met/Oc Buoys IOOS Regional stations Tropical Atmosphere Ocean (TAO) Buoys Deep-Ocean Assessment and Reporting of Tsunamis (DART) Surface Currents from High- Frequency Radar (HFR) National Weather Service (NWS) National Data Buoy Center (NDBC) 228 172 5547 10 Data Assembly Centers

11. IOOS Regional DACs also coming on line NDBCCO-OPS CoastWatch NANOOSNERACOOSPacIOOS CeNCOOS SECOORA AOOSGCOOS SCCOOS IOOS Regional Associations - observations and model outputs NOAA Data Providers 11

12. Data Access Services 12 In-situ features (buoys, piers, floats, ships,...) Regular Grids (radar, satellite, model outputs) OGC Sensor Observation Service (SOS) OpenDAP and/or OGC Web Coverage Service (WCS) XML based on OGC Observations and Measurements (O&M) NetCDF using Climate and Forecast (CF) conventions Images of data (all types) OGC Web Map Service (WMS) GeoTIFF, PNG etc. -possibly with standardized styles [*OGC = Open Geospatial Consortium] Data TypeWeb ServiceEncoding Data Access Services

13. Sampling feature = discrete location(s) of measurements –Point, Vertical or Horizontal Profile, Trajectory (e.g., ship track) –…and Time Series or Collections thereof GetCapabilities operation: “table of contents” GetObservation operation: XML data file containing observation values for desired: –Variable(s) of interest –Bounding box Or perhaps named geographic feature of interest Or perhaps a single sensor –Time DescribeSensor operation: SensorML providing detailed information about a specific sensor (or platform or group of sensors) SOS for In-Situ Data OGC Sensor Observation Service v1.0 13 Data Access Services

14. SOS GetObservation Response XML Encoding of In-Situ Data 14 XML Extensible Markup Language Generic method for structuring text data OGC GML Geography Markup Language XML that can represent any geospatial feature OGC O&M Observations and Measurements Model GML that describes the act of measuring real-world phenomena and the result of the measurement specialized by IOOS v0.6.1 schema Specific encoding used by IOOS SOS servers XSD, Examples, XSLT @ http://ioos.gov/dif/ resulting in Data Access Services

15. SOS and O&M specs are fairly general –Need community specialization/restriction IOOS adopting, defining or researching practices: –URIs for sensors, stations, networks, CRS, phenomenon names –HTTP GET request encoding –SensorML metadata –Observation Offerings –Other formats for SOS NetCDF/CF ASCII CSV KML+JSON (Javascript Object Notation) –IOOS GML schema evaluation pending SOS Profile/Best Practices 15 Data Access Services

16. Services requested from an OPeNDAP server are specified in a suffix appended to the URL. Depending on the suffix supplied, the server will return one of these response types: Data Attribute (.das suffix) –Text file describing the attributes of data quantities in dataset. Data Descriptor (.dds) –Text file describing the structure of the variables in the dataset. OPeNDAP Data (.dods) –Actual data as binary MIME-typed file. –Constraints can be appended to select a subset of the data. ASCII Data (.asc,.ascii) –ASCII representation of the requested data. WWW Interface (.html) –HTML form that can be used to construct a data URL. Information (.info) –HTML information about the server and dataset. OPeNDAP for Gridded Data Open-source Project for a Network Data Access Protocol 16 Source: OpenDAP User Guide 1.14 Data Access Services

17. 271828 4590452353602874713526624977 9676277240766303535475945713821785251664 921817413596629043572900334295265956307 233829887531952510190115738341879307021 2447614666882264801684774118537423454 695517027618386626133138458300752449 200793287091274437470472306969772093101 657463772111252389784425569536967707854 9879316368892300987931277361782154249992 19366803318252886939849646515829392398 117312381976841614397198376793206832 3287825098194558153017567173613320698112 351598888519345872738667385894228792284 6104841984443634632449684875602336248270 235343699418491463140934317381436405462 167683964243781405927145635490613031072 704171898610687396965521267154688957350 32106817121562788235193033224745158 5036604169973297250886876966403555707162 78713419512466521035921236677194325278 WCS for Gridded Data OGC Web Coverage Service v1.1 Coverage ~ array of gridded data values –(simplified viewpoint for this discussion – coverage can be more complex) GetCapabilities operation: “table of contents” GetCoverage operation: data file containing header and array(s) of numbers customized for: –Variable of interest –User-specified bounding box –User-specified time –File format (e.g, NetCDF, HDF, floating-point TIFF) DescribeCoverage operation: metadata about a specific dataset (x1,y1) (x2,y2) 17 Data Access Services

18. “Map” = georeferenced picture of data GetCapabilities operation: “table of contents” in standardized format GetMap operation: image of data customized according to: –Variable(s) of interest –User-specified bounding box –User-specified time –Image size –File format (e.g., PNG, GetTIFF, JPEG, GIF) WMS for Images of Data OGC Web Map Service v1.3 18 ← width → ← height → (x1,y1) (x2,y2) boundaries water bodies topography Layers = Data Access Services

19. Data Customers and Sources CO-OPS SOS CoastWatch DAP CeNCOOS SOS SECOORA SOSDAPWMS AOOS SOSDAPWMS NANOOS DAPWMS NERACOOS DAPWMS PacIOOS DAPWMS SCCOOS SOSDAPWMS GCOOS SOSDAPWMS NDBC SOSDAPWMS Public IP network s Coastal Inundation Harmful Algal Blooms Hurricane Intensity Integrated Ecosystem Assessments Google Oceans Tsunami Event DB other customers t.b.d... Public Internet other providers t.b.d... SOS DAP SOS 19 Modeling & Analysis

20. Additional Services SOSDAPWMS SOSDAPWMS SOSDAPWMS Public Internet 20 IOOS Portal Catalog Registry Web Interface SOSDAPWMS Service Gateway SOSDAPWMS Visualization Format Conversion Utility Services

21. Scalable translation/visualization service in the cloud (Amazon EC2) NSF OOI/CI Collaboration 21 SOS DAP etc ERDDAP CSV HTML KML NetCDF Figure from M. Arrott et al., Proc. MTS/IEEE Oceans 2009

22. IOOS – NextGen WIDB Linkages Does IOOS have data of interest to NextGen/FAA/WIDB Consumers? –IOOS-supported data was instrumental to the safe rescue of passengers and crew on US Air Flight 1549, which crashed into the Hudson River in January, 2009 –Stevens Institute of Technology’s NYHOPS - New York Harbor Observing and Prediction System (www.stevens.edu/maritimeforecast/) – was used to prepare detailed summary of present water conditions surrounding the crash site and to forecast conditions for the next 48 hourswww.stevens.edu/maritimeforecast/ –Data about swift river currents informed decisions to deploy rescue assets downstream, not upstream and to guide the plane eastward to the Battery area for salvage operations “Present In the Moment” - Stevens Efforts Regarding the Crash of US Airways Flight 1549. Alan F. Blumberg, Center for Maritime Systems, Stevens Institute of Technology, Castle Point on Hudson. January 19, 2009

23. Most likely scenario for IOOS sources IOOS – NextGen WIDB Linkages How does IOOS IT Infrastructure integrate with WIDB? –Overall architecture/infrastructure is compatible –IOOS systems would appear as SOA WX Cube sources Are supported standards and formats compatible? –Both have basis in OGC standards –Devil will be in the details, but translators or converters can be employed to bridge the gaps

24. Schedule and Milestones Major Capabilities - “Running Stuff”Status Initial set of standards adopted, encodings and content standards adapted/customized Standardized data access services implemented at operational data providers (NDBC, CO-OPS, CoastWatch, etc) SOS: Point, Profile, Time Series, Collections OpenDAP/WCS: Regular Grids Four active customer projects; NWS customer using IOOS data in operational scenarios Work In ProgressCompletion SOS, WMS, WCS submitted as IOOS standards Need to document SOS Profile for ocean observations Early FY10 Implementing detailed metadata for sensors & platformsEarly FY10 Event-specific “features of interest"Early FY10 Expansion towards IOOS/National DMAC Service types (Registry, Catalog, …) Data types (trajectory, unstructured grid, imagery) Data providers (biological, etc), data customers (climate…) End FY10 See http://ioos.gov/dif/

25. Contacts: Jeff.deLaBeaujardiere@noaa.gov Carmel.Ortiz@noaa.gov Thank You! 25

26. Backup Slides

27. Adopt open standards & practices Federated, service-oriented architecture –Data made accessible via OGC or DAP services Not SOAP/WSDL services –Data stays with data providers –Service adapters for existing systems Core Principles 27

28. IOOS DMAC Cross-cutting Considerations Observing Systems Data Assembly Ctrs Data Access Services Utility Services Modeling & Analysis Cross-cutting Considerations Governance/Policies IT Security/Info Assurance Configuration Management Metadata Input & Access Data Quality Service-Level Agreements Capability Maturity Levels

29. 29 Federated, Service-Oriented Architecture IOOS Portal Catalog Registry Web Interface Utility Services Thematic Portal Registry Catalog Obs Syst. or Model data provider Data Center data access service Obs Syst. or Model Data Center data access service Regional Portal data access service Regional Obs Syst. or Model RegistryCatalog Data Center data access service Data Center data access service 29

30. IOOS Data and Metadata Types 30 Ocean Properties (Physical, biological, chemical) Sampling Feature Types (Point, Profile, Trajectory, Reg Grid, Unstructured Grid) Data Encoding Conventions (GML, KML, O&M, SWEC, CSML, NetCDF/CF) Collection Types (Time Series, Multi-Station Obs) Information Viewpoint from Reference Model for Open Distributed Processing (RM-ODP) Sensor/Platform Metadata (SensorML) QA/QC Metadata (QARTODS/Q20) Discovery Metadata (FGDC, ISO 19115/19139) Service Metadata (OWS Capabilities XML, ISO 19119) Controlled Vocabularies (CF, MMI, OGC, GCMD, URNs)

31. THREDDS IOOS Data and Metadata 31 Properties Datasets Information Viewpoint from Reference Model for Open Distributed Processing (RM-ODP) Registries QA/QC Metadata Discovery Metadata Services Controlled Vocabularies Water Procedures SensorML Measurements Catalogs physical chemical biological Procedure Metadata Service Metadata Data Formats EPSG MMI GCMD CF GTS DAP SOS ISO 19119 Cap.XML FGDC ISO 19115 has that are observed by that make grouped in accessed through documented with ISO 19115 such as described by that include harvested by published in described by that use GML/O&M BUFR CS/W Sensors Lab analysis Surveys KML NetCDF/CF and

32. Each station (buoy, fixed sensor package) is a separate Offering from the SOS –Allows requests for data from 1 station at a time Multi-station Offerings: –“All stations” Offering User specifies bounding box instead of station ID –Soon: program-specific or event-specific Offerings E.g., “all Hurricane Katrina data” –Maybe: phenomenon-specific Offerings E.g., “all temperature data” Offering includes ID and English name –gml:name = ID –gml:description = name May replace multiple sensor IDs per offering with single station ID IOOS Practice: Observation Offerings 32

33. Using URNs for IDs of sensors, stations, networks (URN = Uniform Resource Name) Following “OGC Definition URN” practice –urn:namespace:def:objectType:authority:[version]:code[:otherParams] Examples: –urn:x-noaa:def:network:noaa.nws.ndbc::all –urn:x-noaa:def:station:noaa.nws.ndbc::21418 –urn:x-noaa:def:sensor:noaa.nws.ndbc::21418:tsunameter0 Also using URNs for EPGS CRS identifiers Using URLs for phenomenon names –Adopting MMI/CF URLs: http://mmisw.org/ont/cf/parameter/sea_water_temperature –Allow trailing component as abbreviation (sea_water_temperature) IOOS Practice: Identifiers 33

34. Supporting both HTTP POST requests and HTTP GET –HTTP POST defined in spec, GET left out –Mostly following Oceans IE Best Practice for GET For Bounding Box, using FOI that could be a BBOX or (in future) a named FOI: featureofinterest=BBOX:minlon,minlat,maxlon,maxlat IOOS Practice: GetObservation Request 34

35. IOOS Metadata Linkage Model (Sensors, Stations, Networks, Datasets and Services) 35 Sensor Sensor Type instances Network type station QC procedures Procedure description Station StationType instances type group sensors members phenomenon Dataset applicable to Obs system ISO 19115 SensorML Service network OGC CapXML Online resource WSDL ISO 19119 station sensor THREDDS (make/ model)

36. IOOS Data Model for Time Series at a Collection of Points Collection –Station 1 Time 1 –quantity 1 –quantity 2 Time 2 –quantity 1 –quantity 2 –Station 2 Time 1 –quantity 1 –quantity 2 Time 2 –quantity 1 –quantity 2 36 Collection Bounding box Time range # of stations Station # of times Date/Time Time-dependent metadata # of quantities Quantity Name Units Value 1..* Station Metadata ID (URN) Name Location Procedure IDs Static metadata 1

37. Scalable translation service (NSF OOI/CI) XSLT templates Format Conversion Tools 37 Sensor Observation Service CSV XSLT HTML Table of Contents Data Values XSLT KML SOS DAP etc ERDDAP CSV HTML KML Spreadsheet Virtual Globe Science App Browser NetCDF KML