1. HMA Follow On Activities
Task 2: Feasibility Analysis Service
(Sensor Planning Service)
Final Presentation
XX 2011
Reuben Wright, Deimos Space

2. Open Source Development
Achievements
Deliverables
Specifications
Executable Test Suite
Open Source Development
SF Client
SF Server
Demonstrations

3. Deliverables

4. Specifications
Three specifications were written and gained OGC adoption:
sweCommon 2.0 (Data Model and Service Model)
Sensor Planning Service 2.0
EO Extension for Sensor Planning Service 2.0
Modular Specification Model used

5. Published as OGC 08-094 and OGC 09-001
sweCommon
Published as OGC and OGC
Comprises SWE Common Data Model and SWE Common Service Model.
Specifications published at:
Schemas published at: …
Used by:
Sensor Planning Service 2.0, Order Handling Service … …

6. Provides a set of Data Models
SWE Data Model – OGC
Provides a set of Data Models
Low level data models for exchanging sensor related data
Allow applications and/or servers to structure, encode and transmit sensor datasets
Structures are self describing
Structures can be linked to semantic definitions

7. SWE Service Model – OGC 09-001
Provides the following packages of datatypes and operations
Contents – data types for sensor services
Notification – data types for notification capabilities, and also definition and encoding of SWES events
Common - common data types for other packages
Common Codes – commonly used lists of codes with semantics
DescribeSensor – operation to retrieve sensor metadata
UpdateSensorDescription – operation to modify sensor description
InsertSensor – operation
DeleteSensor – operation

8. Sensor Planning Service 2.0
Specifications published at:
Schemas published at:
Provides a set of operations to:
Query about the capabilities of a sensor and how to task it
Determine the feasibility of a sensor planning request
Submit and reserve/commit a request
Find out the status of a request
Update or cancel such a request
Request information about access to the data collected

9. Sensor Planning Service 2.0 Operations 1/2
Mandatory Interface (Operation Group) 9

10. Sensor Planning Service 2.0 Operations 2/2
Optional Interfaces (Operation Group) 10

11. EO Sensor Planning Service 2.0
Specifications published at:
Schemas published at:
Provides an extension to SPS specifically for EO:
New Operations to support the way the industry works
Defined and registered common parameters to aid interoperability
New operations to:
Validate acquisitions made in response to a task
Find long term information on the availability of a sensor
Submit tasking requests related to individual segments of a task

12. EO Sensor Planning Service 2.0 Parameters
Provides Tasking Parameters
for all missions (eg. how to specify Region and Time of interest)
for Optical (eg. MinLuminosity)
for Radar (eg. polarizationMode)
Provides Validation Parameters
for Optical (eg. MaxCloudCover)
for Radar (eg. maxNoise)
Parameters are in OGC registry
Includes names, datatypes and semantics
Allows reuse
Allows RDF/Ontology support to link semantics to other definitions

13. EO Sensor Planning Service 2.0 Executable Test Suite
Executable Test Suite written in CTL
In the EO SPS Abstract Test Suite there are 31 core tests:
Have implemented 23 of these tests as a first release ETS.
Any limitations are documented in the test scripts.
The parts not implemented are because the specification says it is:
to be a manual check or to run a different ETS (for the core SPS), or require TEAM Engine to be able to handle asynchronous testing.

14. EO SPS 2.0 Executable Test Suite - Reusable function
Provides ability to modify a provided set of parameters programatically. This means a “base” request can be edited to create the various test messages.
<ctl:call-function name="ModifyRequest">
<ctl:with-param name="Request" select="."/>
<ctl:with-param name="Modifications">
<Element name="procedure" namespace=" text="{$sensorID}"/>
<Element name="GetFeasibility" namespace="
<swes:extension>
<eo:FeasibilityLevel>COMPLETE</eo:FeasibilityLevel>
</swes:extension>
</Element>
</ctl:with-param>
</ctl:call-function>

