KOSOVO 3rd meeting of the water monitoring working group

1. KOSOVO3rd meeting of the water monitoring working group Paul Haener International Office for Water p.haener@oieau.fr

2. Table of content • Remind of previous actions • Progress on hydrological database / link with wiski application (HMIK) • Database structure proposal for water quality data • Proposal for hydrological codification • Next steps

3. Remind of previous actions

4. Previous actions • Validating codification rules • Monitoring network • Monitoring station • Parameters • Completing datasets monitoring station • Importing hydrological data necessary for Wiski tests

5. Expected steps after last meeting • Contacts to get to an inter-institutional agreement on codification principles of network, stations, parameters (Fidaim) • Complete XY for manual precipitation stations (Elfete) • Validation of monitoring, stations and parameter characteristics • XLS files to be commented and returned to Agron (all) • Actualisation of data (Agron) • Hydro data • Link with Wiski • Quality data • XY Health Institute stations (Agron) • Data structuring (PH/Agron)

6. Progress on hydrological database / link with wiski application (HMIK)

7. Kosovo QTT monitoring data structure RBD Sub-unit Monitoring network Institution Water segments Water bodies Stations Parameter QTT data Typology

8. First draft of a Kosovo monitoring database

9. Liink with Wiski training

10. Database structure proposal for water quality data

11. Quality data

12. Demo on a access data base • Demo • Next steps

13. Proposal for hydrological codification

14. Management of codes MS will be responsible to • Manage their hydrological codes and non hydrological identifiers • To keep them consistent and unique

15. Unique European codes Following the last CIS recommendations: „Unique European codes will be applied to • Non-hydrological reference features • River basin districts, Sub-units, Water bodies, monitoring stations, discharge points, point sources, … • Hydrological reference features • River(sub)basins • (Main)Rivers • River Segments (reaching from confluence to confluence) • Lakes“

16. Elements of the hydrological code (4) • Can be stored in seperate files in the database – elements can be used flexible • Data exchange – elements can be concatenated • The format of the code will be as follows: HSIICCCCCPPPPPPPPPPPPEELL

17. Thank you for your attention Paul Haener International Office for Water p.haener@oieau.fr

18. Main structure of the codes • Unique non-hydrological identifier are provided by the following format(see CIS Guidance doc. No. 9) MS#1#2…#22 where MS = a 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 Member State. • Entity types can be used to identify the types of features • Non-hydrological reference features should carry the code of the hydrological feature to which they are related as a foreign key

19. Definition of terms Reference features are geographic features reported by Member States to WISE. They can be hydrological features or non hydrological features. (a) hydrological reference features are hydrological features used at European level in WISE as reference for thematic geographic data. Hydrological reference features carry a hydrological feature code (e.g. river basins, rivers, lakes) (b) non-hydrological reference features Non-hydrological reference features carry unique identifiers (e.g. water bodies, monitoring stations)

20. Proposal for coding monitoring features (remind) • Network code • KSMON_AAABB • KS: code of the member state • MON : identification of Monit Network • AAA: Topic : HYD, MET, QLT, GWP, GWQ • BB: indicial number • Station code • KSMOS_AAABBBBB • KS: code of the member state • MOS : identification of Monit Network • AA: Topic : MP (meteo/Prcipitation), SW (Surface water), GW (Ground water) • BBBB: indicial number

21. General recommendations for coding • Code must be stable in time => avoid none useful significant elements inside the code • In relation with characters: Special advice given is that • Alphabetical characters should always be in upper case, as systems will be case sensitive. • Special characters must be avoided, such as ‘$’, ‘!’, ‘&’, ‘ë’, ‘á’, etc. • Digits should be used where practical to help avoid the above problems.

22. Hydrological System and Sea region

23. Elements of the hydrological code • Hydrological System and Sea region code • Island Code • Pfafstetter commencement code • River segments and elementary catchment Pfafstetter code • Entity type code • Lake identifier

24. Elements of the hydrological code (2) • Island coding (proposal available – see Appendix 8) • Pfafstetter commencement code (available with CCM2: http://agrienv.jrc.it/activities/catchments/) • River segments and elementary catchment Pfafstetter code (available with CM2)  see presentation Alfred de Jager

25. Elements of the hydrological code (3) • Entity types • An entity type can be used to identify the type of a feature (see slide 6 – non-hydrological identifiers) • Lake identifier • Required for lakes that are not coneccted to a river network • Has to be managed within an international river basin on European or international level