1. HMA 5-6 July 2010 – Slide 1 Daniele Marchionni Elsag Datamat Stefania Pappagallo Elsag Datamat HMA Follow On Task 4 - Order MTR 5-6 July 2010

2. HMA 5-6 July 2010 – Slide 2 Task 4 – Preliminary Review – Agenda  Task 4 Activities Status  HMA Ordering ICD evolution  HMA Ordering ETS (con terra presentation)  Reference Order Server - OPGW

3. HMA 5 – 6 July 2010 – Slide 3 Task 4 – Activities Status - Deliverables  Deliverables for MTR Ordering Services for Earth Observation Products OGC 06-141r3 V0.9.5 04/07/2010 Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – 23/06/2010 (Technical Note) Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – 23/06/2010 (CTL Scripts) Reference Order Server documentation: OPGW Software Validation Specification – SVS V1.0 25/06/2010 OPGW Software Installation Document – V1.0 25/06/2010 Re-issue after PR: OPGW Software Requirements Specification – SRS V1.1 25/06/2010 OPGW Software Design Document – SDD v1.1 25/06/2010

4. HMA 5 – 6 July 2010 – Slide 4 Task 4 – Activities Status - Deliverables  Deliverables for MTR Additional documents prepared since PR:  Improvement of Ordering Options Handling Technical Note - V1.0 04/03/2010  Analysis of GetQuotation in case of distributed ordering servers – V1.0 07/06/2010

5. HMA 5 – 6 July 2010 – Slide 5 Task 4 – Activities Status - SWG  Ordering Services for Earth Observation Products SWG Two updates to the ICD have been prepared since PR:  OGC 06-141r2 V0.9.5 draft 3, 08/03/2010  OGC 06-141r3 V0.9.5, 04/07/2010

