Loading...
 
ESA > Join & Share > HMA > HMA-FO Progress Task 3 1001
Print

HMA-FO Progress Task 3 1001

!Project Manager Assessment

  • The status of the project is nominal.

Key Problem List

  • None

Deliverables Table

  • Requirement Baseline Document (RB)
  • Technical Specification Document (TS)
  • Specification Dependencies (TN)
  • Design Justification File (DJF)
  • Design Definition File (DDF)

WP1000 Project Management

Activities performed

  • Progress Meeting (and minutes, actions etc)
  • Coordination with subcontractors
  • Progress report updated

Outcome and results

  • Presentations for PR and AWG Meeting

Problems and concerns

  • None

Plans for next period

  • General Project Management work
  • Progress Review Meeting
  • Update PMP

WP2000 EO Requirements for ODA

Activities performed

  • WP2100: EO Data and Service Characteristics (EOX)
  • Analyze data formats and data access services
    • Prepare Requirement Baseline Document (RB)
  • WP 2200: EO Metadata Requirements (Spot)
    • Draft document
  • WP2300: GSC-DA, DAIL, HMA-E Interface Requirements (EOX)
    • Analyze requirements for Online Data Access of GSC-DA, DAIL, HMA-E
    • Prepare Requirement Baseline Document (RB)
  • WP2400: SSE Client Requirements (GIM)
    • Compilation of Client requirements and insertion into RB document
    • Review of RB Document
  • WP2500: GEOSS & INSPIRE Standards (EOX)
    • Analyze requirements for Online Data Access by GEOSs & INSPIRE
    • Prepare Requirement Baseline Document (RB)
  • WP 2600: Service Industry Needs (Spot)
    • Draft document
  • WP2700: Advanced Concepts (WCPS, P2P,Tiling,...) (JUB)
    • .

Outcome and results

  • Requirement Baseline Document (RB)
  • EO Metadata Requirements Document (EOMR-RB)
  • EO INdustry Needs Document (EOIN-RB)
  • Technical Specification Document (TS)
  • Specification Dependencies (TN)
  • Design Justification File (DJF)
  • Design Definition File (DDF)

Problems and concerns

  • All relevant Initiatives, Programs, and Projects hardly define requirements for the EO Online Data Accessts.
  • Knowledge about ODA possibilities other then FTP seems not to exist.
  • It is assumed that knowledge about OGC Services (especially WCS) possibilities is not very thorough

Plans for next period

  • Add Use Cases and Sequence diagramms to RB
  • Consolidate RB Documents
  • Use RB as Input for ODA system design
  • Continue Specification Dependencies (TN)

WP3000 Towards OpenGIS Standardization

Activities performed

  • WP3100: WCS 2.0 SWG Liaison (JUB)
    • .
  • WP3200: WCS 2.0 SWG Liaison (Spot)
    • participate in WCS.SWG telelcons
  • WP3300: WCS 2.0 SWG Liaison (EOX)
    • Follow up on evolution and participate in WCS.SWG telelcons
  • WP3400: WCS 2.0 SWG Liaison (GIM)
    • Follow up on evolutions
  • WP3500: OGC Interoperability Program (JUB)
    • .
  • WP3600: EO Application Profile Development (JUB)
    • .
  • WP3700: Contribution to EO Application Profile & Conformance Testing (EOX)
    • None
  • WP3800: OGC Conformance Test Approach & Tools (JUB)
    • .
  • WP3900: OGC Conformance Testing & Reporting (JUB)
    • .

Outcome and results

  • WCS 2.0 draft submitted for RFC Process
  • GML 3.2.1 Application Schema for WCS (including XML Schema) (OGC 09-146)
  • WCS 2.0 Core (including XML Schema) (OGC 09-110)
  • WCS 2.0 Extension: KVP protocol (OGC 09-147)
  • WCS 2.0 Extension: XML/POST protocol (OGC 09-148)
  • WCS 2.0 Extension: SOAP protocol (OGC 09-149)
  • WCS 2.0 Overview: Core and Extensions (Best Practice) (OGC 09-153)
  • …plus 20 XML schema & example files
  • Additionally, separate: draft template for coverage format extensions (Best Practice)
  • WCS.SWG votes to move WVS 2.0 to the RFC process

Problems and concerns

  • None

Plans for next period

  • Preparations for OGC TC Meeting in Frascati
  • Continue with OGC standartization process (review, voting, etc.)
  • Start requirements systhesis for the EO WCS
  • Summarize needs for extensions for EO WCS
 * Harmonisation of Data Models - EO GML <> (EO) WCS GML

WP4000 Software Implementation

Activities performed

  • WP4100: WCS Server extension implementation (EOX)
    • None
  • WP4200: SSE Client Extension Implementation (GIM)
    • None
  • WP4300: Acceptance Test Planning (EOX)
    • None
  • WP4400: Transfer, Acceptance Testing & Reporting (ECSS) (EOX)
    • None
  • WP4500: WCS Server Warranty (EOX)
    • None
  • WP4600: SSE Client Warranty (GIM)
    • None
  • WP4700: Advanced Concepts - Implementations (JUB)
    • None

Outcome and results

  • None

Problems and concerns

  • None

Plans for next period

  • Start WCS Server implementation in paralell to WCS standardization process
  • Decision on OS Software to use
  • EO WCS development
  • Start SSE Client extension implementation in paralell to WCS standardization process
  • Acceptance Test Planning

WP5000 Software Open Use & Community Support

Activities performed

  • None

Outcome and results

  • None

Problems and concerns

  • None

Plans for next period

  • None


Contributors to this page: Christian Schiller

WebMapViewerSupport .

Page last modified on Thursday 22 of April 2010 17:19:00 CEST by Christian Schiller.

Category: HMA