Difference between revisions of "Ecosystem Approach Community of Practice: SPREAD"

From D4Science Wiki
Jump to: navigation, search
m (→‎Productivity)
 
(16 intermediate revisions by 3 users not shown)
Line 14: Line 14:
  
 
=== Problem ===  
 
=== Problem ===  
−
''Describe the CoP issue to be addressed by the Component (VRE / service / resource / etc)''
 
  
 
The problem of re-allocation is fully described in the SPREAD report.  
 
The problem of re-allocation is fully described in the SPREAD report.  
  
−
The UNGA asked for a distinction between capture from the High Seas and those taken from EEZ's. Since the reporting for FAO does not include that distinction, a means has to be identified to disaggregate time-series.  
+
The UNGA asked for a distinction between capture from the High Seas and those taken from EEZ's. Since the reporting for FAO does not include that distinction, a means has to be identified to disaggregate time-series.
 +
 
 +
=== Progress ===
 +
 
 +
The implementation progress has been tracked through the high level ticket in TRAC [[https://issue.i-marine.research-infrastructures.eu/ticket/832]]
  
 
=== Product ===
 
=== Product ===
−
''Describe the proposed solution in maximum 3 sentences:''
 
  
−
With SPREAD capture time-series from ICIS can be re-allocated to another area using geospatial information on species distribution and capture areas. If the intersection between reporting area and target area is not known, SPREAD offers a facility to generate the intersection using a accurate projection. The generated products are reviewed before they are shared with other users and VRE for e.g. inclusion in species distribution analysis, which can be either and expert-review, or a machine driven review.  
+
With SPREAD capture time-series from ICIS can be re-allocated to another area using geospatial information on:
 +
* species distribution, and  
 +
* capture areas, and
 +
* EEZ.  
 +
 
 +
If the intersection between reporting area and target area is not known, SPREAD relies on a facility to generate the intersection using a accurate projection. This intersection engine is located in and developed by FAO. The resulting layers have to be made discoverable and accessible to D4Science services through GeoNetwork.
 +
 
 +
The generated products are reviewed before they are shared with other users and VRE for e.g. inclusion in species distribution analysis, which can be either and expert-review, or a machine driven review.
 +
 
 +
No public tools are foreseen, all data and products remain the property of the SPREAD user.
  
 
=== Priority to CoP ===  
 
=== Priority to CoP ===  
−
''List proposed solution priority following the iMarine Board priority setting criteria: ''
+
''List proposed solution priority : ''
  
 
* ''Identified community: Users now:'' The need was identified by the UNGA, and the users are in FAO-FI. In general, disaggregation is in high demand in understanding Time-Series in the agriculture and fisheries domains.  
 
* ''Identified community: Users now:'' The need was identified by the UNGA, and the users are in FAO-FI. In general, disaggregation is in high demand in understanding Time-Series in the agriculture and fisheries domains.  
  
 
* ''Potential for co-funding:'' reasonable, if a community can be identified that requires a. dynamic intersection generation, b. statistical data disaggregation.  
 
* ''Potential for co-funding:'' reasonable, if a community can be identified that requires a. dynamic intersection generation, b. statistical data disaggregation.  
−
 
−
* ''Structural allocation of resources:'' To be discussed in a. SB, b. iMarine Board
 
−
 
−
* ''Referred in DoW:'' Not explicitly.
 
−
 
−
* ''Business Cases:'' Supports BC 1.
 
  
 
* ''How does the proposed action generally support sustainability aspects'' If based on OGC standards, SPREAD will be key to bringing the power of the infrastructure to a geospatial explicit data community as a product that is easy to understand (for OGC community members), brings additional resources that do not exist in geo-statistical workflows (integrated R, TS management), and offer VRE secure collaboration.  
 
* ''How does the proposed action generally support sustainability aspects'' If based on OGC standards, SPREAD will be key to bringing the power of the infrastructure to a geospatial explicit data community as a product that is easy to understand (for OGC community members), brings additional resources that do not exist in geo-statistical workflows (integrated R, TS management), and offer VRE secure collaboration.  
Line 42: Line 47:
 
* ''How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):'' For SB
 
* ''How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):'' For SB
  
−
* ''Re-usability – benefits – compatibility'' High.  
+
* ''Re-usability'' of SPREAD works in two directions; it re-uses components of the D4Science infrastructure such as ICIS, and from the FAO infrastructure such as  benefits – Since SPREAD relies on the further development of existing resources, the ''compatibility'' of the the resulting services and products is high.
  
 
=== Parentage ===
 
