View source for Geospatial Draft Work Plan Q2-3 2012

== Abstract or Executive Summary ==


One of the 4 currently identified clusters in iMarine is 'geospatial'. The term is sufficiently vague to enable the collection of requirements that operate on, or benefit from, 'geospatial' services. The boundary of this domain is far from sharp, and immediate relations with e.g. the biodiversity and statistical clusters are evident.

The work-plan is not domain specific, and technology neutral. It decribes how the iMarine Board can be involved in the specification of use-cases, data policies, and harmonization issues, to name a few issues.

== Introduction and Background (The Problems) ==

The iMarine Board is responsible for the implementation of 2 Business Cases in the project, and brings a wealth of community expertise to the technical e-infrastructure. The EA-CoP has needs to manage geospatial explicit data in several scenarios, such as SPREAD; for intersection generation and species re-allocation, Species Occurence data management, Vessel Transmitted Information, and Species Occurence enrichment. 

The geospatial opportunities were presented and discussed at the iMarine Board meeting in Rome (March 19-21), and later further elaborated and discussed by project partners with EA-CoP input.

== Goals and Objectives (The Outputs) ==

The cluster discussion at the iMarine board meeting was summarized by Terradue (Fabrice Brito). Multiple goals were identified as products that can be delivered. For each of these, an initial set of objectives emerged that require further discussion. The medium term goals are : .

[https://gcube.wiki.gcube-system.org/gcube/index.php/Geospatial_Data_Processing Geospatial data processing]

== Resources and Constraints (The Inputs) ==

The iMarine project was designed with a clear vision on the need for geospatial technologies that support challenging scenarios. It also anticipated that specialized resources would have to be identified after the project started, e.g. in establishing collaborations with initiatives of project partners' (FAO intersection engine and Figis system, OBIS), and related EA-CoP projects such as with AgInfra.

A complete assessment of needs and constraints can only be made once such collaborations have established.

The resources from the project would include:

Terradue - Use case description, data provider and developer

FAO - Use case description, data provider

CNR - Tools and application provider, developer

OBIS - Use case description, data 

FIN - .....

Specific constraints are the few componenets for advanced geospatial data management and expertise in the EA-CoP. Although many partners have developed geospatial support infrastructures and tools, the use ses that are to be supported in this project require 'new science' and the involvement of scientist that understand the new horizons offered through a large e-Infrastructure. In addition, many datasets are volatile or incomplete, and will require specialized curation features.


== Strategy and Actions (from Inputs to Outputs) ==


This schedule will have to be further elaborated, and discussed with the iMarine Board in May. Their response can then be used at the TCom in Greece in June.

The goals and objectives have been defined and discussed at the iMarine Board meeting in Rome in March. Here, it was also decided that a biodiversity cluster be established to define objectives, and prepare outlines for VRE's, applications and services. These will then be presented to the iMarine Board and the wider EA-CoP (May 2012).

In June, the results from the EA-CoP consultation will be discussed at the TCom, to establish feasibility, usability, and usefulness of the identified Use Cases and components.

The feed-back from the TCom and technical boards will then be discussed with the iMarine Board and selected EA-CoP representatives for follow-up ations.

Meanwhile, project partners already can spend effort on the first 4 Use Cases to support; the Taxon service, the data access to biodiversity data repositories, and discovery and dowload of species occurence data; taxon name discovery, taxon name reconciliation, occurrence data access, and occurrence data reconciliation.


== Appendices (Planned Effort, Resources, Meeting Notes, Schedule and Others) ==


=== Planned effort & resources ===


Terradue

FAO

CNR

OBIS


=== Meeting notes ===



=== Schedule ===