WP6

Cost-benefit Analysis

Meeting– JRC- May 16/18, 2011

JRC – May 16/18, 2011

Objectives

• To develop and apply methodologies and tools to assess societal benefits of INSPIRE and GEOSS for the three thematic areas of EUROGEOSS (Forestry, Drought, Biodiversity) as well as other SBAs of GEOSS and to undertake an overall aggregated benefit assessment.

• To develop prescriptive guidance for “value of information” analysts in the geospatial field and contribute also to current efforts in assessing the impact of public sector information.

JRC – May 16/18, 2011

Portfolio of EuroGEOSS Benefit Assessment Techniques

Forests

BayesianEU-FASOM

Biodiversity

Real Options

Drought

EuroGEOSS Benefits

EuroGEOSS

Survey Techniques

Systems Dynamics Model (FeliX)

GLOBIOMModel Cluster

JRC – May 16/18, 2011

Linkages among EuroGEOSS Surveys

Survey 5Meta-study of

relevant literature

Survey 4Challenges in provision of

GEOSS

Survey 3

Requirements from Users

Survey 1

Requirements of EG Partners

Survey 2

VMM Survey of EG Partners

JRC – May 16/18, 2011

Outline

• User Requirement Surveys (JRC)• VMM (IIASA)• Broker/Client Assessment (IIASA)• FeliX (IIASA)• Meta-study (UH, Felis)

JRC – May 16/18, 2011

Update on VMM: Benefit chain

(?)CTBLs

JRC – May 16/18, 2011

Update on VMM: Next questionnaire

• Retain the same group of experts• To derive the assessment to €

– EuroGEOSS relevant share s – time period T– budget of client projects L (?)

JRC – May 16/18, 2011

EG-Broker: 06.2010 vs. 05.2011

*For 2011 the following (all connected Web 2.0) services are excluded from analysis: Flickr, Twitter, Wikipedia, GeoCommons, GeoNames, OpenStreetMap.

JRC – May 16/18, 2011

EG-Broker/GI-go: User Perspective

• Questionable info from Web 2.0 - flikr, wikipedia...• Selection of dataset type - [no]picture (ideally raster/vector

data)• Abstract unreadable (one line, need even to scroll to it)• No clear description of a dataset (parameter, units, spatio-

temporal resolution)• The URL link to a data source does not open automatically

(Data identification -> Point of contact -> Responsible party -> Contact info -> Online resource -> Linkage)

• EuroGEOSS configuration should be included in GI-go (must not be a default configuration)

JRC – May 16/18, 2011

EG-Broker/GI-go: Programmer’s Perspective

Excellent team.

API?

Documentation?

JRC – May 16/18, 2011

FeliX

JRC – May 16/18, 2011

FeliX: Scenarios

JRC – May 16/18, 2011

FeliX: Results

JRC – May 16/18, 2011

Partners