=== Parentage ===
−
;''Relation to CoP Software''  
+
;''Relation to EA-CoP Software''  
−
:For Emmanuel
+
:SPREAD relies for its geospatial products, such as intersections, on the FAO SDI, namely the intersection engine and the Geonetwork. In addition, the EEZ's are managed through FAO, but were provided by VLIZ.
  
 
;''Relation to D4S technologies''  
 
;''Relation to D4S technologies''  
−
:<font color="red">For WP6</font>
+
: The data for SPREAD will rely on ICIS for some of data to be re-allocated. The Timeseries contain the capture records, and information on some of the environmental preferences for the species.
 +
: The SPREAD algorithm is foreseen as a WPS process.
 +
: The results of SPREAD will rely on the GeoExplorer to vizualize the results of the re-allocations. ICIS is foreseen as the store of re-allocated TS-Objects. For
  
 
;''Does the proposed solution solve other problems associated with EA-CoP Business Cases?''  
 
;''Does the proposed solution solve other problems associated with EA-CoP Business Cases?''  
−
:For iMarine Board evaluation
+
: SPREAD has interesting features that can be made available to other use cases. For the development of SPREAD, a lot of ground was broken to establish a SDI, and the integration with WPS and the D4Science infrastructure was pioneered in SPREAD. This has equipped the infrastructure for advanced processing of Geospatial data.
−
 
+
−
;''If the proposed solution can be used in another SW scenario (not users!) please describe.''
+
−
:<font color="red">For WP6</font>
+
  
 
=== Public ===
 
=== Public ===
 
;''How big is the expected user community after delivery?''  
 
;''How big is the expected user community after delivery?''  
−
:<font color="red">'''4 persons will use SPREAD.'''</font>
+
:SPREAD has different user categories: Developers, Users, and Consumers.
 +
: * The developers arrange the content, ensure they align to D4Science metadata formats, and are of good enough quality. They also ensure that the algorithm has sufficient resources, and performs well.
 +
: * The users perform re-allocation by selecting the dataset to be re-allocated, the target to re-allocate to, the algortihm to apply, and publish the results.
 +
: * The consumers are D4science VRE users (remember, this is not a public dataset producer), or trusted collaborators having been granted access to the geospatial products directly. They are trusted with the task to analyse the results, and re-use the products outside the e-infrastructure.
  
 
=== Productivity ===  
 
=== Productivity ===  
 
;''Are the proposed measures effective?''  
 
;''Are the proposed measures effective?''  
−
:<font color="red">There are already alternatives to assess the amount of distant fishing which can serve a proxy for high-seas fisheries.</font>
+
:SPREAD is a new developemnt, and it's productivity can not be measured against a benchmark.  
 
   
 
   
 
;''Does it reduce a known workload?''  
 
;''Does it reduce a known workload?''  
−
:<font color="red">'''No.'''</font>
+
:Since SPREAD is a new and groundbreaking application, it can not be stated tht it reduces a work-load.
  
 
=== Price ===
 
=== Price ===
−
''Is the proposed solution cheap?'' No, it should only be pursued if the components can be re-used in other scenarios. That is for the iMarine Board to decide.  
+
;''Is the proposed solution cheap?''  
 +
:No, it should only be pursued if the components can be re-used in other scenarios.  
  
−
''Expected effort in PM:'' <font color="red">12</font>
+
;''Expected effort in PM:''  
 +
:<font color="red">12</font>
  
 
=== Presentation ===  
 
=== Presentation ===  
−
''How is the component delivered to users? (Design / on-line help / training material / support).''
+
;''How is the component delivered to users? (Design / on-line help / training material / support).''
  
−
SPREAD is conceived to be delivered through a <font color="red">VRE that starts from the ICIS</font> (the data to re-allocate). This should provide GIS features to GIS-enable the time-series.  
+
:SPREAD is conceived to be delivered through a <font color="red">VRE that starts from the ICIS</font> (timeseries data to re-allocate). This should provide GIS features to GIS-enable the time-series.  
  
−
<font color="red">It also requires an user interface to select a target area to re-allocate to, </font>
+
:It also requires an user interface to select a target area & probability-based data sources used to re-allocate,
  
−
For the algorithm, machine access to the intersection layer is required.  
+
:For the algorithm, machine access to the intersection layer is required.  
  
−
The output are <font color="red">maps in xyz format</font> that can either be stored in a geospatial database, or in the D4S WS.  
+
:The output are timeseries with a new geospatial dimension (target area).  
  
