freshwater eionet workshop, 2015-06-18 agenda item #3b fernanda nery wise spatial data collection

Freshwater Eionet Workshop, 2015-06-18Agenda item #3bFernanda Nery

WISE spatialdata collection

WISE SoE data flows

Water quality

Water quantity

Emissions

Spatial data • Spatial data (or ancillary data related to the sampled unit) repeatedly reported.

Spatial data in SoE Groundwater

Spatial data in SoE rivers and lakes

From WFD

Water quality

Water quantity

Emissions

WISE SoE data flows

• Time-series reporting (annual).• Spatial data reporting

(“on-update”).

Spatial data

StatisticalUnits

SurfaceWaterBody

GroundwaterBody

SubUnit

RiverBasinDistrict

1

1..n

11..n

0..1

1..n1..n1

1

1..n

+relatedZone

+relatedZone

+relatedZone

+featureOfInterest+featureOfInterest

MonitoringSite

1

+relatedTo

Water quality

Water quantity

Emissions

Water quality

Water quality

Water quantity

Water quantity

Emissions

Reference data

other… Spatial data WFD 2016 Spatial data

WISE SoE spatial reference data

Rivers

Lakes

Groundwater bodies

Monitoring sites

Sub-units

River Basin Districts

Protected areas

Common data models• Most of the WFD spatial data

is directly relevant for the WISE SoE data flows.

• Spatial data sets should use a common model across data flows.

• This simplifies the data collection phase (from the Data Providers perspective) and the quality control and data processing(from the EEA and COMM perspective).

How to create a common model?

Spatial data

WISE

WFD

Core

WISE SoE

Start with the core, then add the minimum needed.

Monitoring sitesWISE

WFD

Core

WISE SoE

Monitoring sites• geometry

• inspireId• thematicId

• beginLifespanVersion• endLifespanVersion

• supersedes• supersededBy

• evolutions

WISE

WFD

Core

WISE SoE

life-cycle

ID

location

• name

• featureOfInterest

• relatedTo

• operationalActivity• mediaMonitored• purpose

• link

WISE

WFD

Core

WISE SoEwaterbody

EIONETstation

moreinfo…

Monitoring sites

• catchmentArea

• maximumDepth

• confidentialityStatus

WISE

WFD

Core

WISE SoE

riverstations

drinkingwater

lakestations

Monitoring sites

River basin districtsSub-units

Surface water bodiesGroundwater bodies

WISE

WFD

Core

WISE SoE

• geometry

• inspireId• thematicId

• beginLifespanVersion• endLifespanVersion

• predecessors• successors

• evolutions

WISE

WFD

Core

WISE SoE

life-cycle

ID

location

River basin districts et al.

• name• zoneType• specialisedZoneType

• relatedZone

• designationPeriod• link

WISE

WFD

Core

WISE SoE


link to SU, RBD…

• legalBasis

• horizons

• sizeValue• sizeValueUoM

protected areas

SWB

GWB

• meanDepthWISE

WFD

Core

WISE SoE

standingwaterbodies


Frequently Asked Questions…

Q. Is the model “INSPIRE-compliant”?A. No.

Q. Why?A. Because only some of the INSPIRE

attributes in the INSPIRE AM and EF themes are needed for the WFD and WISE SoE reporting.

(and there are other reasons...)

Frequently Asked Questions

INSPIRE element # Data element Rive

rBas

inDistr

ict

SubU

nit

Surf

aceW

ater

Body

Surf

aceW

ater

Body

Line

Gro

undW

ater

Body

Mon

itorin

gSite

2 inspireIdLocalId 1 1 1 1 1 13 inspireIdNamespace 1 1 1 1 1 14 inspireIdVersionId 1 1 1 1 1 15 thematicIdIdentifier 1 1 1 1 1 16 thematicIdIdentifierScheme 1 1 1 1 1 1

inspireId

thematicId

Q. Why are there more attributes in the list?A. Because Data Providers requested a flat attribute structure.


… which is another reason why the model is not INSPIRE-compliant

Q. If the structure is flat, how are multiple attributes stored?

A. In most cases where the INSPIRE models allow multiple values, only one was really needs for the specific case of the WFD and SoE reporting.

In other situations, a not-so-elegant solution was adopted. For example:

nameNL, for the name in the national language,

name, for the English version (optional attribute).


Q. Why is there a SurfaceWaterBody data set and a SurfaceWaterBodyLine data set ?

A. Because Data Providers requested that shapefiles would be allowed in the spatial data reporting.

In the shapefile format polygons and lines must be stored in separate data files.So 2 data sets are needed. Same approach was then taken in the GML format.

… which is another reason why the model is not INSPIRE-compliant


Q. Must the shapefile format be used?

A. No. Data Providers are encouraged to use the GML format (XSDs will be provided for each data set).

But, if they need to use shapefiles (empty “template” files will be provided for each data set),then the files will be converted to GML when the envelope is delivered in CDR.

… more on that in the next presentation


Q. Is the life-cycle information mandatory?

A. Only if applicable.

But if it isn’t provided, we’ll continue to have broken time series and being unable to use the full potential of the data in the European assessments.


Q: The predecessors and successors attributes are not in the INSPIRE AM theme.

A: Correct. They came from INSPIRE Statistical Units theme.The life-cycle management that will be adopted in WISEclosely follows what is described in Annex F of the INSPIRE Data Specification on Statistical Units.

