EO Satellite Tasking Extension for SPS OGC 10-135
«DataType»
ProgrammingStatus
«property» + extension: Any [0..]
«DataType»
Segment
«DataType»
GridCell
+cell +segment
0.. 1..
Figure 15 – UML diagram of the ProgrammingStatus class
As shown on the diagram, a list of segments shall always be provided while the list of cells is optional in general. However, for the sake of consistency, the list of cells status is
mandatory if the service uses cells as a way to express feasibility results see §7.1.4.
The following table describes attributes of this class.
Name Description
Type unit
extension Extension slot for mission specific information or future
extensions to this standard. Any
cell List of cells corresponding to the cells listed in the
feasibility study. Cells status information shall be updated every time a new acquisition is made.
GridCell segment
List of segments that have been or are going to be acquired to cover the requested area. The ProgrammingStatus class
shall at least contain all segments with a status of “ACQUIRED” or “VALIDATED” but can also contain
potential, planned, cancelled, rejected and failed segments. Segment
The GridCell and Segment classes are specified in §7.1.6.1 and §7.1.6.2 respectively.
7.1.5.2.3 XML encoding
The following schema snippet normalizes the structure of the ProgrammingStatus XML element:
element name
= ProgrammingStatus
type =
eosps:ProgrammingStatusType substitutionGroup
= gml:AbstractObject
complexType name
= ProgrammingStatusType
sequence element
name =
extension type
= anyType
minOccurs =
maxOccurs =
unbounded element
name =
segment type
= eosps:SegmentPropertyType
maxOccurs =
unbounded element
name =
cell type
= eosps:GridCellPropertyType
minOccurs =
maxOccurs =
unbounded sequence
Copyright ©
2011 Open
Geospatial Consortium
57
OGC 10-135 EO Satellite Tasking Extension for SPS
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 GetStatusResponse element:
sps:GetStatusResponse xmlns:sps
= http:www.opengis.netsps2.0
xmlns:swes =
http:www.opengis.netswes2.0 xmlns:eosps
= http:www.opengis.neteosps2.0
sps:status sps:StatusReport
swes:extension eosps:ProgrammingStatus
eosps:segment ... eosps:segment ...
eosps:cell ... eosps:ProgrammingStatus
swes:extension sps:task
http:ws.spotimage.comspsfeasibilityF2AEA58FFA12B56CC sps:task
sps:procedure http:ws.spotimage.comspssensorsSPOT-Constellation
sps:procedure sps:requestStatus
Accepted sps:requestStatus
sps:updateTime 2010-06-20T11:16:32Z
sps:updateTime sps:StatusReport
sps:status sps:GetStatusResponse
Programming status information can be inserted within a GetStatusResponse element but also within SubmitResponse, UpdateResponse or ConfirmResponse when the task is
accepted synchronously.
Requirement http:www.opengis.netspecEOSPS2.0reqcoreprog-status-valid
Req 23. The ProgrammingStatus element shall be inserted in the extension slot of
the StatusReport element describing the status of a submitted task 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. Full examples of StatusReport within GetStatus operation responses and
containing detailed programming status are provided in Annex C.
58 Copyright
© 2011
Open Geospatial
Consortium
