OGC’s Sensor Web Enablement

1. OGC’s Sensor Web Enablement Lúbia Vinhas Image Processing Division National Institure for Space Research Brazil Bilateral Research Workshop iFGi – INPE, March 11, 2009

2. Introduction • I have a background in Computer Science. • I am a researcher at the DPI since 1998. • I have a background in Computer Science. • I am one of the leaders for the TerraLib project. • Currently I co-supervise 2 Master students and 1 PhD student. • My insterests are: FOSS4GIS, spatial databases, image databases, GIS development.

3. SpaceandSociety Earth Observation Monitoring Amazonia R & D at INPE/OBT/DPI

4. TerraLib A library to develop geographical applications Open Source Policy – LGPL Open Protocols Extensive use DBMS C++ language Allows users to customize a solution Desktop, Distribute, Web

5. TerraLib applications and uses

6. TerraLib applications and uses

7. TerraLib applications and uses Slide by Tiago Carneiro

8. TerraLib applications and uses

9. TerraLib Web Services • A group of graduate students and TerraLib partners outside INPE to explore OGC standards related to Web Services (WMS, WFS, WCS, WPS,GML, Filter Encoding, SLD, ...) • Main goal: capacity building in implementing OGC Web Services Client and Server side

10. Observatorium Slide by Emerson Xavier Mediator Integration Execution Optimization Participation

11. TerraLib 5 • Plataform that will be: • more interoperable, • manage better all kinds of data sources, • more flexible • more extensible

12. TerraLib 5

13. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs) . Sensor Web Concept Botts et al., 2008

14. Sensor Web Enablement

15. Observations & Measurements (O&M) • The general models and XML encodings for sensor observations and measurements. • An observationis an event with a result that has a value describing a phenomenon; • Uses a procedure to determine the value, which may involve a sensor, observer, analytical procedure, simulation or other numerical process • Is modeled as a OGC feature. • An observation feature binds the result to the a feature-of-interest, upon which it was made.

16. Sensor Model Language (SensorML) • The general models and XML schema for describing sensors and processes associated with measurement. Everything is modeled as Process: • Non-physical (“pure”) processes • ProcessModel (atomic) • Examples: sensor model, FFT, Look-Up-Table • ProcessChain (composite) • Examples: geolocation chain, product algorithm • Physical processes • Component (atomic) • Examples: detector, actuator, sampler • System (composite) • Examples: sensor system, weather station, UAV • All SensorML processes have Inputs, outputs, parameters (defined using SWE Common data) and metadata.

17. Transducer Markup Language (TML) • General characterizations of transducers (both receivers and transmitters), their data, how that data is generated, the phenomenon being measured by or produced by transducers, transporting the data, and any and all support data (metadata) necessary for later processing and understanding of the transducer data. • Many of today’s sensor systems are comprised of several sensors which work in unison. It is necessary to capture and exchange instantaneous system state for all sensors at any time during operation. • No single data format exists to handle all sensors. TML provides a standard data format for sensors so that data exchange between different types of sensors is possible.

18. Sensor Observations Service (SOS) • A service interface for requisting, filtering and retrieving observations and sensor system information.

19. Sensor Planning Service (SPS) • A service by which a client can determine collection feasibility for a desired set of collection requests for one or more sensors/platforms, or a client may submit collection requests directly to these sensors/platforms.

20. Sensor Alert Service (SAS) • A service by which a client can register for and receive sensor alert messages. The service supports both pre-defined and custom alerts and covers the process of alert publication, subscription, and notification. • Capabilites determine the nature of the offered alerts, the protocols uses and the options to subscribe to specific alert types. • An alert is na special kind of notification indicating that a na event has occurred at na object of interest, which results in condition of heightened watchfulness or preparation for action.

21. Web Notification Service (WNS) • A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. • The WNS is a general purpose messaging service. It is an asynchronous and statefull service. It is a service that sends notifications consisting of well-structured content to a client. To enable any kind of dialogue between the user and an invoking service, functionality has to be provided that enables the user to asynchronously answer with any kind of structured content.

22. Status Current specs are in various stages SensorML/SWE Common – Version 1.0.1 TransducerML – Version 1.0 Observations & Measurement – Version 1.0 WNS – Request for Comments SOS – Version 1.0 SPS – Version 1.0 SAS – Ready for final vote Approved SWE standards can be downloaded: Specification Documents: http://www.opengeospatial.org/standards Specification Schema: http://schemas.opengis.net/

23. Current SWE implementation efforts • Oak Ridge National Laboratory’s (ORNL) SensorNet program at Fort Bragg, North Carolina, developing a collection of systems for the detection, identification and assessment of chemical, biological, radiological and nuclear threats. • SensorWeb, being developed by SAIC for the Defense Intelligence Agency (DIA). • SANY (Sensors Anywhere), co-funded by the Information Society and Media Directorate General of the European Commission, contributing to the Global Monitoring for Environment and Security (GMES) program.

24. Current SWE implementation efforts • The Consortium of Universities for the Advancement of Hydrologic Science Inc. (CUAHSI) representing more than 100 U.S. universities, uses SWE standards in its Hydrologic Information System (HIS). • Persistent Universal Layered Sensor Exploitation Network (PULSENet), a Northrop Grumman Corporation internal research and development project

25. Current SWE implementation efforts • The German organization 52North provides a complete set of SWE services under GPL license. One project using 52North’s software is the German Indonesian Tsunami Early Warning System (GITEWS), a 35-million euro project of the German aerospace agency, DLR, and the GeoForschungsZentrum Potsdam (GFZ), Germany's National Research Centre for Geosciences.

27. My concerns for this joint research agenda... • How can we critically evaluate this framework? • How can we contribute to this framework? • How can we use this framework in applications such as Amazonian Land Use and Cover Change and Global Climatic and Environmental Changes Studies? • How can we transform technology in academic results?

28. Thank you! lubia@dpi.inpe.br www.dpi.inpe.br/~lubia