Sensors, SWE and European spatial data initiatives – INSPIRE and GMES Adobe Systems Brno, 17. 4. 2012 Radim Štampach, Ph.D. Good morning, Ladies and Gentlemen. My name is Radim Štampach. I am from the same institution and I am working on the same project as my colleague Petr Duda. He presented you some basic information about sensors and SWE. I would like to speak about relationship between sensors, SWE and European spatial data initiatives – INSPIRE and GMES. Their development is very actual topic now and they are highly connected also to sensors. Sensor Web Enablement and its future development Sensor network – different producers, different protocols… SWE: • initiative of the Open Geospatial Consortium (OGC) • standardizes web service interfaces • hides the different hardware and communication protocols SWE framework: • SOS – obtain observations from sensors • SPS – control the sensor (e.g. make image at this time) • SAS – receive sensor alert messages (e.g. low battery) • WNS – SAS alerts can be delivered by e-mail, SMS… • SensorML, TransducerML – model and XML schema for describing sensors • Observation/Measurement – model and XML encoding of observations Working with sensor data is connected with problem of interoperability. Different sensors producers use different protocols and different ways to get the data. The Sensor Web Enablement (SWE) initiative of the Open Geospatial Consortium (OGC) standardizes web service interfaces and data encodings which can be used for sensor data. It hides the different hardware and communication protocols from the applications built on top of it. Sensor Observation Service (SOS) is a service by which a client can obtain observations from one or more sensors/platforms (can be of mixed sensor/platform types). Clients can also obtain information that describes the associated sensors and processes (OGC SML 2007, 13). Sensor Planning Service (SPS) allows client to 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 (OGC SPS 2007, 9). SPS can be used to control the sensor - e.g. select instrument, acquire image at this time, etc. Sensor Alert Service (SAS) is a service by which a client can register for and receive sensor alert messages (OGC SOS 2007, 12). Web Notification Services (WNS) is a service interface for asynchronous delivery of messages or alerts from SAS and SPS web services (OGC SWE WG 2011). Alerts can be delivered by e-mail, SMS etc. Sensor Markup Language (SensorML) specifies the general models and XML schema for describing sensors and processes associated with measurement (OGC SOS 2007, 12). Transducer Markup Language (TransducerML) specifies the conceptual model and XML Schema for describing transducers and supporting real-time streaming of data to and from sensor systems (OGC SWE WG 2011). Observation/Measurement (O&M) specifies the general models and XML encodings for sensor observations and measurements (OGC SOS 2007, 12). SOS – Sensor Observation Service The basic and most developed service in SWE 1.0 framework is SOS. Initial draft of SOS was produced in 2005 and current specification was developed in 2007 (OGC SOS 2007). SOS has three mandatory “core” operations: GetCapabilities, DescribeSensor, and GetObservation. The GetCapabilities operation provides consumer with the possibilities to access SOS service metadata. The consumer gets the capabilities (described in XML document), which allow him to inspect available sensor observations. The consumer then invokes the DescribeSensor operation to find detailed information about sensor and processes generating those measurements. This information is returned to consumer in SensorML or TransducerML format. Finally, the consumer calls the GetObservation operation to get the required observations from sensor. Transferred data are encoded with using Observation/Measurement specification (Kozel et al. 2011).SOSconsumerGetCapabilitiesCapabilities response (XML document)DescribeSensorSensorML or TransducerMLGetObservationdata (Observations & Measurement) SOS can be used not only by data consumers. This specification also defines operations for sensor data providers. They can insert new sensors and sensor observations into an SOS where consumer can find them. The RegisterSensor operation allows the provider to register a new sensor system with the SOS. The InsertObservation operation allows inserting of new observations for a sensor system that was registered by RegisterSensor operation. O&M – Observation and Measurement WHAT? temperature OF WHAT? air HOW? Sensor TQS3M RESULT 23°C OBSERVATION WHEN? 10th May 2011, 13:30 WHERE? Brno The basic and most developed service in SWE 1.0 framework is SOS. Initial draft of SOS was produced in 2005 and current specification was developed in 2007 (OGC SOS 2007). SOS has three mandatory “core” operations: GetCapabilities, DescribeSensor, and GetObservation. The GetCapabilities operation provides consumer with the possibilities to access SOS service metadata. The consumer gets the capabilities (described in XML document), which allow him to inspect available sensor observations. The consumer then invokes the DescribeSensor operation to find detailed information about sensor and processes generating those measurements. This information is returned to consumer in SensorML or TransducerML format. Finally, the consumer calls the GetObservation operation to get the required observations from sensor. Transferred data are encoded with using Observation/Measurement specification (Kozel et al. 2011).SOSconsumerGetCapabilitiesCapabilities response (XML document)DescribeSensorSensorML or TransducerMLGetObservationdata (Observations & Measurement) SOS can be used not only by data consumers. This specification also defines operations for sensor data providers. They can insert new sensors and sensor observations into an SOS where consumer can find them. The RegisterSensor operation allows the provider to register a new sensor system with the SOS. The InsertObservation operation allows inserting of new observations for a sensor system that was registered by RegisterSensor operation. Visit in Ispra and its topic Joint Research Centre Institute of Environment and Sustainability Spatial Data Infrastructures Unit Ispra, Italy Searching connections between sensors, SWE and important European initiatives – Inspire and GMES. March 2011 In name of Geotým project I was sent to Joint Research Centre in Ispra, Italy. It is place where important European legislation about spatial data is prepared, including Inspire directive and GMES initiative. My topic was studying connections between sensors and both initiatives – Inspire and GMES. • lays down general rules to establish an infrastructure for spatial information in Europe. • for the purposes of Community environmental policies and policies or activities which may have an impact on the environment. • entried into force 15 May 2007 Inspire Network Services: • Discovery Services • View Services • Download Services • Transformation Services INSPIRE Directive I am sure that it is useless to explain here what „INSPIRE“ is, because all we are from geoinformatics community. So only shortly. Inspire Directive lays down general rules to establish an infrastructure for spatial information in Europe. Inspire is prepared for the purposes of Community environmental policies and policies or activities which may have an impact on the environment. Directive entried into force 15 May 2007. Important part of Inspire are Network Services. Geodata across Europe should be findable through Discovery Services, viewable with View Service they should be able to be downloaded by Download Service and transformed with Transformation Service - e.g. to different coordination system. 43 themes – 3 annexes, one theme – one Data Specification Annex I – Data Specifications completed Annex II-III – Data Specifications testing – April-October 2011 Annex III – many typical “sensor data” INSPIRE Directive Inspire divides data into three groups – „annexes“ – and 21 themes. Data Specifications for Annex I are prepared. Data Specifications of themes from Annex II and III are in phase of commenting from wider community. You can see that in Annex III there are some themes that are typical cases of data measured by sensors – meteorological, atmospheric conditions etc. SWE and INSPIRE INSPIRE Cross Thematic Working Group on Observations & Measurements solves using of Sensor Web Enablement-related standards in INSPIRE data specification. The rest of presentation is about my questions to JRC SDI Unit team and answers I was given by them in Ispra. Data specifications for Annex II and III are in testing. Part of these annexes is connected to sensor data. Will be SWE and sensors mentioned or recommended in Data Specifications of Annex II and III? Data specifications for Annex II and III are in testing and commenting by wider community now. Testing will be finished in October. INSPIRE Cross Thematic Working Group on Observations & Measurements solves using of Sensor Web Enablement-related standards in INSPIRE data specification. Observation & Measurement •Some Annex themes include measured, modelled or simulated data. •The ISO 19156 (Observation & Measurement 2.0) standard was designed for this explicit purpose, and thus shall be used in INSPIRE to cover these requirements. •The following INSPIRE themes use O&M in data specifications: •Geology •Oceanographic geographical features •Atmospheric conditions and Meteorological geographical features •Environmental monitoring facilities •Soil SWE and INSPIRE Specification Observation & Measurement is mentioned many times in Data Specifications. New version of this specification is standardised as ISO 19156. Some Annex themes include measured, modelled or simulated data and this standard was designed for this explicit purpose, so it should be used in INSPIRE to cover these requirements. The following INSPIRE themes using O&M in their data specifications: Geology Oceanographic geographical features Atmospheric conditions and Meteorological geographical features Environmental monitoring facilities Soil SWE and INSPIRE INSPIRE Cross Thematic Working Group on Observations & Measurements nominated also two other SWE specifications as useful for INSPIRE: SOS – proposed to be used as Download Service SensorML – description of data survey process Not used in current version of Data Specification, only recommended for implementation into next version. INSPIRE Cross Thematic Working Group on Observations & Measurements nominated also two others SWE specifications as useful for INSPIRE: SOS – proposed to be used as Download Service SensorML – description of data survey process GMES GMES (Global Monitoring for Environment and Security) is the European Programme for the establishment of a European capacity for Earth observation. • Six thematic areas: marine, land, atmosphere, emergency, security, climate change. • Space division: Earth observation satellites • In-situ division: ground stations, planes, balloons, sea-borne sensors… Not only Inspire is geospatial initiative connected to sensor data. Sensors are probably the most important part of GMES initiative. Global Monitoring for Environment and Security is the European Programme for the establishment of a European capacity for Earth Observation. Services should cover six thematic areas: marine, land, atmosphere, emergency, security, climate change. System should consist both from earth observation satellites and in situ sensors that includes ground stations, but also planes, balloons or sea-borne sensors. GMES DG Enterprise – coordination • Space division – European Space Agency • In situ division – European Environmental Agency • Service segment – European Commission. This segment should produce “value added products” from raw data of ground and space division – e.g. landcover maps. GMES is coordinated by DG Enterprise (Ministry of Industry of EU). Leader of Space division is European space agency, European environmental agency is responsible for in situ division. There is also „service segment“ that should produce “value added products” from raw data of ground and space division – e.g. landcover maps. This part is controlled by European Commission. GMES GMES plan for 2011: Start of GMES Initial phase (2011-2013) Services preparation should start (delivery in 2013-2014): • GMES emergency management services – Mapping in support to crisis management inside and outside EU. • European Flood Alert System • Pan-EU Land Cover monitoring service Space segment preparation. First sentinel should be launched in 2013. GMES services should enter into initial operations in period 2011-2013 and into operational phase in 2014. Building of sensor networks is very important part of this initiative. What is the state of art of GMES preparation? GMES plan for 2011 says that year 2011 is start of GMES Initial phase (2011-2013) Following services are being prepared (delivery in 2013-2014): GMES emergency management services – Mapping in support to crisis management inside and outside EU. European Flood Alert System. Pan-EU Land Cover monitoring service. Space segment is also being prepared. First sentinel should be launched in 2013. SWE and GMES Is SWE framework considered in preparation of GMES? SWE tested in some GMES-related projects: e.g. OSIRIS (Open architecture for Smart and Interoperable networks in Risk management based on In-situ Sensors) • addresses the monitoring, preparation and response phases of environmental risk and crisis management (forest fires, industrial risks, water pollution, air pollution) • SOS, SensorML and O&M were used http://www.osiris-fp6.eu/ Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. TEST - answers Adobe Systems Good morning, Ladies and Gentlemen. My name is Radim Štampach. I am from the same institution and working project as my colleague Petr Duda. He presented you some basic information about sensors and SWE. I would like to speak about relationship between sensors, SWE and European spatial data initiatives – INSPIRE and GMES. Test - answers SOS is part of Sensor Web Enablement. This acronym means: ü Sensor Observation Service Save Our Souls. But not in SWE framework. > Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. Test - answers Which specification from SWE framework si the most frequently used in Data specifications of themes in Annex III? ü Observation & Measurement SensorML is only recommended for using by INSPIRE Cross Thematic Working Group on Observations & Measurements. > Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. Test - answers What is standard ISO 19156? ü Observation & Measurement specification released as ISO standard. SWE framework was not released as ISO standard. > Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. Test - answers Which from following Inspire themes use O&M in their Data specifications? o Buildings ü Soil o Human health and safety ü Environmental monitoring facilities ü Atmospheric conditions ü Meteorological geographical features Also Geology and Oceanographic geographical features. > Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. Test - answers Is European Space Agency responsible for whole GMES coordination? ü No ESA is responsible only for space segment of GMES. DG Enterprise is main GMES coordinator. > Is SWE framework considered in preparation of GMES? SWE framework and its specifications are not mentioned in documents about GMES preparation but they were tested in some projects connected ti GMES. An example can be OSIRIS project that tested using in-situ sensors for risk management. Three specifications from SWE framework were used in this project – SOS, SensorML and Observation & Measurement. Thank you for your attention! http://geotym.geogr.muni.cz Adobe Systems That is all from me about using sensors in European geospatial initiatives Ispire and GMES. Thank you for your attention. I hope that you remembered at least a few knowledges from this presentation.