DataAvailable DataNotAvailable UnavailableCode DescribeResultAccess Operation
7.3.8.8 DataNotAvailable
This data type expresses that no data is available. Requirement http:www.opengis.netspecSPS2.0reqDataNotAvailabledataType REQ 77. The DataNotAvailable data type shall contain the properties according to Table 48. Table 48 — Properties in the DataNotAvailable data type Name Definition Data type and values Multiplicity and use message human readable message that provides further information or reason why no data is available LanguageString, see clause 10.7 in [OGC 06-121r3] Zero or more optional Include one for each language represented unavailabl eCode identifies the reason why data is unavailable UnavailableCode, see clause 7.3.8.9 One mandatory7.3.8.9 UnavailableCode
This type is a list of codes signifying the reason why result access information for a given task or sensor is not available. Copyright © 2011 Open Geospatial Consortium 101 Requirement http:www.opengis.netspecSPS2.0reqDescribeResultAccessResponseUnavailableCode REQ 78. The UnavailableCode code list shall contain the propertieschoices according to Table 49. Table 49 — Properties in the UnavailableCode code list Name a Definition Value DataNotAvailable Result access information is not available because no data has been published yet. “DataNotAvailable” DataServiceUnava ilable Result access information is not available because one or more of the services that are assigned to store the data gathered in a task is currently unavailable. “DataServiceUnavailable” a Although some values listed in the column appear to contain spaces, they shall not contain spaces. The code list is extensible. The pattern for new codes is the regular expression: other: [A-Za-z0-9_]{2,} However, for interoperability reasons a service should not use an arbitrary code that is not defined by an official SPS extension.7.3.8.10 SPSMetadata
This data type provides SPS specific metadata for service references given in a DescribeResultAccessResponse. The SPSMetadata data type is derived from the OWS Common AbstractMetadata data type [OGC 06-121r3]. That data type does not define any property and thus SPSMetadata does not inherit any property from it. However, it is a child of AbstractMetadata and thus is a valid substitute whenever such metadata is provided, for example in references see clause 7.3.8.1.2. Requirement http:www.opengis.netspecSPS2.0reqDescribeResultAccessResponseSPSMetadata REQ 79. The SPSMetadata data type shall contain the properties according to Table 50. 102 Copyright © 2011 Open Geospatial Consortium Table 50 — Properties in the SPSMetadata data typeParts
» 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