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
OGC 10-135 EO Satellite Tasking Extension for SPS
Note: Programming status can also be provided for information when the demand is rejected. In this case, the response can contain a list of cells andor segments indicating
which ones have been rejected.
7.1.5.2 ProgrammingStatus Class
7.1.5.2.1 Description
This class allows the programming service to describe the status of EO acquisitions in details, enabling the user to follow the advancement of his tasks both temporally and
spatially.
As described in section §7.1.4, this SPS extension is designed to satisfy the needs of different types of EO systems and thus allows reporting status for both cells and
segments. All acquired and validated segments shall be included in the list. Segments with different states i.e. potential, planned, cancelled, rejected or failed can optionally
be included for information.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreprog-status-inc-segments
Req 21. An instance of the ProgrammingStatus class shall include all segments that
have been acquired i.e. in the ‘ACQUIRED’ or ‘VALIDATED’ state at the time the
report is generated.
If the programming system generates feasibility results using a discretization in cells, the status of these cells shall also be included in the programming status class.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreprog-status-inc-cells
Req 22. An instance of the ProgrammingStatus class shall include the list of all cells
resulting from the corresponding feasibility study if any, with an updated status.
7.1.5.2.2 Data model
The ProgrammingStatus class is a top level class and aggregates either a list of segments, a list of cells or both as required above. It shall be inserted directly in the extension slot
of a StatusReport element.
56 Copyright
© 2011
Open Geospatial
Consortium
