EO Satellite Tasking Extension for SPS OGC 10-135
«DataType»
FeasibilityStudy
«property» + expirationDate:
DateTime + estimatedCost: Measure [0..1]
+ successRate: Real
+ informationUsed: InformationT ype [1..] + extension: Any [0..]
«DataType»
GridCell
«DataType»
Segment
«CodeList»
InformationType
«property» + KINEMAT IC MODEL: CharacterString
+ CLIMAT E STAT IST ICS: CharacterString + WEAT HER FORECAST: CharacterString
+ EST IMAT ED WORKLOAD: CharacterString + REAL WORKLOAD: CharacterString
+segment 0..
+cell 0..
Figure 14 – UML diagram of the FeasibilityStudy class
Attributes of this class are described below:
Name Description
Type unit
expirationDate Date of expiration of the feasibility study i.e. the task is
guaranteed to be executed as described in the feasibility study if submitted before this date.
DateTime estimatedCost
Estimated cost to cover the requested area with the requested parameters. This includes the cost of the programming and the
cost of the acquired image themselves. Measure
currency unit successRate
Overall success rate of the proposed acquisition. This is the probability that the whole requested area will be covered
possibly N times in the case of time series with the specified acquisition parameters before the end of the time period.
Real
informationUsed Type of information used to do the simulation and compute the
feasibility result. Several ones can be specified. CodeList
- KINEMATIC MODEL - CLIMATE STATISTICS
- WEATHER FORECAST - ESTIMATED WORKLOAD
- REAL WORKLOAD
extension Extension slot for mission specific information or future
extensions to this standard. Any
cell A list of cells is included when providing feasibility results in a
statistical form. Each cell represents a subset of the region of interest for which statistics have been computed. Cells should
not overlap. GridCell
segment List of potential segments to be acquired to cover the region of
interest. Note that when the same area can be covered by different segments at different dates, all the possible segments
can be listed here but only some of them will actually be acquired. Segments can overlap.
Segment
The GridCell and Segment classes are specified in §7.1.6.1 and §7.1.6.2 respectively. Copyright
© 2011
Open Geospatial
Consortium 53
OGC 10-135 EO Satellite Tasking Extension for SPS
Requirement http:www.opengis.netspecEOSPS2.0reqcorefeasibility-study-acc-obj-status
Req 17. The value of the status attribute of GridCell and Segment instances shall be
‘POTENTIAL’ when these objects are used within a feasibility study report with a
request status of ‘Accepted’ i.e. feasible.
Requirement http:www.opengis.netspecEOSPS2.0reqcorefeasibility-study-rej-obj-status
Req 18. The value of the status attribute of the GridCell and Segment instances shall
be ‘POTENTIAL’ or ‘REJECTED’ when these objects are used within a feasibility study
report with a request status of ‘Rejected’ i.e. not feasible.
7.1.4.2.3 XML encoding
The following schema snippet normalizes the structure of the FeasibilityStudy XML element:
element name
= FeasibilityStudy
type =
eosps:FeasibilityStudyType substitutionGroup
= gml:AbstractObject
complexType name
= FeasibilityStudyType
sequence element
name =
expirationDate type
= dateTime
element name
= estimatedCost
type =
gml:MeasureType minOccurs
= element
name =
successRate type
= double
element name
= informationUsed
type =
eosps:InformationTypeType maxOccurs
= unbounded
element name
= extension
type =
anyType minOccurs
= maxOccurs
= unbounded
element name
= segment
type =
eosps:SegmentPropertyType minOccurs
= maxOccurs
= unbounded
element name
= cell
type =
eosps:GridCellPropertyType minOccurs
= maxOccurs
= unbounded
sequence attribute
ref =
gml:id use
= optional
complexType
This element shall be inserted within an extension slot of the StatusReport element defined in the SPS interface standard [OGC 09-000]. The example below shows this
within a GetFeasibilityResponse element:
sps:GetFeasibilityResponse xmlns:sps
= http:www.opengis.netsps2.0
xmlns:swes =
http:www.opengis.netswes2.0 xmlns:eosps
= http:www.opengis.neteosps2.0
sps:result sps:StatusReport
swes:extension eosps:FeasibilitysStudy
eosps:expirationDate 2010-05-27T10:30:32Z
eosps:expirationDate eosps:successRate
82 eosps:successRate
eosps:informationUsed KINEMATIC MODEL
eosps:informationUsed eosps:informationUsed
CLIMATE STATISTICS eosps:informationUsed
eosps:segment ... eosps:cell ...
eosps:FeasibilitysStudy
54 Copyright
© 2011
Open Geospatial
Consortium
EO Satellite Tasking Extension for SPS OGC 10-135
swes:extension sps:task
http:ws.spotimage.comspstasksF0112F56ADE2A56CB sps:task
sps:procedure http:ws.spotimage.comspssensorsSPOT-Constellation
sps:procedure sps:status
Accepted sps:status
sps:updateTime 2010-05-20T10:30:32Z
sps:updateTime sps:StatusReport
sps:result sps:GetFeasibilityResponse
Feasibility study information can be inserted within a GetFeasbilityResponse element or within a GetStatusResponse element in the case the call to GetStatus was used to retrieve
the results of a feasibility study asynchronously.
Requirement http:www.opengis.netspecEOSPS2.0reqcorefeasibility-study-valid
Req 19. The FeasibilityStudy XML element shall be inserted in the extension slot of
the SPS StatusReport element describing the status of a feasibility study and be valid
with respect to the eoTaskingExtensions.xsd schema.
Details of the segment and cell elements have been omitted for clarity in the snippet above and are detailed in sections §0 and §7.1.6.2 respectively. Full examples of
StatusReport containing feasibility analysis results are provided in Annex C.
7.1.5 Programming status model
7.1.5.1 Introduction
In addition to the basic information included in the status reports defined in the SPS standard, detailed EO system programming status shall also be provided by an SPS
supporting this extension. Such information is essential to provide a spatio-temporal view of the advancement of on-going data acquisitions. This information shall be inserted in
the StatusReport in the response to a GetStatus, Submit, Update or Confirm request resulting from a task submission as soon as the task is in execution i.e. task status
changes to “InExecution”. The ProgrammingStatus class described in this clause describes the information model and encoding to be used to provide detailed status of on-
going acquisitions.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreprog-status-report
Req 20. A StatusReport describing the state of a programming task and with the task
status ‘InExecution’ shall include an instance of the ProgrammingStatus class.
Copyright ©
2011 Open
Geospatial Consortium
55