15. SFRE Development (SF Client and SF Server)
Fully working reference implementations – client and server
All the EO SPS Operations have been successfully implemented:
GetCapabilities, GetSensorAvailability
DescribeSensor, DescribeTasking
GetFeasibility, Submit
Cancel, Update
Reserve, Confirm
GetStatus, DescribeResultAccess
Validate
SF server also implements Notifications
Code is to be released as Open Source
[Question : More detail useful? Or just show demo?]

16. Other (non-Open Source) code
SPOT Image SPS Server
Deployed at:
SF Client configured to use it (as well as SF Server)
Ad hoc SF Client testing and ETS testing has been carried out
Not Open Source.
Earth Explorer CFI
Used in SF Server, with the libraries included in the delivered code.
Collection of multiplatform precompiled C libraries for timing, coordinate conversions, orbit propagation, satellite pointing calculations, and target visibility calculations.
SF Server does not include the source code of the software. Library is provided under the Earth Observation CFI Licence Terms and Conditions -

17. What Next
To Do
...

18. Demonstration To Do Summary of steps/storyboard...
Would this perhaps be better as a separate presentation (covering all the tasks)?

19. Thanks for listening Questions Any Questions before
SF Client and SF Server
Demonstration?

20. Extra Slides - if there any questions on the technical details of standards or development/design.
SF Client UI (final UI in Operations Manual)
SPS 2.0 operations
EO Extension for SPS 2.0 parameters and operations
Sensor Feasibility Reference Environment architecture

21. SF Client screenshots
SF Client UI
3D Map
Sensor selection
Tasking Parameters (sent to SF Server)
Display of Server responses (Feasibility Analyses)

22. SF Client screenshots

23. SF Client screenshots

24. SF Client screenshots

25. SF Client screenshots

26. SF Client screenshots

27. SF Client screenshots

28. SF Client screenshots

29. SF Client screenshots

30. Sensor Planning Service 2.0 Operations 1/2
Mandatory Interface (Operation Group) 30

31. Sensor Planning Service 2.0 Operations 2/2
Optional Interfaces (Operation Group) 31

32. EO Extension for Sensor Planning Service 2.0
SPS Tasking Parameters for all missions 32

33. EO Extension for Sensor Planning Service 2.0
SPS Tasking Parameters for all missions 33

34. EO Extension for Sensor Planning Service 2.0
SPS Tasking Parameters for all missions 34

35. EO Extension for Sensor Planning Service 2.0
SPS Tasking Parameters specific to Optical and Radar 35

36. EO Extension for Sensor Planning Service 2.0
Validation parameters specific to Optical and Radar 36

37. EO Extension for Sensor Planning Service 2.0
SPS Feasibility Study Parameters 37

38. EO Extension for Sensor Planning Service 2.0
SPS Status Parameters 38

39. EO Extension for Sensor Planning Service 2.0
New Operation: GetSensorAvailability 39

40. EO Extension for Sensor Planning Service 2.0
New Operation: Validate 40

41. EO Extension for Sensor Planning Service 2.0
New Operation: SubmitSegmentByID
Response is classical SPS SubmitResponse 41

42. EO Extension for Sensor Planning Service 2.0
Additional Notification Topics
SegmentPlanned
SegmentAcquired
SegmentValidated
SegmentCancelled
SegmentFailed 42

43. SF Client Architecture WorldWind Google Web Toolkit Apache Tomcat
Web Browser
Web Server
MySQL DB
WorldWind
Google Web Toolkit
Apache Tomcat
SPS Library

44. SF Server Architecture Earth Explorer Mission CFI Apache Axis
SPS Controller
Notifications
Planning System
Earth Explorer
Mission CFI
Apache Axis
SPS Library
Notification Library

45. SF Server State management Submit Reserve Confirm Update
Simulated acquisitions
May fail (eg weather)
Database updated
Notifications triggered
Get Status responses updated