on Air Quality Management and Assessment

Transcription

1 9 th EIONET Workshop on Air Quality Management and Assessment EEA support of European Environment reporting Reportnet v2 (urls added) Sheila Cryan 1

2 European environment reporting Many people with different tasks: Data definers (obligations, technical formats) National data suppliers Data collectors Information providers Information users EEA Regulation (1210/90 Article 2ii) requires Agency to provide appropriate support for reporting requirements...with the aim of coordinating reporting. 2

3 Reportnet: 2 tracks Technical: electronic infrastructure and tools for streamlining flows of environmental information in Europe on-going Organisational: business process reengineering (BPR) of reporting processes started August

4 Reportnet: electronic infrastructure and tools Web based Reportnet modules Integrated modules Open source ( Distributed responsibility Shared challenge Standards 4

5 Reporting: why, what, when, how and who Data definers (obligation, technical formats) Data suppliers (countries) 5

6 ROD provides regularly maintained information on: why legislative instrument reporting obligation what, how reporting formats specifications when deadlines national calendar who national coordinators national reporters requesting institution other user institutions ROD ( 6

7 Data dictionary DD: What and how Technical specification document MS Excel template XML schema 7

8 Reporting: supporting national suppliers and tracking deliveries Data suppliers (countries) Data collectors 8

9 Network Directory ND: Air and Climate Change Who s who Shows EIONET NRCs Maintained at national level Facilitates communication Management of permissions throughout Reportnet 9

10 Data Exchange Modules (1 st IT tools to support reporting) supporting national suppliers to provide high quality data Help desk Specifications Data transfer QA rules Feedback on quality 10

11 National repository for deliveries Several types of repository have been used for national data Repositories for EEA requests Dataflow specific ftp://ftp.mnp.rivm.nl/e tcacc/upload/dem... Country specific s/irc/circa-it/reportnet/library Generic CDR CIRCA 11

12 National repository: CDR Increasing use at European level EoI 20+ countries CDR Countries can customize structure Experimentation at national level Germany Light to develop 12

13 Reporting: SoE and underlying data Information providers Information users 13

14 European repository Data from all countries, (harmonised) and quality checked Many repositories at European level Dataflow specific Airbase holds complete EoI Generic EEA data service holds aggregated level for use in further products 14

15 Content Registry CR: Provides a view of contents across an increasing number of Reportnet modules plus EEA reports Based on Dublin core metadata element set Used for communication between ROD and CDR 15

16 Reportnet: work in progress 2004 Generic Data Exchange Mechanisms (GDEM) 1st GDEM module webquestionnaire introduced (see additional detail in the second part of this presentation) Indicator Management Service (IMS) populated with specifications for EEA core set of indicators 16

17 Reportnet: next steps Develop missing parts of the Reportnet data exchange and harmonisation system Geared towards improved, customised user interfacing (web dashboards, notification services) Providing advanced data handling functions (data tranformation and merging) Add functionalities identified by BPR project 17

18 PART II Additional information on GDEM 18

19 GDEM: Generic Data Exchange Mechanisms Modular framework for handling reporting with primary focus on XML Quality assessment mechanism Feedback to data providers Our first dataflow via GDEM technology Groundwater Bodies 19

20 GDEM main pillars Four upload mechanisms Webbrowser, Specialised application, System-to-CDR delivery, Webquestionnaire Automatic quality assessments Feedback Data conversion Workflow 20

21 21 QA

22 How to build a dataflow 1. Describe obligation in ROD 2. Describe datastructure in DD 1. XMLSchema 3. Generate webform template 1. Modify it for userfriendlyness 4. Develop QA rules 5. Design the workflow 6. Develop conversions 22

23 23 Describe obligation in ROD

24 24 Describe datastructure in DD

25 25 XMLSchema

26 26 Generate webform template

27 27 Tweak it to this

28 Develop QA Rules (:===================================================================:) (: Rule 1 :) (: Goes through all the Rows in the document and checks if there exist:) (: similar EWN codes in the same document:) (: if yes, returns the code, if no, returns nothing = empty String:) (:===================================================================:) declare function local:checkewncode($url as xs:string) { for $pn in fn:distinct values(fn:doc($url)//dd8:generalcharacterisation/ dd8:row/dd37:ewn Code) let $i := fn:doc($url)//dd8:generalcharacterisation/dd8:row[ dd37:ewn Code= $pn] where fn:count($i) > 1 order by $pn return <b>{$pn}<br></br></b> }; 28

29 29 Design the workflow

30 30 Develop conversions

31 How is it all integrated? Everything is revolving around CDR Only the workflow part is integrated The rest are optional modules Webquestionnaire Conversions QA service Best way is by demonstration 31

32 32 Envelope just created

33 33 Envelope activated

34 34 The global task list