Task #2001

Project WP #654: WP6 - Supporting Blue Economy: VREs Development [Months: 1-30]

Project Task #656: T6.2 Strategic Investment analysis and Scientific Planning/Alerting VRE [Months: 1-30]

Project Activity #1633: Blue Economy VRE#2 Software Implementation, Integration and Deployment (Stage 2)

Task #6101: Geospatial Analytics & Alerting Platform Implementation (Stage 2)

Implement Geospatial Analytics Model Configuration & Management Logic

Added by Gerasimos Farantatos over 3 years ago. Updated over 1 year ago.

Status:ClosedStart date:Nov 01, 2016
Priority:NormalDue date:May 31, 2017
Assignee:Nikolas Laskaris% Done:


Duration: 152


A model, in the context of the platform is defined as
* A set of virtual layers which will serve as inputs to the geospatial analytics algorithm
* The mapping from input virtual layers to algorithm parameters
* Description of input and output units
* A set of mappings/conversions between logical layers, which will be used during the computation for the on demand homogenization of logical layers which are incompatible with one another.
* The fitness function which will be used to obtain results

An algorithm is described in an abstract way in terms of the computational runtime upon which it will be executed (Apache Spark, local Java implementation etc). This abstract definition also contains algorithm-specific configuration such as the way an algorithm run is initialized (e.g. starting points for a simulated annealing algorithm or different system parameters for each run).

A sub-component of the platform needs to be developed, whose main tasks will be to interface with the geospatial model/algorithm store within the infrastructure and provide an API for the management of models and algorithms.


#1 Updated by Gianpaolo Coro about 3 years ago

Dear Gerasimos, this case will be followed by the colleagues of Engineering, another BlueBRIDGE partner that has effort in your WorkPackage. Please, refer to them for your issues, but continue using SAI in the way you currently do. CNR will act as a backup.

#2 Updated by George Kakaletris about 3 years ago

  • Start date changed from Jan 18, 2016 to Nov 01, 2016
  • Assignee changed from Gerasimos Farantatos to Nikolas Laskaris
  • Due date set to May 31, 2017

#3 Updated by Dimitris Katris over 2 years ago

  • Parent task changed from #1991 to #6101

#4 Updated by Dimitris Katris over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed
  • Infrastructure Development added

Also available in: Atom PDF