Environmental datacentres Current status in Go4 and EEA discussions Stefan Jensen

Biodiversity DC meeting 30.9.2009Biodiversity DC meeting 30.9.2009

Environmental datacentres

Current status in Go4 and EEA discussions

Stefan Jensen


Go4 acitivities on data centres


HistoricHistoric

”Political” agreement on DC’s by Go4 based on shared responsibilities (2005)

Establishment of a common architecture team (CADT) > prepare an Enterprise architecture report (draft) (2007-08)

Reporting on annual DC progress (2007-08) in DIMESA meetings

Shaping of DC acitivities as key SEIS actions on EU level amongst Go4 partner (2009)


• Different progress on indivdual DCs

• MDIAK reflection • Common elements template• ...

State of discussionState of discussion


EEA activities related to data centres


Building EnvironmentalBuilding Environmentaldata centresdata centres

History:• Ongoing, growing data work in thematic areas since the

start of EEA• Go4 technical agreement on responsibilities in late 2005• Participation in Go4 DC architecture group since 2006• Limited, scattered internal EEA discussion• Launch of first version of water data centre March 2007• First reporting sheets on DC progress in 2007• Initial effort to prepare implementation plans 2008

(Land)• Intensified discussion along the June 2008 visit of ESTAT

consultants tasked to do a common architecture proposal

• Horizontal papers produced by „SEIS team“ • DC team announced in fall 2008• Formally established early 2009


Data Centre concept –Data Centre concept –a Go4 technical definition a Go4 technical definition

• Environmental data centres are institutionally supported facilities providing convenient access to, manipulation of, and/or distribution of data sets relating to a specific thematic area (including supporting information and expertise) to users. They are intended to have a long lifespan, as they are not tied to a specific project


Data Centre concept –Data Centre concept –EEA adaptation/refinement EEA adaptation/refinement

• The focus of the Data Centre is on the data handling. All other tasks are defined to lie outside the EDC. A Data Centre at the EEA is a data custodian of European data and data service provider to other EU-organisations, the MS and the general public. It lies within the task to provide a quantitative analysis of the data and provide the data part of the presentation of an indicator or a spatial presentation but not to provide the assessment.


Each data centre shallEach data centre shall

• Collect, store, maintain, update and make available any kind of data within their thematic area that is necessary for both creating the indicators that have been specified as well as other specified assessments to support EU policies relevant for the European level

Actions:• Frame scope by defining indicator/data

relationship (thematic groups)



• Collect, store, maintain, update and make available data based on EU reporting obligations (Directives, Systems, SoE voluntary arrangements) and other agreed tasks within the thematic area

Actions:• Define other agreed tasks (thematic groups)



• Provide a link and set up agreements on storage and/or access to data hosted by other data centres / institutions (“foreign” datasets) and create (?) and maintain these data in order to produce a quantitative analysis of the data for the presentation of all indicators at the European level within the thematic area

Actions:• Identify necessary partnerships and set up

agreements where needed (DC contacts with SES3/SES1)


Each data centre shallEach data centre shall• Work in close contact with data providers at both the

national, European and global level

• Take an active part in implementing SEIS - the EDC’s are the data custodians for their specified thematic area at the European level

• Use a common European spatial data infrastructure based on the implementation rules set out by the INSPIRE directive

Actions:• Engage in the INSPIRE process (DC contacts with SES3)

(ongoing for water and nature/biodiversity) and derive development needs



• Follow the work on e-government to ensure interoperability for environmental data within their theme

Action:• SES to follow and advise

• Follow the development of GMES in order to meet the upcoming in situ data requirements for related services

Action:• SES1 to identify (DC contacts with SES1)


Each data centre shallEach data centre shall• Be responsible for the QA/QC procedures at the European

level and maintain metadata descriptions both for the data and for the indicators as well as data flowcharts for each indicator relevant for the thematic area

Action:• SES2 to stepwise organise

• Provide and maintain web pages as part of the EEA website and provide links to interoperable web based applications for metadata, discovery, view and download services.

Action: • Organise links and services (DC contacts with SES3 and

OSE)


Next steps / priority tasksNext steps / priority taskstowards DC interoperabilitytowards DC interoperability

• Review/establish implementation plans• Identify/review indicator/data relations per

DC (SES2 END lead?)• Identify service developments needs in line

with INSPIRE (e.g. metadata related) • Plan common DC web pages (as part of EEA

website re-design)• Identify additional QA/QC tasks• Set up roadmap for GMES implementation• Identify and encourage common technical

elements


Expert services

Applications

System-to-system services

Data hosting

European data centreEuropean data centretechnical functions technical functions (OSE/SES view)(OSE/SES view)


Area Function General comments Individual data centre content (some thoughts/notes)

Data (service) Display of available data and download

Pretty much as the current data service(Could also link to key datasets provided by partners)

available

Data viewer As current

Map viewer As current

Indicators Indicators linked to the theme

by keyword/theme tag CSI + (SEBI etc)

Reporting Listing of obligations (ROD);Access to CDR

Pre selection based on area (let’s see what is possible there)

As available

Web services Link to machine to machine data exchange e.g. through discomap

Future other INSPIRE network services, only available for LUDC for now

On protectd areas?tbd

Links ETC, key partner URL’s, document libraries (CIRCA et.al.), Clearinghouses,other Data Centres

Could also link to key datasets provided by partners

Network aspects especially important for BiodIvSpecial role for clearinghouse

Explanation Allows each DC to provide some own story about status/plans etc. evt.logos of partnerships

...

Thematic Simple link to stories/reports/assessments etc.

Switches to the theme site of the website(the theme site would consequently need a data link)


Review of present data centre webpresences across Go4 websites

DC priority setting

Suggested common elements of datacentres

Boundary discussions / limitations (EEA websiteintegration)

Revisit common aspectsRevisit common aspects


Key ideas from the BISE discussion


Constructing a systemConstructing a system

Indicators and assessments

Viewing of information

Other data, e.g. spatial layers of direct interest

Data on sites, species & habitats

Spa

tial D

imen

sion

, IN

SP

IRE

& S

EIS

rul

es,


Lead roles in MDIAK chain for Lead roles in MDIAK chain for biodiversitybiodiversity


Things to achieve ...

DiscussionBiodiversity ”profile”Needed adjustments

Thank you!

Environmental datacentres Current status in Go4 and EEA discussions Stefan Jensen

Documents

Transcript of Environmental datacentres Current status in Go4 and EEA discussions Stefan Jensen