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
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