Q: What are the supersedes and superseedBy attributesin the MonitoringSites data set?

A: The same concept as above. The attributes have a different name in the INSPIRE EF theme.(there are two similar situations, that are flagged in the model).


"Multiple thematic object identifiers may be assigned to a zone where different data exchange requirements (e.g. national vs European reporting) have defined different lexical rules for thematic object identifiers. Where multiple thematic object identifiers exist all should be provided. This shall allow external datasets that use these thematic object identifiers for referencing to link to the INSPIRE spatial object."Spatial Object WFD Reporting Identifier Scheme WISE SoE Reporting Identifier Scheme

Monitoring Site 'euMonitoringSiteCode' 'eionetMonitoringSiteCode'

Surface Water Body 'euSurfaceWaterBodyCode' 'eionetSurfaceWaterBodyCode'

Groundwater Body 'euGroundWaterBodyCode' 'eionetGroundWaterBodyCode'

Sub Unit 'euSubUnitCode' 'eionetSubUnitCode'

River Basin District 'euRBDCode' 'eionetRBDCode'


Q: Why use thematic identifiers?

A:

So, thematic identifiers are used in all the data sets.Also, they are used to link between data sets.

wfd eionet1

2

3

4

5

6

Monitoring Sites in Country XZ

7

8

# thematicIDIdentifier

thematicIDIdentifierScheme

relatedToIdentifier

relatedToIdentifierScheme

1 XZ1 euMonitoringSiteCode - -

2 XZ2 euMonitoringSiteCode - -

3 XZ3 euMonitoringSiteCode XZeionetCodeForSite3 eionetMonitoringSiteCode

4 XZ4 euMonitoringSiteCode XZeionetCodeForSite4 eionetMonitoringSiteCode

5 XZ5 eionetMonitoringSiteCode - -

6 XZ6 eionetMonitoringSiteCode - -

eionet1

2

3

4

5

6

Monitoring Sites in Country ZZ

7

8



relatedToIdentifier

relatedToIdentifierScheme

3 ZZ3 eionetMonitoringSiteCode - -




wfd eionet1

2

3

4

5

6

Groundwater bodies in Country XZ

7

8



1 XZ1 euGroundWaterBodyCode




5 XZ5 eionetGroundWaterBodyCode

6 XZ6 eionetGroundWaterBodyCode

eionet

Groundwater bodies in Country ZZ



3 ZZ3 eionetGroundWaterBodyCode




1

2

3

4

5

6

7

8


Q: Couldn’t the INSPIRE identifier be used instead of the thematic identifier?

A: Not all EIONET countries are EU Member States,so they may not be implementing INSPIRE.

(in this case, just report the national ID as the inspireID localID)

(Also, it would make it more difficult to report predecessors or a relatedZone that may not have an INSPIRE ID)


Q: When can we have a fully-compliant INSPIRE data model ?

A: The EEA (IDM&NSV) just initiated a project focused on monitoring sites, both for freshwater and marine.Results to be presented in next year EIONET workshop.

Q: Will that change the reporting process?

A: Not in the short term. 2020 ?

Spatial data

Rivers

Lakes

Groundwater

Monitoring Sites

SUs

RBDs

A: Yes. It needs to be in place to collect:

• data from countries not reporting under WFD

• EIONET sites not used in WFD monitoring & reporting

• reporting unitsthat are not WFD WaterBodies(e.g. very small lakes)


Q: Spatial data will be collected via WFD. Will a separate spatial data flow be in place?

Freshwater Eionet Workshop, 2015-06-18Agenda item #3bFernanda Nery

Questions?Thank you

Freshwater Eionet Workshop, 2015-06-18Agenda item #3b

Next: Ongoing developments in the reporting infrastructure for WFDand WISE portal design. Alberto Telletxea, Bilbomatica

Content1. Improve the workflow

2. Data dissemination improvement

Freshwater Eionet Workshop, 2015-06-18, Agenda item

#3b

Alberto Telletxea, Bilbomatica

UML as starting point

• Standard data modelling -> UML• Single area for modifications and versioning• Automatic derivation of reporting tools and DB

model

UML

XML Schemas for spatial and descriptive data

XML files GML files

Shapefiles

Access DB

European databases


#3b


Allow visibility during the workflow

Under analysis


#3b


Technical solution

MS data area upload

CDR - Reportnet

XML-RPC protocol

Converters - ReportnetQA/QC

execution area

FME- IDM infrastructure

REST API

QA/QC and ETL procesess

IDM data dissemination infrastructure

ReportsMaps

REST API


#3b


WISE Portal (water.europa.eu)

Search engine to explore data and information

Common access to:

- reports (tables, indicators)

- data products

- geospatial data visualisation

- documents (PDFs, …)

1st phase – restricted area (COM, EEA, ETC), for data reporting

results

2nd phase – public area, for specific data products not in the EEA

website

3rd phase? – restricted area (countries), for country data

reporting results

Data dissemination improvement


#3b


Restricted area - login


#3b



#3b


Restricted area - search


#3b


Restricted area – explore

Freshwater Eionet Workshop, 2015-06-18Agenda item #3b

Next: Calendar and other changes. Olaf Büttner, ETC/ICM

freshwater eionet workshop, 2015-06-18 agenda item #3b fernanda nery wise spatial data collection

Documents

wfd spatial data

spatial data reporting

spatial data sets

soe groundwater spatial

ancillary data

data processingfrom

data providers perspective

data collection phase