−
These maps will have to be accessible by other VREs if the owner so decides.
+
:Reallocated data maps (as well as initial data maps) have to be managed by generic TimeSeries thematic mapping functionalities.
 +
 
 +
:These maps will have to be accessible by other VREs if the owner so decides.
  
 
=== Privacy ===
 
=== Privacy ===
 
;''Are they safe?''  
 
;''Are they safe?''  
−
:There are no privacy issues of legal or physical persons involved.  
+
:There are no privacy issues of legal or physical persons involved. However, the risk of misinforming the general audience with SPREAD products requires that a proper work-flow is ensured before data can be published.  
  
 
;''Need the proposed solution to manage confidential info at data / dataset / organizational level?''  
 
;''Need the proposed solution to manage confidential info at data / dataset / organizational level?''  
Line 95: Line 106:
  
 
;''Describe security and privacy issues:''
 
;''Describe security and privacy issues:''
−
:<font color="red>Not possible, here WP6 can contribute.</font>
+
:The SPREAD Policy for data access and sharing is described [[Use_Cases_for_EA-CoP_Data_Access_and_Sharing_Policies#SPREAD | here]]
  
 
=== Policy ===  
 
=== Policy ===  
−
;''Are there any policies available that describe data access and sharing?''
+
:The SPREAD Policy for data access and sharing is described [[Use_Cases_for_EA-CoP_Data_Access_and_Sharing_Policies#SPREAD | here]]
−
:No, a beginning has been made in T3.2 by FAO.
+
−
+
−
;''Are these really needed?''
+
−
:Yes, the data used are often confidential, and the products convey a strong message. The output should always be validated and cleared by the data owner.
+
−
 
+
−
;''Copyright / attribution / metadata / legal''
+
−
:The SPREAD use case is interesting to see how policies can be developed that range from statistical data in the public domain, but attributable to FAO, with geospatial maps generated by VLIZ, with a legal information on fisheries agreements. The produced products, be they maps, images, geospatial formats or reports, will all need to propagate the ownerships, address copyright issues and contain a clear disclaimer.
+
  
 
=== Perils ===  
 
=== Perils ===  

Latest revision as of 11:29, 3 September 2015

SPREAD Profile

The SPatial REallocation of Aquatic Data (SPREAD) aims to provide the conversion of geospatial explicit data from one resolution to another.

The Use Cases were already descibed in D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, and can be found under the Advanced Curation Use Case.

It was included under ICIS Advanced Curation because in the context of D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, the starting point for a re-allocation is a TS-Object, and the re-allocation was perceived as a precision of geospatial location of a reported capture without much reasoning or change of the reported values.

A progress report on SPREAD accomplishments and opportunities can be found on BSCW (SPREAD120207.docx).

Problem

The problem of re-allocation is fully described in the SPREAD report.

The UNGA asked for a distinction between capture from the High Seas and those taken from EEZ's. Since the reporting for FAO does not include that distinction, a means has to be identified to disaggregate time-series.

Progress

The implementation progress has been tracked through the high level ticket in TRAC [[1]]

Product

With SPREAD capture time-series from ICIS can be re-allocated to another area using geospatial information on:

  • species distribution, and
  • capture areas, and
  • EEZ.

If the intersection between reporting area and target area is not known, SPREAD relies on a facility to generate the intersection using a accurate projection. This intersection engine is located in and developed by FAO. The resulting layers have to be made discoverable and accessible to D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. services through GeoNetwork.

The generated products are reviewed before they are shared with other users and VREVirtual Research Environment. for e.g. inclusion in species distribution analysis, which can be either and expert-review, or a machine driven review.

No public tools are foreseen, all data and products remain the property of the SPREAD user.

Priority to CoPCommunity of Practice.

List proposed solution priority :

  • Identified community: Users now: The need was identified by the UNGA, and the users are in FAO-FI. In general, disaggregation is in high demand in understanding Time-Series in the agriculture and fisheries domains.
  • Potential for co-funding: reasonable, if a community can be identified that requires a. dynamic intersection generation, b. statistical data disaggregation.
  • How does the proposed action generally support sustainability aspects If based on OGC standards, SPREAD will be key to bringing the power of the infrastructure to a geospatial explicit data community as a product that is easy to understand (for OGC community members), brings additional resources that do not exist in geo-statistical workflows (integrated R, TS management), and offer VREVirtual Research Environment. secure collaboration.
  • How consistent it is with EC regulations/strategies (eg INSPIRE, ... ): For SB
  • Re-usability of SPREAD works in two directions; it re-uses components of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. infrastructure such as ICIS, and from the FAO infrastructure such as benefits – Since SPREAD relies on the further development of existing resources, the compatibility of the the resulting services and products is high.

Parentage

Relation to EA-CoPCommunity of Practice. Software
SPREAD relies for its geospatial products, such as intersections, on the FAO SDI, namely the intersection engine and the Geonetwork. In addition, the EEZ's are managed through FAO, but were provided by VLIZ.
Relation to D4S technologies
The data for SPREAD will rely on ICIS for some of data to be re-allocated. The Timeseries contain the capture records, and information on some of the environmental preferences for the species.
The SPREAD algorithm is foreseen as a WPS process.
The results of SPREAD will rely on the GeoExplorer to vizualize the results of the re-allocations. ICIS is foreseen as the store of re-allocated TS-Objects. For
Does the proposed solution solve other problems associated with EA-CoPCommunity of Practice. Business Cases?
SPREAD has interesting features that can be made available to other use cases. For the development of SPREAD, a lot of ground was broken to establish a SDI, and the integration with WPS and the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. infrastructure was pioneered in SPREAD. This has equipped the infrastructure for advanced processing of Geospatial data.

Public

How big is the expected user community after delivery?
SPREAD has different user categories: Developers, Users, and Consumers.
* The developers arrange the content, ensure they align to D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. metadata formats, and are of good enough quality. They also ensure that the algorithm has sufficient resources, and performs well.
* The users perform re-allocation by selecting the dataset to be re-allocated, the target to re-allocate to, the algortihm to apply, and publish the results.
* The consumers are D4science VREVirtual Research Environment. users (remember, this is not a public dataset producer), or trusted collaborators having been granted access to the geospatial products directly. They are trusted with the task to analyse the results, and re-use the products outside the e-infrastructure.

Productivity

Are the proposed measures effective?
SPREAD is a new developemnt, and it's productivity can not be measured against a benchmark.
Does it reduce a known workload?
Since SPREAD is a new and groundbreaking application, it can not be stated tht it reduces a work-load.

Price

Is the proposed solution cheap?
No, it should only be pursued if the components can be re-used in other scenarios.
Expected effort in PM:
12

Presentation

How is the component delivered to users? (Design / on-line help / training material / support).
SPREAD is conceived to be delivered through a VREVirtual Research Environment. that starts from the ICIS (timeseries data to re-allocate). This should provide GIS features to GIS-enable the time-series.
It also requires an user interface to select a target area & probability-based data sources used to re-allocate,
For the algorithm, machine access to the intersection layer is required.
The output are timeseries with a new geospatial dimension (target area).
Reallocated data maps (as well as initial data maps) have to be managed by generic TimeSeries thematic mapping functionalities.
These maps will have to be accessible by other VREs if the owner so decides.

Privacy

Are they safe?
There are no privacy issues of legal or physical persons involved. However, the risk of misinforming the general audience with SPREAD products requires that a proper work-flow is ensured before data can be published.
Need the proposed solution to manage confidential info at data / dataset / organizational level?
Initially this is not needed.
However, every map produced can only be shared by the VREVirtual Research Environment. User that generated it in the VREVirtual Research Environment.. Only the VREVirtual Research Environment. manager can publish the generated maps to render them discoverable and visible to other VREs.
Describe security and privacy issues:
The SPREAD Policy for data access and sharing is described here

Policy

The SPREAD Policy for data access and sharing is described here

Perils

Do they introduce moral hazard? (A hazard here is the risk that users will behave more recklessly if they are insulated from the effects of the software, or if they do not understand what it produces, where data come from, what they represent etc. .)

Several critical comments were made that have to be better understood before SPREAD can be fully implemented:

  1. Several FI officers have doubts that the produced re-allocated maps can be distributed openly as FAO and / RFB maps. They may convey a message that goes beyond the quality of the data and the algorithm involved.
  2. There is no intrinsic generic mechanism to check the statistical relevance of the products. This may lead to a product that can not be validated.
  3. The quality of the source data may not be up to standards for the required processes. One important reason to develop SPREAD was indeed to identify these gaps in e.g. reliable maps of EEZ's, difficulties in generating reliable intersections, solving issues with authoritative metadata, e.g. to differentiate between country, flag, and sovereignty.
Retrieved from "https://wiki.d4science.org/index.php?title=Ecosystem_Approach_Community_of_Practice:_SPREAD&oldid=21463"