6. HMA 5 – 6 July 2010 – Slide 6 Task 4 – Activities Status - SWG  A number of issues have been raised (http://portal.opengeospatial.org/?m=projects&a=v iew&project_id=325&tab=5):http://portal.opengeospatial.org/?m=projects&a=v iew&project_id=325&tab=5 21 issues closed with V0.9.5 draft 1 4 issues closed with V0.9.5 draft 2 3 issues closed with V0.9.5 draft 3 9 issues closed with V0.9.5 1 issue currently open (OWS 1.2)

7. HMA 5 – 6 July 2010 – Slide 7 Task 4 – Activities Status - SWG  Next activities: To go for voting for the 30 days public comment period

8. HMA Ordering ICD (OGC 06-141r3) Evolution  Summary of Changes: Implemented pending comments from RFC review:  Document reformatted according to the updated OGC policies  Requirements included in the document  ATS included in annex (from con terra TN) Completed list of pre-defined order options (order options TN included in the document) Clarification of Error Handling Better description of Asynchronous operations Alignment with SPS, SWE from TASK2 Included GML 3.2.1, as derived from SPS, SWE alignment Added usage of WS-notification Some minor corrections Schemas have Internet references + local copies via “Catalog” feature (XML Spy) 5-6 July 2010 – Slide 8

9. HMA Changes – Updated format  Alignment with “Template for OWS Implementation Standards” (OGC 05-009r3) (ISSUE tracker#438) The Ordering ICD has been reformatted according to the template and guidelines for writing and formatting the OWS specifications. Main changes:  A dedicated chapter for each service operation  For each operation (chapter): –Added XSD fragments describing the main items of the operation request and response –Added XML request and response examples –Added the list of exceptions –Added the list of requirements for compliance testing 5-6 July 2010 – Slide 9

10. HMA Changes – Added requirements  Alignment according to “The Specification Model A Standard for Modular specifications”(OGC 08-131r3) (ISSUE tracker#462) For each service operation a requirements section has been added specifying all the requirements a server must comply with (and the ATS refers to these sections). 5-6 July 2010 – Slide 10

11. HMA Changes – Added requirements  Some example requirements (from GetStatus): Req 59. The Order Server shall implement the GetStatus operation. Req 60. The GetStatus operation shall be a synchronous operation. Req 61. The GetStatus request shall be called by order identifier or by search criteria. Req 62. The GetStatus request shall contain the type of presentation to provide within the response. The order server shall support either brief or full or both presentations. Req 63. The GetStatus request by search criteria shall be called by last update or by order status or by order reference. 5-6 July 2010 – Slide 11

12. HMA Changes – Added requirements 5-6 July 2010 – Slide 12 OperationNumber of requirements GetCapabilities7 GetOptions18 GetQuotation16 Submit13 GetStatus14 DescribeResultAccess10 Cancel10 TOTAL88  Statistics:

13. HMA Changes - Added ATS  To comply with OGC 05-009r3 and OGC 08-131r3 the ATS, prepared by con terra as separated document, has been included in the spec (Appendix A).  A number of conformance classes have been defined considering the different operations, the type of order (products, subscription, tasking), the type of interaction (sync / async). 5-6 July 2010 – Slide 13

14. HMA Changes - Identification of Order Options  Implementation of ISSUE Tracker #460: finalization of order options.  The objective of the issue was to improve the list of order options specified in the document gathering inputs from the different ground segments.  The inputs have been analyzed and harmonized in the Technical Note: “IMPROVEMENT OF ORDERING OPTIONS HANDLING TECHNICAL NOTE”  The TN has been merged in the document (table added at §7.3.4) 5-6 July 2010 – Slide 14

15. HMA Some example of Order Options 5-6 July 2010 – Slide 15 ParameterIDTypeMissionDescription compression swe:DataRec ord/ swe:field/ swe:Category EUMETSATType of compression applied to the delivered products. E.g.: none, zip, gzip, bzip2, pkzip, comp consolidation swe:DataRec ord/ swe:field/ swe:Category ESA/ENVISAT (low bit rate) Allow to define if the processing is consolidated or not. Some example of allowed values: – unconsolidated – consolidated format swe:DataRec ord/ swe:field/ swe:Category ESA/ENVISAT ESA/ALOS ESA/ERS ESA/JERS ESA/IRS P6 ESA/KOMPSAT2 ESA/UKDMC 1 ESA/IKONOS 2 ESA/SPOT ESA/Landsat EUMETSAT Format file to use for delivery data. Between the possible values there is also the JPEG2000 format, in this case it has not to use the compression. Some examples of allowed values: – ENVISAT – jpeg2000LL – jpeg2000LS – TIFF/1byte – TIFF/2bytes – DIMAP – GEOTIFF –.... geoCorrection swe:DataRec ord/ swe:field/ swe:Category ESA/ALOS ESA/JERS ESA/Landsat Geometric Correction. Example allowed values: – geo-coded – geo-referenced.

16. HMA Some example of Order Options 5-6 July 2010 – Slide 16 ParameterIDTypeMissionDescription mapDirection swe:DataRec ord/ swe:field/ swe:Category ESA/ALOSAllow to define the direction for the map. Possible allowed values: – map north – true north mapProjection swe:DataRec ord/ swe:field/ swe:Category ESA/ALOSAllow to define the projection for the map. Possible allowed values: –UTM –PS –ARC –TPL polarisation swe:DataRec ord/ swe:field/ swe:Category ESA/ENVISAT ASARAllow to choose the polarisation. Possible allowed values: – HH/VV – HH/HV – VV/VH – default – H/H – V/V processingLevel swe:DataRec ord/ swe:field/ swe:Category ESA/ALOS ESA/NOAA ESA/NIMBUS ESA/SEASTAR ESA/IRS ESA/SPOT EUMETSAT Level associated to the products. For the naming convention see Table 5 ‑ 1. E.g: for ESA ALOS AVNIR-2 Possible values are: – 0 – 1A – 1B1 – 1B2

17. HMA Alignment with SPS, SWE Order Option Description 5-6 July 2010– Slide 17  06-141r2 V0.9.5 Draft3

18. HMA Alignment with SPS, SWE Order Option Description  06-141r3 V0.9.5 5-6 July 2010 – Slide 18

19. HMA Alignment with SPS, SWE Order Option Setting 5-6 July 2010 – Slide 19  06-141r2 V0.9.5 Draft3

20. HMA Alignment with SPS, SWE Order Option Setting  06-141r3 V0.9.5 5-6 July 2010 – Slide 20

21. HMA OGC 06-141 Issues  Alignment with TASK 2: Some problems have been noticed integrating the schemas of SPS, SWE:  Problem on swesNotification.xsd  Seems due to this: Missing schema location (additionally GML 3.2 ?) 5-6 July 2010 – Slide 21

22. HMA OGC 06-141 Issues Sep 2009 – Slide 22 Problem on t-1.xsd (WS notification)

23. HMA OGC 06-141 Issues  Joint usage of SPS and OS: Pending action:  HMAFO-T4-02 (DM/ED): Investigate proposal by Spotimage to have SPS URL and Task ID as separate fields in Submit to allow linking programming and ordering as per MoM.  Integration of Catalogue and Ordering Because the ordering is performed after the catalogue browsing, and the link is simply the catalogue identifier, then some coordination has to be done between TASK1 and TASK4, in order that the items returned by the TASK1 Reference Catalogue can be ordered by TASK4 Reference Order Server. 5-6 July 2010 – Slide 23

24. HMA Reference Order Server - Overview  A reference order server will be set-up with the following objectives: Demonstrate the updated specification; Support the implementation of ordering clients; Support the implementation of ordering servers.  Since ordering process implies processing, formatting and delivering to the user of the required products, then a fully functional order server would mean a complete ordering handling system for EO products.  The order server that will be implemented is a system that will provide to the client an OGC 06-141 compliant interface, but the ordering functionality is accomplished by calling an actual order handling system (M2EOS – going operational next week).  The order server that will be provided is the evolution of Ordering & Programming Gateway – OPGW already implemented in previous HMA-I and HMA-E projects. 5-6 July 2010 – Slide 24

25. HMA Reference Order Server - Context 5-6 July 2010 – Slide 25

26. HMA Reference Order Server - Context  External Entities: HMA Client: TEAM Engine, SSE EOLI XML Catalogue Server (M2EOS – M2CS Catalogue)  Called for getting details about the product to order EOLI XML Order Server (MMOHS via M2EOS)  The input HMA Order is translated in the corresponding EOLI XML Order for being actually executed OPGW Operator  Provides the order options configuration and some ESA GS users External OGC 06-131 Catalogue  This is the OGC Catalogue storing the EO Product metadata to be queried and ordered from the HMA Client. 5-6 July 2010 – Slide 26

27. HMA Reference Order Server - Documentation  MTR Documents: OPGW Software Validation Specification – SVS V1.0 25/06/2010 OPGW Software Installation Document – V1.0 25/06/2010 Re-issue after PR: OPGW Software Requirements Specification – SRS V1.1 25/06/2010 OPGW Software Design Document – SDD v1.1 25/06/2010 just update of Applicable Documents (UM ICD V0.0.6) 5-6 July 2010 – Slide 27

28. HMA OPGW SVS – Approach 5-6 July 2010 - Slide 28  OPGW Software Validation Specification Document has been prepared following the ECSS Space engineering ECSS-E-ST-40C DRD.  Tests have been derived from OPGW SVTS (Software Validation Testing Specification) prepared in the frame of HMA-E Project, tailoring with respect to HMA FO needs:  Updated Ordering ICD  Removed Programming Service Due to the re-use of the already available software, the Test Procedure section has been provided even if the Reference Order Server is not available yet in this phase of the project.

29. HMA OPGW SVS – Approach 5-6 July 2010 - Slide 29  SVS Overview: TD_001, TC_001_001: for verifying the OPGW installation and Configuration TD_010, for verifying the compliance with respect to the Ordering Protocol  For each operation a dedicated test case has been defined e.g.: –TC_010_001: Ordering Service – GetCapabilities –TC_010_010: Ordering Service – GetOptions –TC_010_020: Ordering Service – GetQuotation –TC_010_030: Ordering Service – Submit –.... TD_020, for verifying the compliance with respect to the joined SPS server

30. HMA OPGW SVS – Approach 5-6 July 2010 - Slide 30  SVS Overview: For each test case several test messages have been foreseen (Inputs and Outputs specifications paragraph of TCs) for covering the different cases and non-nominal conditions of each operation e.g.:

31. HMA OPGW Software Installation Document - Overview 5-6 July 2010 – Slide 31  The OPGW Software Installation Document has been prepared re- using the already available OPGW installation document (to be noted that in this phase of the project the reference order server is not available yet).  This document will be finalized in the next phase of the project, when the reference order server for HMA FO will be implemented.