Operation response – GetSensorAvailabilityResponse Data model

EO Satellite Tasking Extension for SPS OGC 10-135 that data type. GetSensorAvailabilityResponse does not restrict the content model of ExtensibleResponse, but adds the additional properties that contain the availability time periods. It shall therefore contain the properties defined for the ExtensibleResponse data type plus the types defined in the following table. Name Definition Data Type Multiplicity responsePeriod Period for which availability has been assessed by the server. It can be different from the requested period as explained below. TM_Period One mandatory availabilityPeriod Periods of availability of the sensor. When no periods are listed, the sensor is not available at all during the response period. TM_Period Zero or more Some missions can provide many details about sensor availability while some others cannot, so that there are no special requirements on the granularity and the accuracy of the availability periods returned. The service is free to choose the level of details of the response. For example, one global period or several short periods of availability can be returned and either precise time range with hours or date only can be used. For the same reason, the server may not trim availability periods to the exact period of time given by the client in the request since that would allow for precise discovery of the system’s workload. Typically, when the requested period is small, a larger period than the one requested can be included in the response in order to prevent clients from discovering more precise information by issuing multiple well-chosen requests. The responsePeriod also indicates the period for which availability was really assessed. For instance, when the requested period is large i.e. more than one year in the future, the ground segment may not be available to provide information on the system availability for the whole period. Instead, the server can describe its availability only up to its maximum planning horizon and indicate this with the responsePeriod attribute in the response.

8.1.3 XML Encoding

The following XML schema snippet normalizes the XML encoding of the GetSensorAvailability class. element name = GetSensorAvailability type = eosps:GetSensorAvailabilityType complexType name = GetSensorAvailabilityType complexContent extension base = swes:ExtensibleRequestType sequence element name = sensor type = anyURI element name = requestPeriod complexType sequence element ref = gml:TimePeriod sequence Copyright © 2011 Open Geospatial Consortium 79 OGC 10-135 EO Satellite Tasking Extension for SPS complexType element sequence extension complexContent complexType Requirement http:www.opengis.netspecEOSPS2.0reqgsarequest-valid Req 41. The XML message encoding a GetSensorAvailability request shall be valid with respect to the getSensorAvailability.xsd XML schema. The server shall correctly reject an invalid request by returning the proper correctly formatted exception as defined in [OGC 06‐121] and [OGC 09‐001]. The following XML schema snippet normalizes the XML encoding of the GetSensorAvailabilityResponse class. element name = GetSensorAvailabilityResponse type = eosps:GetSensorAvailabilityResponseType complexType name = GetSensorAvailabilityResponseType complexContent extension base = swes:ExtensibleResponseType sequence element name = responsePeriod complexType sequence element ref = gml:TimePeriod sequence complexType element element name = availabilityPeriod minOccurs = maxOccurs = unbounded complexType sequence element ref = gml:TimePeriod sequence complexType element sequence extension complexContent complexType Requirement http:www.opengis.netspecEOSPS2.0reqgsaresponse-valid Req 42. The XML message encoding a GetSensorAvailabilityResponse shall be valid with respect to the getSensorAvailability.xsd XML schema. Below is an example GetSensorAvailability request along with the corresponding response: GetSensorAvailability service = EOSPS version = 2.0 xmlns = http:www.opengis.neteosps2.0 xmlns:gml = http:www.opengis.netgml3.2 80 Copyright © 2011 Open Geospatial Consortium