Introduction Data Types Contents Package
7.3.3.3 SPSContents
This data type defines the supported encodings for tasking parameter values and provides metadata about the sensors facaded by the service. In addition, it provides information on the storage time of task and task request status information. By default, SPS servers store the last status information only. After finalization of a task or task request, any SPS service stores this information until the minStatusTime has expired. This time period starts when the task or task request transitions into a final state. Optionally, SPS servers can store any additional historic status information. SPS servers indicate this capability by adding the since parameter to the metadata of the GetStatus operation in the Capabilities document see clause 7.3.2.4.3 - Advertising Support for Status Logging on page 57. The SPSContents acts as the property provider for a SensorOffering see clause 22 in [OGC 09-001]. The SPSContents see Figure 17 type is derived from SWES AbstractContents type defined in clause 7 of [OGC09-001] and therefore inherits all the properties contained in that data type. SPSContents restricts the content model of AbstractContents in that it requires that the offering property is of type SensorOffering see clause 7.3.3.4 or a subtype thereof. Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsecontents REQ 45. The SPSContents data type shall contain the properties defined for SWES AbstractContents. In addition, it shall contain the properties according to Table 24 in combination with Table 25. Table 24 — Properties in the SPSContents data type Name Definition Data type and values Multiplicity and use minStatusTi me time period for which the services provides status information about finalized tasks or tasking requests TM_PeriodDuration, see ISO 19108 One mandatory supportedE ncoding encoding supported by the service to encode tasking parameter values SWEEncodingCode, see clause 10.2.3 in OGC 09-001 applicable code values as defined in Table 25 One or more mandatory 62 Copyright © 2011 Open Geospatial Consortium Table 25 — Code values applicable to the supportedEncoding property Applicable Code Values Additional Note http:www.opengis.netswe2.0TextEncoding best suited in most cases if ASCII encoded parameters are used http:www.opengis.netswe2.0XMLEncoding generally applicable http:www.opengis.netswe2.0BinaryEncoding suited for example for transferring image data to the service7.3.3.4 SensorOffering
This data type contains metadata about a sensor provided by the service. The SensorOffering see Figure 17 type is derived from SWES AbstractOffering defined in clause 7 of [OGC 09-001] and therefore inherits all the properties contained in that type. SensorOffering does not restrict the content model of AbstractOffering. Requirement http:www.opengis.netspecSPS2.0reqGetCapabilitiesResponsesensorOffering REQ 46. The SensorOffering type shall contain the properties defined for SWES AbstractOffering. In addition, it shall contain the property according to Table 26. Table 26 — Properties in the SensorOffering type Name Definition Data type and values Multiplicity and use observable Area the area that the sensor can observe PointOrPolygon, see clause 7.3.3.5 One mandatory The SensorOffering represents an inheritor of the properties contained in the SPSContentsParts
» OGC® Sensor Planning Service Implementation Standard
» Abstract Submitting organizations OGC® Sensor Planning Service Implementation Standard
» Specification identifier Conformance Classes
» Abbreviated terms OGC® Sensor Planning Service Implementation Standard
» Data dictionary tables Classes imported from other specifications with predefined XML encoding
» Namespace Conventions OGC® Sensor Planning Service Implementation Standard
» Introduction OGC® Sensor Planning Service Implementation Standard
» Client Server Interaction OGC® Sensor Planning Service Implementation Standard
» Introduction Task – Concept and Handling
» Tasking Parameters Tasking requests
» Reserving a Task State Handling
» Status Reporting OGC® Sensor Planning Service Implementation Standard
» Levels of Abstraction – SPS Chains
» Asynchronous Communication Information Access
» Interface Overview OGC® Sensor Planning Service Implementation Standard
» SPS Exceptions OGC® Sensor Planning Service Implementation Standard
» Introduction Data Types GetCapabilities Operation
» Operation Request – GetCapabilities GetCapabilities Operation
» OperationsMetadata section standard contents Advertising Implemented Operations
» Advertising Support for Status Logging
» Introduction Data Types Contents Package
» SPSContents SensorOffering Contents Package
» Data Types Operation Request - DescribeTasking
» Introduction Data Types Submit Operation
» Operation Request - Submit Operation Response - SubmitResponse
» Data Types GetStatus Operation
» Operation Request - GetStatus
» Operation Response - GetStatusResponse
» Data Types Operation Request – GetTask
» Operation Response – GetTaskResponse GetTask Operation
» Reference group usage Introduction
» Operation Response - DescribeResultAccessResponse AvailableOrNot
» DataAvailable DataNotAvailable UnavailableCode DescribeResultAccess Operation
» Introduction Data Types Reserve Operation
» Operation Request - Reserve Operation Response - ReservationReport
» Introduction Data Types Confirm Operation
» Operation Response - ConfirmResponse
» Introduction Data Types GetFeasibility Operation
» Operation Request - GetFeasibility
» Operation Response - GetFeasibilityResponse
» Data Types Operation Request - Update
» Operation Response - UpdateResponse
» Introduction Data Types Cancel Operation
» Operation Response - CancelResponse Exceptions
» Optional Parameters SPS tasking parameters representation
» SPS Events OGC® Sensor Planning Service Implementation Standard
» Channel based filteringSPS notification topics
» Introduction Action URIs OGC® Sensor Planning Service Implementation Standard
» actio OGC® Sensor Planning Service Implementation Standard
» Realization of PublishSubscribe OGC® Sensor Planning Service Implementation Standard
» Realization of Asynchronous RequestResponse
» Retrieving the Capabilities Document
» Getting Result Access Information for a Procedure
» Getting the Tasking Parameter Description
» Determining the Feasibility of a Tasking Request
» Task Submission Scheduling a Task Submit Reserve
» Reserving a Task Scheduling a Task Submit Reserve
» Automatic Reservation Expiration Scheduling a Task Submit Reserve
» Task Failure Scheduling a Task Submit Reserve
» Final Response Not Provided Before Latest Response Time
» Final Response is Provided Before Latest Response Time
» Task Completion Scheduling a Task Submit Reserve
» Getting Result Access Information for a Task
» Service Exceptions SPS Examples Scenario
» Notifications SPS Examples Scenario
» Using WS-Addressing SPS Examples Scenario
» Scheduled State InExecution State
» Reserved State Tasking Request Choice
» Diagrams Tasking Request State Machine
» Accepted State ChoiceA ChoiceB
» Invalid version number Common Request Response Handling
» Exception Appropriateness Exception Model Compliancy
» GetCapabilities operation facet validity Indicate support of SWE Common Encodings
» Mandatory Operations Service Metadata
» DescribeTasking operation facet validity
» Provide name for tasking parameter component
» Tasking Parameter Description Model Validity
» Tasking Parameter Usage Tasking request expiration
» GetStatus operation facet validity
» GetTask operation facet validity
» Handling requests for already deleted status information
» State handling State information storage
» Successful task submission Submit
» Identifiers for references and reference groups
» Referencing task data Result Handling
» Capability Test Conformance Class – State Logger
» GetStatus with since parameter Status history provisioning
» Capability Test Conformance Class – Reservation Manager
» Operations listed in Capabilities
» Cancel operation facet validity
» Capability Test Conformance Class – Task Updater
» Handling of updatable DataArray Handling of updatable DataRecord DataChoice
» Handling update not supported for a given procedure New identifier assignment
» State transition resulting of task update
» Operation listed in Capabilities
» SPS event encoding SPS event publication
» Capability Test Conformance Class – Channel Based PubSub
» Support of Topic Dialect Topic Set Contents
» XML Encoding Validity XML Validation Exception Reporting
Show more