Data Types Operation Request - DescribeTasking
7.3.4.4 Operation Response - DescribeTaskingResponse
The DescribeTaskingResponse data type represents the response to an SPS DescribeTasking operation request. The DescribeTaskingResponse data type is derived from the SWES ExtensibleResponse data type specified in clause 9 of [OGC 09-001] and therefore inherits all the properties contained in that data type. DescribeTaskingResponse does not restrict the content model of ExtensibleResponse. Requirement http:www.opengis.netspecSPS2.0reqDescribeTaskingResponsedataType REQ 49. The DescribeTaskingResponse data type shall contain the properties defined for SWES ExtensibleResponse. In addition, it shall contain the property according to Table 30. Table 30 – Properties in the DescribeTaskingResponse data type Name Definition Data type and values Multiplicity and use taskingParameters description of tasking parameters for tasking the requested asset AbstractDataCompone nt, see clause 7.2 in [OGC 08-094] One mandatory The taskingParameter property shall be fully identified with a name defined by the SPS – see OGC 08-094 for further details. The XML Schema encoding of the DescribeTaskingResponse ensures via the soft-typed tagged value that such a name can be added by the service. The name is important for clients when certain encodings are used to encode the tasking paramter data, and the encodings require naming of SWE Common data components like the XML encoding. 66 Copyright © 2011 Open Geospatial Consortium7.3.4.5 Exceptions
Requirement http:www.opengis.netspecSPS2.0reqDescribeTaskingResponseexceptions REQ 50. When an SPS server encounters an error while performing a DescribeTasking operation, it shall return an exception message as specified in clause 7.2.7.3.4.6 Examples
Clause 9.6 provides example XML instances for the DescribeTasking operation request and response.7.3.5 Submit Operation
7.3.5.1 Introduction
The Submit operation allows SPS clients to submit a tasking request for an asset. The client encodes the tasking parameters according to the parameter description defined in the DescribeTasking response. SPS servers do a feasibility check of the request and perform the task if applicable.7.3.5.2 Data Types
The conceptual model of the Submit operation is shown in the following UML diagram.Parts
» 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