Copyright © 2011 Open Geospatial Consortium 9
Table 2 — Implementation of types from OWS Common [OGC 06-121r3] UML class
object element type
property type
AbstractMetadata ows:AbstractMetaData -
- GetCapabilities -
ows:GetCapabilitiesType -
LanguageString - ows:LanguageStringType
- OWSServiceMetadata -
ows:CapabilitiesBaseType - ReferenceGroup ows:ReferenceGroup
ows:ReferenceGroupType -
Table 3 — Implementation of types from SWE Common Data Model [OGC 08-094] UML class
object element type
property type
AbstractDataCom ponent
swe:AbstractDataCo mponent
swe:AbstractDataCompo nentType
swe:AbstractDataComponentP ropertyType
AbstractEncoding swe:AbstractEncodin g
swe:AbstractEncodingTy pe
swe:AbstractEncodingPropert yType
Table 4 — Implementation of types from SWE Service Model [OGC 09-001] UML class
object element type
property type
AbstractContents swes:AbstractContent s
swes:AbstractContentsTy pe
swes:AbstractContentsProper tyType
AbstractOffering swes:AbstractOffering swes:AbstractOfferingTy
pe swes:AbstractOfferingProper
tyType ExtensibleRequest swes:ExtensibleReque
st swes:ExtensibleRequestT
ype swes:ExtensibleRequestProp
ertyType ExtensibleRespons
e swes:ExtensibleRespo
nse swes:ExtensibleResponse
Type swes:ExtensibleResponsePro
pertyType NotificationProduc
erMetadata swes:NotificationProd
ucerMetadata swes:NotificationProduce
rMetadataType swes:NotificationProducerM
etadataPropertyType
10 Co
5.6 Namespace Conventions
This standard uses a number of namespace prefixes throughout; they are listed in Table 5. Note that the choice of any namespace prefix is arbitrary and not semantically significant.
Table 5 — Prefixes and Namespaces used in this standard Prefix Namespace
gml http:www.opengis.netgml3.2 ows http:www.opengis.netows1.1
soap11 http:schemas.xmlsoap.orgsoap soap12 http:www.w3.org200305soap-envelope
swe http:www.opengis.netswe2.0 swes http:www.opengis.netswes2.0
wsa http:www.w3.org200508addressing wsn-b http:docs.oasis-open.orgwsnb-2
xs http:www.w3.org2001XMLSchema
pyright © 2011 Open Geospatial Consortium
Co
6 Sensor Planning Service – Abstract Overview
6.1 Introduction
The operational context of the SPS is abstracted from, and therefore applies to, several areas of interest. In the scientific area there is a constant interplay between facts, and
theories that explain the facts, which then gives rise to the need for more information in order to confirm and extend the theories. Similarly, in the medical area symptoms give
rise to a need for information that calls for tests that support diagnosis. In the military area there is always a great deal that is unknown about a battle space, or about a theatre
of operations other than war, which gives rise to needs for specific useful information. In the business area corporations and other non-governmental organizations have a need for
global economic intelligence.
All of these areas have information needs, and the SPS is used to task assets to satisfy those needs. The SPS provides an interface to parameterize assets and asset management
systems. It can be applied whenever a client is allowed to influence the internal processes of such a system. The SPS does not provide direct access to the information gathered by
the system itself. This will be done via a SOS or some other OGC Web service. It rather serves as an interface layer to the parameterization interface of the underlying system
see Figure 2.
Figure 2 — SWE Interface of an Asset Management System
The SPS is an interface to a system of any complexity. The system itself is considered as a black box. In this black box, some sort of process gets executed that can be manipulated
by setting specific parameters.
Example: a webcam takes pictures every minute. The SPS interface to this webcam allows modifying this time interval to anything between 10sec and 1hr.
Example: A more complex example is that of a satellite. The SPS interface allows to set a number of parameters, such as region of interest, time of interest, incidence angle with azimuth and elevation, ground resolution etc.
It is up to the SPS provider to define which parameterization options are available to clients via the SPS interface of the given service.
A system operator may even decide to have a chain of SPS instances to provide different capabilities to different types of users for the very same asset.
pyright © 2011 Open Geospatial Consortium 11
