WP6 M04 Monthly Progress Report (Dec 2015)

Links: WP Issue: [#654]. Previous month: WP6-M03-MonthlyProgressReport. Next month: WP6-M05-MonthlyProgressReport

Note: Use bullets in sections

WP Summary

  • WP Management & Coordination (UoA)
  • Internal meeting (UoA, I2S, CITE)
  • Knowledge transfer from UoA to I2S and to a lesser extent to CITE about
    • gCube infrastructure & services
    • Portal & portlets development, specifically for the BlueBRIDGE portal environment
  • Discussion on a potential course as part of a training plan based on the outcomes of this WP. The plan will be further refined and the target audience will be identified as soon as a first version of the tools is available in the infrastructure. (UoA)
  • Contribution to Data Management Plan (UoA, I2S)
  • Contribution in the generalization of requirements, so that they can be covered or can strengthen existing common services. (UoA)
  • Completed Functional Specifications of Blue Economy VRE#1 (I2S)
  • Completed Database Design of Blue Economy VRE#1 (I2S)
  • Initial UI Design of prototype application for Blue Economy VRE#1 (I2S)
  • Development a small prototype application showing the main functionality of the service of Blue Economy VRE#1 (I2S)
  • Launched research on suitable algorithms, which are implemented in R, for the evaluation of the KPIs performance. Research on connectivity issues about R and Java (I2S)
  • WFS vs WMS pre-evaluation. An initial analysis has led to the conclusion that this issue is relatively complex, thereby warranting the creation of a separate task. A careful balancing in the usage of the two standards is to be considered. (UoA)
  • Further analysis on technological challenges in the design of the Geospatial Analytics & Alerting platform. Focus on
    • Investigating the usage of Apache Spark for the execution of geospatial algorithms conforming to different processing models (UoA)
    • Execution of standalone algorithms vs machine learning algorithms that require training (UoA)
    • Designed the structure of layers in the context of the Geospatial Analytics & Alerting Platform. Physical, logical and virtual layers and their configuration of them have been defined. (CITE)
  • Began task of downgrading the user interface of Geopolis to Bootstrap v2.0 from v3.0, in order to be integrated as a Liferay v6.2 portlet. (CITE)
  • Launch of moving the front end logic of Geopolis to a Liferay portlet. (CITE)
  • Launch of redesign of Geopolis platform, in order for it to become the management part of the Geospatial Analytics & Alerting platform. (CITE, UoA)
  • Revisiting the data access model of Geopolis, in order for it to evolve from direct geospatial database access into a more generic one. (CITE)

T6.1 Performance evaluation, benchmarking and decision making in aquaculture VRE

Note: To be completed by Task Leader

Progress of Work

UOA

  • Knowledge tranfer from UoA to I2S and to a lesser extent to CITE about
    • gCube infrastructure & services
    • Portal & portlets development, specifically for the BlueBRIDGE portal environment
  • Discussion on a potential course as part of a training plan based on the outcomes of this WP. The plan will be further refined and the target audience will be identified as soon as a first version of the tools is available in the infrastructure.
  • Contribution to Data Management Plan.

I2S

  • Complete Functional Specifications (Project Activity #1889).
  • Complete Database Design (Project Activity #1889).
  • Complete prototype UI Design (Project Activity #1891).
  • Contribute to Data Management Plan by writing: > the specification of datasets which are suitable to forecast each KPI (Project Activity #1885) > the specification of the data sets that are produced as outcome of the analysis (Project Activity #1886) > the description of the datasets comes from outsource databases.
  • Development a small prototype application showing the main functionality of the service (Project Activity #1892).
  • Discussion and meeting with CITE and UOA about technical and dissemination issues.
  • Research on suitable algorithms, which are implemented in R, for the evaluation of the KPIs performance. Research on connectivity issues about R and Java (in progress).

Deviations from plans and corrective actions

Note: if any. Use bullets. Any references to partners should be in a parenthesis at the end of the bullet

UOA

None

I2S

None

Plans for next month

Note: add any short term plans for the activity

UOA

I2S

Continue with the software development, focusing on the elaboration of the prototype application and integrating it with models for analysis and performance evaluation.

Risks

Note: identify any new, rising or diminishing risks

T6.2 Strategic Investment analysis and Scientific Planning/Alerting VRE

Note: To be completed by Task Leader

Progress of work

UOA

  • WFS vs WMS pre-evaluation. An initial analysis has led to the conclusion that this issue is relatively complex, thereby warranting the creation of a separate task. A careful balancing in the usage of the two standards is to be considered.
  • Further analysis on technological challenges in the design of the Geospatial Analytics & Alerting platform. Focus on
    • Investigating the usage of Apache Spark for the execution of geospatial algorithms conforming to different processing models
    • Execution of standalone algorithms vs machine learning algorithms that require training
  • Contribution to the redesign of Geopolis in the context of the GAAP.
  • Contribution in the generalization of requirements, so that they can be covered or can strengthen existing common services.

CITE

  • Began task of downgrading the user interface of Geopolis to Bootstrap v2.0 from v3.0, in order to be integrated as a Liferay v6.2 portlet.
  • Launch of moving the front end logic of Geopolis to a Liferay portlet.
  • Launch of redesign of Geopolis platform, in order for it to become the management part of the Geospatial Analytics & Alerting platform.
  • Revisiting the data access model of Geopolis, in order for it to evolve from direct geospatial database access into a more generic one.
  • Designed the structure of layers in the context of the Geospatial Analytics & Alerting Platform. Physical, logical and virtual layers and their configuration of them have been defined.

I2S

FAO

Deviations from plans and corrective actions

Note: if any. Use bullets. Any references to partners should be in a parenthesis at the end of the bullet

UOA

CITE

I2S

FAO

Plans for next month

Note: add any short term plans for the activity

UOA

CITE

I2S

FAO

Risks

Note: identify any new, rising or diminishing risks

Meetings

18 Dec 2015 Face to Face Meeting @ CITE