Freshwater Eionet Workshop, Agenda item #3b Fernanda Nery WISE spatial data 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 SurfaceWaterBod y GroundwaterBody SubUnit RiverBasinDistrict 1 1..n n 1 1 +relatedZone +featureOfInterest MonitoringSite 1 +relatedTo Water quality Water quantity Emissions Water quality Water quantity Emissions Reference data

other…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 WFDWFD Core WISE SoE Start with the core, then add the minimum needed.

Monitoring sites WISE WFD CoreCore WISE SoE

Monitoring sites geometry inspireId thematicId beginLifespanVersion endLifespanVersion supersedes supersededBy evolutions geometry inspireId thematicId beginLifespanVersion endLifespanVersion supersedes supersededBy evolutions WISE WFD CoreCore WISE SoE life-cycle ID location

name featureOfInterest relatedTo operationalActivity mediaMonitored purpose link name featureOfInterest relatedTo operationalActivity mediaMonitored purpose link WISE WFD Core WISE SoE water body EIONET station more info… Monitoring sites

catchmentArea maximumDepth confidentialityStatus catchmentArea maximumDepth confidentialityStatus WISE WFD Core WISE SoE river stations drinking water lake stations Monitoring sites

River basin districts Sub-units Surface water bodies Groundwater bodies WISE WFD CoreCore WISE SoE

geometry inspireId thematicId beginLifespanVersion endLifespanVersion predecessors successors evolutions geometry inspireId thematicId beginLifespanVersion endLifespanVersion predecessors successors evolutions WISE WFD CoreCore WISE SoE life-cycle ID location River basin districts et al.

name zoneType specialisedZoneType relatedZone designationPeriod link name zoneType specialisedZoneType relatedZone designationPeriod link WISE WFD Core WISE SoE River basin districts et al. link to SU, RBD… legalBasis horizons sizeValue sizeValueUoM sizeValue sizeValueUoM protected areas SWB GWB

meanDepth WISE WFD Core WISE SoE standing water bodies River basin districts et al.

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

Q. Why are there more attributes in the list? A. Because Data Providers requested a flat attribute structure. Frequently Asked Questions … 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). Frequently Asked Questions

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 Frequently Asked Questions

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 Frequently Asked Questions

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. Frequently Asked Questions

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 WISE closely follows what is described in Annex F of the INSPIRE Data Specification on Statistical Units. Q: What are the supersedes and superseedBy attributes in 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). Frequently Asked Questions

"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." Frequently Asked Questions 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.

wfdeionet Monitoring Sites in Country XZ 7 8 # thematicID Identifier thematicID IdentifierScheme relatedTo Identifier relatedTo IdentifierScheme 1XZ1euMonitoringSiteCode-- 2XZ2euMonitoringSiteCode-- 3XZ3euMonitoringSiteCodeXZeionetCodeForSite3eionetMonitoringSiteCode 4XZ4euMonitoringSiteCodeXZeionetCodeForSite4eionetMonitoringSiteCode 5XZ5eionetMonitoringSiteCode-- 6XZ6eionetMonitoringSiteCode--

eionet Monitoring Sites in Country ZZ 7 8 # thematicID Identifier thematicID IdentifierScheme relatedTo Identifier relatedTo IdentifierScheme 3ZZ3eionetMonitoringSiteCode-- 4ZZ4eionetMonitoringSiteCode-- 5ZZ5eionetMonitoringSiteCode-- 6ZZ6eionetMonitoringSiteCode--

wfd eionet Groundwater bodies in Country XZ 7 8 # thematicID Identifier thematicID IdentifierScheme 1XZ1euGroundWaterBodyCode 2XZ2euGroundWaterBodyCode 3XZ3euGroundWaterBodyCode 4XZ4euGroundWaterBodyCode 5XZ5eionetGroundWaterBodyCode 6XZ6eionetGroundWaterBodyCode

eionet Groundwater bodies in Country ZZ # thematicID Identifier thematicID IdentifierScheme 3ZZ3eionetGroundWaterBodyCode 4ZZ4eionetGroundWaterBodyCode 5ZZ5eionetGroundWaterBodyCode 6ZZ6eionetGroundWaterBodyCode

Frequently Asked Questions 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)

Frequently Asked Questions 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 ?

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 units that are not WFD WaterBodies (e.g. very small lakes) Frequently Asked Questions Q: Spatial data will be collected via WFD. Will a separate spatial data flow be in place?

Freshwater Eionet Workshop, Agenda item #3b Fernanda Nery Questions? Thank you

Freshwater Eionet Workshop, Agenda item #3b Next: Ongoing developments in the reporting infrastructure for WFD and WISE portal design. Alberto Telletxea, Bilbomatica

Content 1. Improve the workflow 2. Data dissemination improvement Freshwater Eionet Workshop, , 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 filesGML files Shapefiles Access DB European databases Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica

Allow visibility during the workflow Under analysis Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica

Technical solution Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica

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 Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica

Restricted area - login Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica

Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica Restricted area - search

Freshwater Eionet Workshop, , Agenda item #3b Alberto Telletxea, Bilbomatica Restricted area – explore

Freshwater Eionet Workshop, Agenda item #3b Next: Calendar and other changes. Olaf Büttner, ETC/ICM