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

HMA-FO Progress Task 3 1004

Project Manager Assessment

  • The status of the project is nominal.

Key Problem List

  • None

Deliverables Table

  • None

WP1000 Project Management

Activities performed

  • Coordination with subcontractors
  • Progress report
  • Preparation Progress Telecon

Outcome and results

  • Progress Report
  • Progress Telecon (minutes, actions, slides, etc)
  • Technical telecon regarding EO WCS

Problems and concerns

  • None

Plans for next period

  • General Project Management work
  • Technical telecon regarding EO WCS
  • Technical Meeting JUB-EOX (Vienna, 7.May)
  • Start preparation for WCS workshop 9.June at DLR
    • Propose Workshop-Agenda
    • Propose Presentation Plan for participating Agencies
      • what are the plans
      • what are existing implementations capabilities
      • ...

WP2000 EO Requirements for ODA

Activities performed

  • WP2100: EO Data and Service Characteristics (EOX)
    • Harmonization and consolidation of RB-SSS, RB-TN, TS-SSS
  • WP 2200: EO Metadata Requirements (Spot)
    • .
  • WP2300: GSC-DA, DAIL, HMA-E Interface Requirements (EOX)
    • Harmonization and consolidation of RB-SSS, RB-TN, TS-SSS
  • WP2400: SSE Client Requirements (GIM)
    • .
  • WP2500: GEOSS & INSPIRE Standards (EOX)
    • Harmonization and consolidation of RB-SSS, RB-TN, TS-SSS.
  • WP 2600: Service Industry Needs (Spot)
    • .
  • WP2700: Advanced Concepts (WCPS, P2P, Tilinng,...) (JUB)
    • .

Outcome and results

  • RB-SSS v1.2
  • RB-TN v1.0
  • TS-SRS v1.1
  • hmafo-tn-0001-spb-v12-draft

Problems and concerns

  • ECSS-ST-E-40C experienced as overcomplicated; ECSS-E-ST-10-06C seems more appropriate for such rather small project
  • Due to the combination of requirements collected for a standard (WCS), an interface (EO WCS), a demonstrator software (a WCS server implementation) and operational requirements (by Agencies), the assignment of requirements for SSS and SRS has been difficult.

Plans for next period

  • Evaluation of RIDS received from Agencies and integration into documents
  • Propose updated list of deliverables

WP3000 Towards OpenGIS Standardization

Activities performed

  • WP3100: WCS 2.0 SWG Liaison (JUB)
    • final handling of incoming TC-vote comments (resolution, discussion, documentation)
    • facilitation of weekly telecon (effectively acting as SWG chair, as Steven Keens has started to be permanently absent);
    • Input to mailing list discussions aiming at clarification of concepts and advancing consensus;
    • advancing concepts, in particular with view on EO AP
    • Harmonization of WCS and SWE metadata
  • WP3200: WCS 2.0 SWG Liaison (Spot)
    • .
  • WP3300: WCS 2.0 SWG Liaison (EOX)
    • Participation in WCS telecons
    • Drafting GeoTIFF WCS 2.0 extension started
    • received confirmation of 2 volonteers for extension writing (JPEG2000 and netCDF)
  • WP3400: WCS 2.0 SWG Liaison (GIM)
    • .
  • WP3500: OGC Interoperability Program (JUB)
    • .
  • WP3600: EO Application Profile Development (JUB)
    • .
  • WP3700: Contribution to EO Application Profile & Conformance Testing (EOX)
    • Discussions in consortium on WCS EO Profile directions
    • Telecon - RB implications for the EO WCS and possible solutions
  • WP3800: OGC Conformance Test Approach & Tools (JUB)
    • .
  • WP3900: OGC Conformance Testing & Reporting (JUB)
    • .

Outcome and results

  • Harmonization of WCS and SWE metadata has been achieved fast
  • WCS 2.0 bundle submitted for OGC TC-voting (voting period 2010/04/20 - 2010/06/19)

Problems and concerns

  • Timeline of OGC standartization process again shifted
  • after timely submission of WCS package for voting, roll-out has been delayed (again) by Carl Reed; now vote will end a few days after TC meeting

Plans for next period

  • respond to further discussions, if necessary adapt draft
  • continue with EO WCS development and with the writing of extensions

WP4000 Software Implementation

Activities performed

  • WP4100: WCS Server extension implementation (EOX)
    • Analyses of MapServer Sources
    • Mapserver extension architecture and design analysis started
  • WP4200: SSE Client Extension Implementation (GIM)
    • .
  • WP4300: Acceptance Test Planning (EOX)
    • None
  • WP4400: Transfer, Acceptance Testing & Reporting (ECSS) (EOX)
    • .
  • WP4500: WCS Server Warranty (EOX)
    • None
  • WP4600: SSE Client Warranty (GIM)
    • .
  • WP4700: Advanced Concepts - Implementations (JUB)
    • .

Outcome and results

  • None

Problems and concerns

  • If EO WCS and WCS 2.0 extensions are not written then implementation of Demonstrator can't be performed on time.

Plans for next period

  • Propose possible solution e.g. via inofficial "minimalistic, but functional" extensions e.g. minimalistic set of CRS
  • Propose schedule for such solution

WP5000 Software Open Use & Community Support

Activities performed

  • Contacts initiated

Outcome and results

  • None

Problems and concerns

  • None

Plans for next period

  • intensify contacts
  • start informing MapServer community



Contributors to this page: Christian Schiller .

Page last modified on Wednesday 28 of April 2010 12:23:41 CEST by Christian Schiller.

Category: HMA