Interoperability Workshop in Portland Maine, as a representative of IGWADTS and NASA Dryden. John Wilson is an engineer at Creare Inc., a small R&D firm located in Hanover, NH. At Creare, John has been involved in a range of software and hardware development projects, including graphical user interfaces, control code, and device driver software in Java, C+ +, MATLAB, assembler, and CLIPS. He is Project Engineer on several DoD/NASA projects which utilize Creare’s Ring Buffered Network Bus technology to advance the integration and interoperability of diverse systems. The RBNB-based Intelligent Network Data Server (INDS) system used at NASA Dryden has recently supported several NASA/NOAA suborbital airborne science
23
Embed
John Wilson attended John Graybeal’s Sensor Interoperability Workshop in Portland Maine, as a representative of IGWADTS and NASA Dryden. John Wilson is.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
John Wilson attended John Graybeal’s Sensor Interoperability Workshop in Portland Maine, as a representative of IGWADTS and NASA Dryden.
John Wilson is an engineer at Creare Inc., a small R&D firm located in Hanover, NH. At Creare, John has been involved in a range of software and hardware development projects, including graphical user interfaces, control code, and device driver software in Java, C++, MATLAB, assembler, and CLIPS. He is Project Engineer on several DoD/NASA projects which utilize Creare’s Ring Buffered Network Bus technology to advance the integration and interoperability of diverse systems. The RBNB-based Intelligent Network Data Server (INDS) system used at NASA Dryden has recently supported several NASA/NOAA suborbital airborne science activities.
– Track 1: Teams assigned a standard; they come up with an instance for a particular instrument (i.e., CTD (Conductivity, Temperature, Depth) instrument).
– Track 2: Exposure/introduction to standards (primarily SensorML and TML), XML and XSLT.
• “Content descriptive”– Standards: DIF, ISO 19115, FGDC
– Primarily used for discovery/searching, for example:• Does the desired data exist?• If data exists, metadata can instruct where to get it (Web link or
• Describes geographic information and services.• From MMI Web site: “It provides information about the
identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data.”
• Primarily a “content descriptive” standard.• Has the benefit of being an international standard.• Implementation schema: ISO 19139.• Can be extended by embedding an instance of or reference
• FGDC CSDGM: Federal Geographic Data Committee Content Standard for Digital Geospatial Metadata.
• From MMI Web site: “Purpose of the standard: define the information required by a prospective user to determine the availability of a set of geospatial data, the fitness the set of geospatial data for an intended use, the means of accessing the set of geospatial data, and to enable successful transfer.”
• Primarily a “content descriptive” standard.• As a federal standard, adherence is required by federal agencies
and funded programs.• Will be compliant with ISO 19115.• Remote Sensing Extension adds elements which describe the
• Presentation by Steve Havens, Argon ST (the developers of TML standard)• <http://www.transducerml.org>• A data-centric, “processable” standard―very close to the sensor
– Doesn’t include search keywords, contact info, historical data, etc– Doesn’t deal with system-of-systems or data products (that is, any client-side
visualization or other application)
• Two parts– Static system descriptor: tells the receiver how to interpret the data– Dynamic data stream, including time tag and system descriptor ID tag
• Can be used to describe any sensor―“sensor agnostic”• Can be used in any domain (NASA, FBI, etc.) ―“domain agnostic”―helps
facilitate data sharing between domains• Developed to help the military perform battlefield data fusion• IWG or REVEAL UDP formats could use TML?• TML is an OGC standard
• Metadata standards– Sensor Model Language (SensorML)– Transducer Model Language (TransducerML or TML)– Base standard: OGC Geography Markup Language (GML)
• Sensor Observations Service (SOS): Web service interface for requesting data from a data repository.
– Wrap RBNB as SOS service for data sink request?
• Sensor Alert Service (SAS): Web service interface for subscribing to streaming data or alerts.
– Wrap RBNB as SAS service for data sink streaming?
• 52North has produced an open source Java SWE implementation <http://52north.org>
• Ocean Research Interactive Observatory Network • <http://www.orionprogram.org>• NSF’s Ocean Sciences Division has developed the Ocean Observatories Initiative
(OOI), which is an integral part of ORION.• Similar to LEAD and NEON• Goal: “Provide the U.S. ocean sciences research community with access to the
basic infrastructure required to make sustained, long-term and adaptive measurements in the oceans.”
– Investigate phenomenon which fluctuate over long periods of time (decades or longer) or are episodic (i.e., underwater volcanic eruptions).
– Enable users to interact with sensors to adjust measurements.
• OOI-enabled observatories to be networked and become an “integral part” of IOOS• Cyberinfrastructure (CI) component provides the common infrastructure to connect
and coordinate the observatories– MMI ORION presentation by Alan Chave, Senior Scientist at Woods Hole Oceanographic
Institution, is on the CI team.– Based on DoDAF (DoD Architectural Framework)– Addresses “observatory resource management, mission command and control, data
management and distribution and the meaningful collaboration across a wide range of disciplines.”
• North-East Pacific Time-Series Undersea Networked Experiments • <http://www.neptunecanada.ca>• Planned to be the largest cable-linked seafloor observatory• Begin operation in 2007; two test networks deployed in 2007–2008
– VENUS (Victoria Experimental Network Under the Sea) project off the southern British Columbia coast <http://www.venus.uvic.ca>
– MARS (Monterey Accelerated Research System) project off Monterey, California <http://www.mbari.org/mars>
• Benoit Pirenne (NEPTUNE/VENUS) presented their metadata “topology”– Motivation: Twenty years from now, be able to query for instrument data and metadata– “Topology” is the metadata document which describes each instrument’s historical record
When was the sensor deployed Historical record of calibrations and maintenance When was it taken out of the water
– Topology hierarchy Region Location Sites Platform Instrument Sensor
– There are many Sensors on an Instrument; many Instruments on a Platform, etc.
• Web form/GUI tools for creating XML instances which adhere to a standard schema (SensorML, TML, etc.) are needed
• The definition of common controlled vocabularies is needed; MMI VINE (Vocabulary Integration Environment) is a step in this direction
• Beginner’s resources are needed– Documentation, tutorials– E-mail/phone “helpdesk” to ask experts
• Need a better understanding of the differences between SensorML and TML• Different standards play different roles (“content descriptive” vs. “processable”)
– “Content descriptive” standards (i.e., ISO 19115) could include links to or embed instances of a “processable” objects (i.e., SensorML)
– The Workshop ISO Track 1 team used this technique in the XML instance they created