Embed Size (px)
Citation preview
- 1 -
Technical document: How to use Reportnet for reporting under the Article 15 of the UWWTD 1
How to use Reportnet for reporting under the article 15 of the Urban Waste Water Treatment Directive (91/271/EEC)
(Version December 2017)
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 2
Contents
Introduction .......................................................................................................................... 3
1. How to find the reporting obligation for UWWTD on Reportnet (ROD) ................... 4
2. How to find and download data definition, templates and supporting documents 5
3. How to compile tabular data for UWWTD reporting .................................................. 5
4. Quality checking of the data ....................................................................................... 7
5. How to compile GIS data for UWWTD reporting ....................................................... 8
6. How to deliver data under the Article 15 of the UWWTD through Reportnet ......... 9
7. Confirmation of receipt ............................................................................................. 13
8. Help desk and support .............................................................................................. 13
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 3
Introduction
These guidelines explain how to use Reportnet (the European Environment Agency's electronic
infrastructure for data collection) for finding information and reporting information to the EU
Commission in pursuance of the Article 15 of the Urban Waste Water Treatment Directive
(91/271/EEC). The reporting is organised in collaboration between DG Environment and the
European Environment Agency (EEA).
The guidelines addresses the whole reporting process involving:
acquiring the reporting obligation from Reportnet,
downloading data definition, reporting templates and supporting documents
data compilation using xml schema or xls template
compiling spatial UWWTD data
uploading dataset on the Central Data Repository in Reportnet
quality analysis of reported data
confirmation of receipt
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 4
1. How to find the reporting obligation for UWWTD on Reportnet (ROD)
ROD is the part of Reportnet where you can find the EEA's reporting obligations database. It
contains records describing environmental reporting obligations that countries have towards in-
ternational organisations.
Fig. 1 reporting obligation database
Go to http://rod.eionet.europa.eu/index.html
Select issue: Water
Select Organisation: Comission – European
ComissionClick on GO icon
Scroll to find „Reporting obligation for: Urban
Waste Water Treatment Directive - Implementa-
tion (Art. 15)
Finding
UWWTD
reporting
obligations
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 5
2. How to find and download data definition, templates and supporting documents
In the reporting obligation „ Reporting obligation for: Urban Waste Water Treatment Directive -
Implementation (Art. 15) you will find a link to the Eionet Central Data Repository General help
website, section „Urban Waste Water Treatment Directive”, where all guidance documents,
templates, schemas pertaining to the UWWTD Article 15 are available under the section „Urban
Waste Water Treatment Directive“
Member States are required to report tabular data in terms of xml-files, GIS files, additional doc-
uments and reports under the UWWTD. The list of documents relevant for the reporting under
the UWWTD includes the following:
Data dictionary and codification of parameters for UWWTD Questionnaire/providing in-
formation on the minimum parameters, data types and data formats
Microsoft Excel Templates for Article 15 reporting
Xml schemas for Article 15 reporting
Hyperlink to prefilled spatial data templates
List of automatic quality checks for Article 15 reporting
3. How to compile tabular data for UWWTD reporting
In the 2017 reporting exercise, Member States are asked to provide UWWTD tabular data in
predefined templates.
The data requested should be derived from existing national and/or regional information systems
within each Member State and should contain in particular:
1. Information on designated sensitive areas and their catchments (and also less sensitive areas
in case they have been designated)
2. Information about agglomerations, including
(a) required information (according to the data dictionary) (agglomerations/treatment
plants/discharging points/receiving areas/receiving water bodies) and
(b) complete information per each agglomeration: part (a) plus information on waste water col-
lection, conduction, treatment performance, etc.
http://cdr.eionet.europa.eu/help/UWWTD/
UWWTD_613
Direct link
to UWWTD
Art 15 re-
porting
guidelines
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 6
3. Aggregated information on Member State level on sewage sludge and waste water reuse
‘Old’ Member States (EU-15) are requested to report
information for all three parts mentioned above including all information about agglomera-
tions related to 1998, 2000 and 2005 deadlines and to deadlines pursuant articles 5(6) and
5(7)-update of sensitive areas.
‘New’ Member States Bulgaria, Croatia, Czech Republic, Cyprus, Estonia, Hungary, Lat-
via, Lithuania, Malta, Poland, Romania, Slovakia, Slovenia are requested to report
information for all three parts mentioned above including all information about agglomera-
tions for which transitional periods have already expired
required information (according to the data dictionary) for agglomerations for which
transitional periods have not expired yet
Member States have two options to create the requested UWWTD xml-files from tabular data
and upload them into the CDR: The first option is to fill in the xls data template and convert it
into XML using the web conversion tool. The other option consists of direct export of xml file
from national databases.
Fig. 2 Microsoft excel template
Reference year
for 2017 repor-
ting exercise:
• Status as on 31/12/2016 should be reported
• Monitoring results for the year 2016: from
01/01/2016 to 31/12/2016.
• The information for the entire Member State
has to be consistent and refer to a unique,
clearly indicated, reporting year
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 7
Option 1: Creation of xml files by using Microsoft excel template Use the Microsoft excel template available on the CDR. The structure of the template follows the
data dictionary. Complete the xls template with your data. Then, to convert your files to xml,
send your data in the xls template to your country envelope on CDR, where it will be converted
automatically.
Please note that it is no longer possible to use the webtool (as was available for previous report-
ing exercises) as the data structure has been changed.
Option 2: Creation of xml files directly from the national databases If the Member State has a national water information system and/ or a central database on
UWWTD data, the Member State can compile the data directly into the required xml-format.
XML-schemas are available on EEA Eionet Central Data Repository General help. The generat-
ed xml-format can then be uploaded to the CDR.
4. Quality checking of the data
The overall quality checking process consists of three steps as shown in the schema below:
Data compilation quality check (internal)
Reportnet automatic quality control on CDR (UWWTD Art.15 QAQC queries)
Additional checks after data submission
Please note!:
It is necessary to upload tabular data in xml format on
CDR, otherwise the automatic QC procedures will
not be carried out after the data upload and the data
provider will not receive feedback! Compliance
assessment will use only the datasets uploaded in
CDR and having passed automatic QC .
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 8
.
5. How to compile GIS data for UWWTD reporting
MSs will be requested to supplement tabular data on the receiving areas (sensitive areas,
catchment of sensitive areas, less sensitive areas) with corresponding spatial data.
For the 2017 reporting exercise, ETC-ICM have prepared data templates with data previously
reported by countries. The prefilled templates can be found at
https://forum.eionet.europa.eu/x_wise-
reporting/library/restricted_distribution/XX/uwwtd_sensitiveareas_2016_XX
(please replace XX in the link with your country abbreviation)
There are two options for reporting spatial data on receiving areas:
- The spatial data have not changed since the last reporting exercise. In this case the pre-
filled templates can be uploaded as the current data delivery. - The spatial data have changed (new sensitive areas, changes in the delineation). In this
case please upload the newly created dataset. It is recommended to use the WFD tools
and templates (ProtectedArea, ProtectedAreaLine). Gml schemas, shapefile templates
and gml to xml convertor are available at
http://cdr.eionet.europa.eu/help/WFD/WFD_521_2016. Instructions in WISE GIS Guid-
ance (v6.0.6 2016-04-29) should be followed.
Quality checks on spatial data are not automated in CDR. Semi- automated checking after
data submission is used to reveal serious errors. This checking focuses on
- Coordinate system – the coordinate system ETRS89 should be used for Europe, WGS84
for non-European territories - Topology - Consistency with tabular data (in XML). Please upload only quality assured spatial data, without topological errors and with correct
object codes consistent with the tabular part of reporting
MS Internal QC
• Data compilation into the Microsoft excel templates/xml
• Internal data checks
CDR QC
• Reportnet automatic quality control on CDR after data upload
Additional QC
• additional rules, spatial data check
• Review of the datasets
• QC during compliance check
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 9
6. How to deliver data under the Article 15 of the UWWTD through Reportnet
Step 1: User accounts and access permissions
Only authorized national reporters with an Eionet account, user name and password are able to
upload the national delivery. The national reporters are designated by the national focal points
(NFPs) and are listed in the list of “Authorised WISE data providers for UWWTD”. Please in-
form ETC ICM ([email protected]) in case of changes in nomination of nation-
al reporters.
Step 2: Enter the Central Data Repository, login to your country folder and create an enve-
lope under Urban Waste Water Treatment Directive 91/271/EEC - Implementation
When preparing for the Urban Waste Water Treatment Directive (UWWTD) delivery, you first
have to go to the respective UWWTD folder in EEA’s Central Data Repository, see the links in
Table 1 (overleaf).
Fig. 3 Central data repository login
a) Log into the UWWTD folder of your country by using your Eionet user name and password
b)
Now create a new envelope into which your data will be up-
loaded. Add a meaningful title for the envelope (proposed
title for the envelope is “UWWTD Implementation Programme
YYYY ”). Where YYYY is the reference year used in the re-
port. Please note that the reference year should be indicated in
the envelope heading. Envelope description and coverage note
fields are optional.
c) Open the new envelope by clicking on its title.
d) Activate the task, by clicking on the related button. Activating means that you have reserved
the envelope for yourself to work on. Other users will not be able to modify it. Your new enve-
lope is now in Draft status and files can be added.
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 10
Table 1: Member State URL to UWWTD Article 15 folder in EEA Central Data
Repository
Country current URL
AT http://cdr.eionet.europa.eu/at/eu/uwwt/
BE http://cdr.eionet.europa.eu/be/eu/uwwt/
BG http://cdr.eionet.europa.eu/bg/eu/uwwt/
CY http://cdr.eionet.europa.eu/cy/eu/uwwt/
CZ http://cdr.eionet.europa.eu/cz/eu/uwwt/
DE http://cdr.eionet.europa.eu/de/eu/uwwt/
DK http://cdr.eionet.europa.eu/dk/eu/uwwt/
EE http://cdr.eionet.europa.eu/ee/eu/uwwt/
ES http://cdr.eionet.europa.eu/es/eu/uwwt/
FI http://cdr.eionet.europa.eu/fi/eu/uwwt/
FR http://cdr.eionet.europa.eu/fr/eu/uwwt/
GR http://cdr.eionet.europa.eu/gr/eu/uwwt/
HR http://cdr.eionet.europa.eu/hr/eu/uwwt/
HU http://cdr.eionet.europa.eu/hu/eu/uwwt/
IE http://cdr.eionet.europa.eu/ie/eu/uwwt/
IT http://cdr.eionet.europa.eu/it/eu/uwwt/
LT http://cdr.eionet.europa.eu/lt/eu/uwwt/
LV http://cdr.eionet.europa.eu/lv/eu/uwwt/
LU http://cdr.eionet.europa.eu/lu/eu/uwwt/
MT http://cdr.eionet.europa.eu/mt/eu/uwwt/
NL http://cdr.eionet.europa.eu/nl/eu/uwwt/
PL http://cdr.eionet.europa.eu/pl/eu/uwwt/
PT http://cdr.eionet.europa.eu/pt/eu/uwwt/
RO http://cdr.eionet.europa.eu/ro/eu/uwwt/
SE http://cdr.eionet.europa.eu/se/eu/colsycrwq/
SI http://cdr.eionet.europa.eu/si/eu/uwwt/
SK http://cdr.eionet.europa.eu/sk/eu/uwwt/
UK http://cdr.eionet.europa.eu/gb/eu/uwwt/
NO http://cdr.eionet.europa.eu/no/eu/colp0r2w/colsyn6cw/
Step 3: Upload your UWWTD data and make it available
Upload your Article 15 data from your own system using the
“Upload delivery” option. The uploading menu provides you
with a check box to restrict a file from public access should
this be necessary. Files with access restriction can only be
downloaded by privileged users. Please provide your data in
correct up-to-date xls template. The data will be automatically
converted to XML format.
Step 4: Testing your data after uploading on CDR
Clicking the “Run automatic QA” button allows you to run a
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 11
syntax check and reference check of the uploaded file. Corre-
sponding error reports will be displayed.
The errors are classified into four groups: blocker/error/warning/information.
Blocker – serious issues, the envelope cannot be released
Error - the envelope may be released but some explanation is required. Please note, er-
rors should be avoided. You should upload a file with errors only under exceptional cir-
cumstances.
Warning – less serious issues, does not prevent release of an envelope.
Information – minor issue, does not prevent release of an envelope.
If blockers or errors were identified by the QC, please correct your dataset, activate the task in
your envelope once more, delete current datafiles containing blocker/errors and re-upload the
whole delivery. Then run the full QC again. A related message is given in the status field of the
envelope overview tab or under the “data quality” section (fig. 4-6).
Fig. 4 automatic QA result
Fig. 5 automatic QA result
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 12
Fig. 6 automatic QA result
It is not possible to release the envelope as long as there are “blockers” identified by the QC.
Note that you will be able to upload data even with errors flagged by the automatic QC, however
in this case you will be very likely contacted by the ETC by e-mail and asked for clarifications
Step 5: releasing the envelope
Once you are satisfied that you have uploaded the correct
file(s), QA process was executed, no blockers (and if possi-
ble no errors) are found, complete your delivery by releas-
ing the envelope. First click the button “Activate task” and
then “Release envelope”. The purpose of release is to signal
that the data have been delivered. Your dataset is now pub-
licly available in the Reportnet Central Data Repository
(CDR) unless you have applied access restrictions as ex-
plained above.
Once the envelope is released, it is marked as an official delivery and the specific file cannot
be further changed by the reporter. The status of the delivery will be “Task(s) waiting to be
assigned: Final feedback” until the delivery has been inspected and accepted by the data man-
ager at ETC or EEA.
The final feedback is provided by the ETC/EEA data manager (who now has the rights to acti-
vate the envelope). Once the data manager has inspected the delivery, the status changes to “En-
velope is complete”. If the data manager has technically rejected the delivery due to errors or
incompleteness, reporters will be contacted and asked for clarifications. The data will need to be
corrected by reporter and submitted under new envelope as described above (Steps 3-5). If the
data manager has technically accepted the delivery, no further actions are necessary.
Once the status has been changed to “Envelope is complete”, the delivery will be marked as an
official delivery and the specific file cannot be changed; data updates, corrections and re-
submissions can be delivered via separate envelope which enables clear and automated tracking
of delivery versions in the database.
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 13
7. Confirmation of receipt
An acknowledgment of receipt is generated when an envelope has been released and completed.
This confirmation document is available in the feedback section of the CDR envelope and a noti-
fication will be forwarded to the subscribers.
8. Help desk and support
Help desk :
• On Reportnet CDR: http://cdr.eionet.europa.eu/help
[email protected] (in case of
login problems)
• On 2017 UWWTD reporting exercise:
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 14
Annex I identifier management and update Concise coding will ease up electronic data transfer in the future and allow linkage to additional
datasets that use the same coding mechanism. Reported objects feature coding is the assignment
of unique identification codes to each table or spatial feature that will be referenced by GIS. This
assignment needs to be managed to ensure uniqueness at national and international level. Stand-
ard code formats will ease electronic data transfer and enhance the possibility of central querying
against distributed storage.
Unique European codes should be generated by placing the ISO 2 character national code for
each Member State in front of up to 22 characters unique identifier codes generated within
Member States.
Unique European codes are provided by following format
MS #1#2….#22 where:
MS = 2 character Member State identifier, in accordance with ISO 3166-1-
Alpha-2 country codes, and
#1#2…#22 = an up to 22 character feature code that is unique within the Mem-
ber State symbol # = wildcard character (a wildcard character can
be used to substitute for any other character or characters in a string).
Coding of sensitive areas and less sensitive areas
The feature code for sensitive areas should be unique also among the different types of sensitive
areas. Therefore the following format for the sensitive areas code is recommended:
MS SA #1#2….#22 where:
MS = 2 character Member State identifier, in accordance with ISO 3166-1-
Alpha-2 country codes, and
SA = a 2 character code for the sensitive area (see below)
#1#2…#22 = an up to 22 character feature code that is unique within the Mem-
ber State symbol # = wildcard character (a wildcard character can
be used to substitute for any other character or characters in a string).
The following 2 character unique identifiers for sensitive areas are recommended:
RI for Sensitive Area – river
LK for Sensitive Area – lake
CL for Sensitive Area – coastline
CA for Sensitive Area – coast area
CM for Sensitive Area – catchment
LS for Less sensitive area (coastline)
TW for Sensitive Areas and Less Sensitive Areas – transitional waters*
Definitions:
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 15
Transitional waters - WFD Article 2(6): are bodies of surface water in the vicinity of river
mouths which are partly saline in character as a result of their proximity to coastal waters but
which are substantially influenced by freshwater flows.
Transitional waters are for example estuaries, salt lakes or lagoons.
Estuary: is a semi-enclosed body of water where fresh water from the land, usually from a river,
meets salt water from the sea. In the sense of UWWTD (Art. 2.12) an “estuary” means the transi-
tional area at the mouth of a river between fresh-water and coastal waters.
Salt lakes and Lagoon (tropical): are bordered by land on at least one side and are blocked from
the sea by sandbars or coral reefs. Salt lakes and Lagoons are typically shallow and do not have a
major point source of fresh water input, such as a river, but do collect fresh water as it is dis-
charged from the land through storm water runoff or groundwater infiltration. The salinity of a
salt Lake and lagoon depends on; seasonal rainfall, fresh water flowing from the land, evapora-
tion, and the exposure to sea water.
Examples how to use unique identifiers:
A sensitive area lake in Italy might have the identifierITLK45734
or an agglomeration in Spain might have the identifierES6712454212145
Use of the MS #1#2….#22 and MS SA #1#2….#22 is the only requirement for unique Euro-
pean feature identification codes. Codes of this format should be used for initial and subse-
quent references to features reporting to the Commission.
Underscores (“_”) must not be used directly after the Member State identifier (MS). This could
result in difficulties when creating European codes by placing the ISO 2 character national code
for each Member state in front of up to 22 characters unique identifier codes generated within
Member States. However, underscores can be used as part of the 22 character feature code (e.g.
an agglomeration in Spain might have the identifier ESAG_67124542145)
Technical document: How to use Reportnet for reporting under article 15 of the UWWTD 16
Annex II. Management of the lifetime of reported objects
Life cycle of the spatial objects reported under the UWWTD are derived from provision of arti-
cles 5.6 and 6.4 of the Directive.
Principles of historic data management are specified in Appendix 9 of Guidance Document No.
22 Updated Guidance on Implementing the Geographical Information System (GIS) Elements of
the EU Water policy.
The identifier (ID) of reported object has to remain unchanged during its life-time. If features
are re-coded, links to historical data and links to data related to these features will be lost. It is
therefore necessary to establish a system that manages the changes of objects in time and identi-
fies predecessors and successors.
For reporting under the UWWTD it is essential that the IDs of all sensitive areas, agglomera-
tions, UWWTPs and discharge points, reported for the previous reporting exercise, are reported
again.
Agglomeration, UWWTP, Discharge Points
In a case where an element is no longer relevant, because e.g. the UWWTP reported previously
was closed and another one was built, then the status of the closed UWWTP has to be indicated
to be 0 (= inactive) for the current reference period of reporting and the parameter uwwEndLife
has to be completed. A similar procedure can be applied for deactivated agglomerations or dis-
charge points. The link between current identifiers and their predecessors must be reported in a
separate table (a change list - AggloUWWTPDischargepointchange_template).
Sensitive and less sensitive areas
In a case where the receiving area is no longer operational , this should be indicated in the attrib-
ute rcaEndLife. The successor of this receiving area must be designated and the link between
predecessor and successor reported in the template ReceivingAreasSALSAPredecessor.
When an element was reported as inactive for one reference year, it does not have to be reported
again in the following year.
Please always give an explanation (either in the remarks field or in a separate list), why the ele-
ment became inactive for the reference date of reporting and – in case of a successor – please
also indicate the ID of the successor.
