The Sensor Planning Service technical note [RD6] presents the results of the Technology Watch on the SPS activities within GEOSS, INSPIRE, and GMES.

One main conclusion of the Technical Watching activity states that the Sensor Planning Service is not used and implemented at the same level within the initiatives.

The INSPIRE directive states that "INSPIRE does not require the collection on new spatial data". However, access to observation (information) coming from EO sensor is within the INSPIRE Directive (Annex II/III) such as Ortho-Imagery and DEM and other themes could have sensors as sources (both EO and In Situ). For those themes, SPS should be used as a possible service in conjunction with others (e.g. WPS) in order to provide access to the data.

In GMES and GEOSS, the implementation of SPS only shows differences on the technical aspect:

• GMES CDS is based on SPS profile with a very detailed interface that restricts the SPS service. This implementation by restriction and not by extension regarding the SPS standard specification should preserve the interoperability. From a technical point of view, SPS is using a SOAP binding.
• GEOSS is based only on SPS version 1.0 using a RESTful binding.

The SPS analysis was complemented by taking into account the usage of SPS in the scope of the EU FP7 project SANY. This project implements a first version of SPS with no recommended binding (this corresponds to the approach applied in GEOSS). Please note that this analysis for SANY was based on SANY Sensor Service Architecture V1.

In the following, please find a list of core issues identified in the Technology Watch on SPS for each of the initiatives:

• GMES CDS: It is very well documented due to the constraint of an existing implementation planning for GMES pre-operational services.
• GEOSS is approaching the global access to sensor and not only from a sensor availability point of view.
• There is no GMES FP6/7 project using SPS, the main reason is due to GMES FP6/7 projects such as Geoland2 for Land Cover are dedicated to value added chain.
• There are other projects from FP6/7 using SPS or other SWE suite services such as SANY. However it is pointed out that for SANY, the information coming from EO sensor are not directly accessed by user. The user accesses only thematic information through value added product (via a SOS).

Download full document from GIGAS

soap, rest, sensor web

gmes, seis, geoss

Last updated 852 days ago by Simon Cox