Project Manager Assessment

• The status of the project is nominal.

Key Problem List

• None

Deliverables Table

• None

WP1000 Project Management

Activities performed

• WP1100: Overall Project Coordination (EOX)
• WP1200: Contractor Management (EOX)
• WP1300: Subcontractor Management (GIM)
• WP1400: Subcontractor Management (JUB)
  • .
• WP1500: Subcontractor Management (Spot)
  • .
• WP1600: Project Reporting (EOX)
  • Management Progress report 12/2009 Wiki
  • Consolidation of prepared Documents

Outcome and results

• None

Problems and concerns

• None

Plans for next period

• Release of Requirements Baseline Document

WP2000 EO Requirements for ODA

Activities performed

• WP2100: EO Data and Service Characteristics (EOX)
  • Collect, review and analyze requirements for Online Data Access of GMES relevant Initiatives, Programs, and Projects
  • Prepare Baseline Document
• WP 2200: EO Metadata Requirements (Spot)
  • Draft will be uploaded to the wiki before the PR for comments.
• WP2300: GSC-DA, DAIL, HMA-E Interface Requirements (EOX)
  • Collect, review and analyze requirements for Online Data Access of GMES relevant Initiatives, Programs, and Projects
  • Prepare Baseline Document
• WP2400: SSE Client Requirements (GIM)
  • Establishing SSE WebMapViewer requirements in function of WCS 2.0 draft;
  • Work on consolidation of HMA Specification dependencies document: clarifying links between discovery (CIM EP, EO EP), View (EO WMS) and Online data Access (EO WCS);
  • Formulation of a set of requirements for the EO WCS to ensure consistency with the existing HMA Specification baseline.
• WP2500: GEOSS & INSPIRE Standards (EOX)
  • Collect, review and analyze requirements for Online Data Access of GMES relevant Initiatives, Programs, and Projects
  • Prepare Baseline Document
• WP 2600: Service Industry Needs (Spot)
  • Draft will be uploaded to the wiki before the PR for comments.
• WP2700: Advanced Concepts (WCPS, P2P,Tilinng,...) (JUB)
  • .

Outcome and results

• Prepare Baseline Document

Problems and concerns

• GMES relevant Initiatives, Programs, and Projects mostly don't provide requirements for Online Data Access to EO data. We have concluded that the ODA issue is very much in the forefront and most providers and users have no idea what might be possible with nowadays technologies. It has been agreed within the team that for Requirement Baseline Document the ODA use cases and ODA requirements are to be defined based on the our own experience and involvement in various initiatives. Discussion with providers and users can be then be performed based on the document.

Plans for next period

• Release of the Requirement Baseline Document v1.0

WP3000 Towards OpenGIS Standardization

Activities performed

• WP3100: WCS 2.0 SWG Liaison (JUB)
  • Regular active participation in weekly OGC WCS telecons, including several times facilitation of telecon;
  • Input to mailing list discussions aiming at clarification of concepts and advancing consensus;
  • finalized WCS 2.0 draft for vote by WCS.SWG (6 documents, 20 XML files with schemas and examples)
• WP3200: WCS 2.0 SWG Liaison (Spot)
  • Participation in the WG during December TC and to the mailing list discussions of WCS.SWG
• WP3300: WCS 2.0 SWG Liaison (EOX)
  • Participation in the mailing list discussions of WCS.SWG
  • Regular participation in weekly OGC WCS telecons
  • Review of WCS 2.0 draft documents
• WP3400: WCS 2.0 SWG Liaison (GIM)
  • Follow-up on mailing list discussion
  • Review of WCS 2.0 Core
• WP3500: OGC Interoperability Program (JUB)
• unfortunately, WCS was not considered in OWS-7, despite manifold talks
• WP3600: EO Application Profile Development (JUB)
  • None
• WP3700: Contribution to EO Application Profile & Conformance Testing (EOX)
  • None
• WP3800: OGC Conformance Test Approach & Tools (JUB)
  • None
• WP3900: OGC Conformance Testing & Reporting (JUB)
  • None

Outcome and results

• WCS 2.0 draft completed, available on WCS.SWG wiki

Problems and concerns

• not more than before

Plans for next period

• have WCS 2.0 draft accepted by WCS.SWG, publish for RFC
• continue proof-of-concept implementation, to further convince WCS.SWG and externals about feasibility of the approach

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)
  • .

Outcome and results

• None

Problems and concerns

• None

Plans for next period

• None

WP5000 Software Open Use & Community Support

Activities performed

• None

Outcome and results

• None

Problems and concerns

• None

Plans for next period

• None