1 / 37

Integrated Ocean Observing System (IOOS)

Integrated Ocean Observing System (IOOS). Jeff de La Beaujardière, PhD Carmel Ortiz NOAA IOOS Program Office. Outline. IOOS program overview IOOS high-level architecture Observing Systems Data Assembly Centers Data Access Services Supported Standards & Formats Utility Services

dooley
Download Presentation

Integrated Ocean Observing System (IOOS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. IOOS is not building a new system • 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?

  4. 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 • 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 1 7 5 3 8 12 6 9 10 11 4 2 Alaska Ocean Observing Systems (AOOS) Caribbean Regional Association (CaRA) Central and Northern California Coastal Ocean Observing System (CeNCOOS) Gulf Coastal Ocean Observing System (GCOOS) Great Lakes Observing System (GLOS) Mid-Atlantic Coastal Ocean Observing System Regional Association (MACOORA) • Northwest Association of Networked Ocean Observing Systems (NANOOS) • Northeast Regional Association of Coastal Ocean Observing Systems (NERACOOS) • Pacific Islands Ocean Observing System (PacIOOS) • Southern California Coastal Ocean Observing System (SCCOOS) • Southeast Coastal Ocean Observing System Regional Association (SECOORA) • Alliance for Coastal Technologies (ACT) {Sensor V & V}

  5. IOOS Partners: Federal Agencies • 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 Partners: International • 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) Global Ocean Observing System IOOS GOOS GEOSS

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

  8. Observing Systems Observing Systems • 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

  9. Observing Systems IOOS Core Variables 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...

  10. IOOS DACs at NOAA Data Assembly Centers National Weather Service (NWS) National Data Buoy Center (NDBC) 172 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) 228 55 47 National Ocean Service (NOS) Center for Operational Oceanographic Products and Services (CO-OPS) National Water Level Observation Network (NWLON) Physical Oceanographic Real-Time System (PORTS) National Environmental Satellite, Data, and Information Service (NESDIS) CoastWatch Satellite Ocean Color (Aqua MODIS)

  11. IOOS Regional DACs also coming on line Data Assembly Centers NOAA Data Providers NDBC CO-OPS CoastWatch IOOS Regional Associations - observations and model outputs CeNCOOS AOOS GCOOS SECOORA NANOOS NERACOOS PacIOOS SCCOOS

  12. Data Access Services Data Access Services Data Type Web Service Encoding In-situ features (buoys, piers, floats, ships, ...) OGC Sensor Observation Service (SOS) XML based on OGC Observations and Measurements (O&M) Regular Grids (radar, satellite, model outputs) OpenDAP and/or OGC Web Coverage Service (WCS) 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]

  13. Data Access Services SOS for In-Situ DataOGC Sensor Observation Service v1.0 • 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 filecontaining 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)

  14. Data Access Services SOS GetObservation ResponseXML Encoding of In-Situ Data XML Extensible Markup LanguageGeneric method for structuring text data OGC GMLGeography Markup LanguageXML that can represent any geospatial feature specializedby OGC O&MObservations and Measurements ModelGML that describes the act of measuring real-world phenomena and the result of the measurement specializedby IOOS v0.6.1 schemaSpecific encoding used by IOOS SOS servers XSD, Examples, XSLT @ http://ioos.gov/dif/ resulting in

  15. Data Access Services SOS Profile/Best Practices • 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

  16. Data Access Services OPeNDAP for Gridded DataOpen-source Project for a Network Data Access Protocol • 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. Source: OpenDAP User Guide 1.14

  17. WCS for Gridded DataOGC Web Coverage Service v1.1 (x2,y2) (x1,y1) Data Access Services • Coverage ~ array of gridded data values • (simplified viewpoint for this discussion – coverage can be more complex) • GetCapabilities operation: “table of contents” • GetCoverage operation: data filecontaining header and array(s) ofnumbers 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

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

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

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

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

  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 hours • 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. 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 Most likely scenario for IOOS 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 See http://ioos.gov/dif/

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

  26. Backup Slides

  27. Core Principles • 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

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

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

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

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

  32. IOOS Practice: Observation Offerings • 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

  33. IOOS Practice: Identifiers • 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)

  34. IOOS Practice: GetObservation Request • 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

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

  36. IOOS Data Model for Time Series at a Collection of Points Collection Bounding box Time range # of stations • 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 1..* Station Metadata ID (URN) Name Location Procedure IDs Static metadata Station # of times 1 1..* Date/Time Time-dependent metadata # of quantities 1..* Quantity Name Units Value

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

More Related