Reporting and Exchange of Air Quality Information Under CAFE Directive Using INSPIRE Services Testbed Results

Transcription

1 Reporting and Exchange of Air Quality Information Under CAFE Directive Using INSPIRE Services Testbed Results Alina Kmiecik, Dominik Kobus, Magdalena Bednarek, Anna Zamolska, Piotr Krok, Marek Brylski, Carmelo Attardo 24/6/2010

2 Presentation scope Lot general information Pilot project workflow elements: metadata data model model transformation Reporting prototype architecture INSPIRE service integration Conclusions

3 Project general information Title: Development and demonstration of technical IT solutions for data Exchange and reporting under CAFE Directive using INSPIRE services LOT 2: de-centralized with less than 100 stations Customer: The European Community represented by Commission of the European Communities represented by Institute for Environment and Sustainability of the Joint Research Center. Contract no Project involved participants: PARTNER ROLE RESPONSISBILITIES INTERGRAPH Poland Chief Inspectorate for Environmental Protection (CIEP) Mazovian Voivodship Inspectorate for Environment Protection in Warsaw (VIEP) West-Pomeranian Voivodship Inspectorate for Environment Protection in Szczecin (VIEP) Contractor, Project leader, Technological partner national LMO regional LMO regional LMO Domain Analysis, Functional Design, Services Development Project Management, LOT2 Contact Point Data Provider Air Quality Data Expert Regional Data Provider Regional Data Provider Institute of Environmental Protection (IEP) Domain expert Air Quality Data Expert INTERGRAPH Italy Technological partner Project Management

4 Project partners: Polish LMO s National LMO: Chief Inspectorate for Environmental Protection Regional LMO s: West Pomeranian Voivodship Inspectorate for Environmental Protection Mazovian Voivodship Inspectorate for Environmental Protection Intergraph Project Lider Institute of Environmental Protection Warsaw, Poland

5 Project overall workflow D 1.1. Report Current implementation of reporting and data exchange D.1.2. Report Integration of INSPIRE services with the CAFE reporting Prototype assessments D. 2.4 Report Conformity of the reporting under CAFE Directive D. 2.3 Report Demonstration of the prototype for compliance to INSPIRE rules D Report Data specification for air quality data according to INSPIRE and CAFE requirements D Report Architecture of the reporting prototype D 2.2 Report D Report D Report D Report Methodology of transformation ORIGINAL DATA REMODELED DATA METADATA D Report D Report Metadata profile Data processing

6 Reporting prototype - components INSPIRE-compliant download services established for air quality data reporting, GML application schemas defined for INSPIRE compliant publication of air quality data, AQD database schemas for collecting and publishing of air quality data from CIEP, VIEP Mazovia and VIEP West Pomeranian Data Providers, FTPService for uploading of near-real time air quality monitoring into the publication databases view services for ear-real time and validated air quality data, metadata catalogue and discovery service for collecting and searching of AQ metadata, SEIS-CAFE Geoportal.

7 Data scope in the project

8 Original resources

9 Developing metadata final profile Resource Title (mandatory) Resource Abstract (mandatory) Resource Type( mandatory) Resource Locator (mandatory) Unique Resource Identifier (mandatory) Coupled Resource (mandatory) Resource Language (mandatory) Topic Category (mandatory) Spatial data service type (optional) Spatial data service type: View (optional) Spatial data service type: Download (mandatory) Keyword value (mandatory) Originating controlled vocabulary (mandatory) Geographic description (optional) Geographic bounding box (mandatory) Temporal Extent (mandatory/optional - depending of the dataset) Date of publication (mandatory for datasets / optional otherwise) Date of last revision (optional) Date of creation (optional) Lineage (mandatory) Spatial resolution (mandatory) Specification (mandatory) Degree (mandatory) Conditions applying to access and use (mandatory) Limitations on public access (mandatory) Responsible party (mandatory) Metadata Point of Contact (mandatory) Metadata Date (mandatory) Metadata Language (mandatory)

10 Metadata discovery example

11

12 Data model specification for air quality data requirements CAFE requirements Draft CAFÉ Implementing Povisions (as of January 19, 2009) Requirements for scope of air quality information Technical requirements for air quality information exchange Requirements extracted from Airbase Data Dictionary INSPIRE requirements Recommended methodology for common model development Recommendations for INSPIRE data specifications Requirements of Generic Conceptual Model Requirements for Application schema encoding

13 Model elements Feature types 18 Data Types 10 Code lists 38 16/3/2010 SEIS - CAFE Project final workshop - Brussels

14

15 Remoddeling process - workflow PHASE 1: PRELIMINARY PROCESSING OF PRODUCTION DATA DATA TRANSFER FILE FORMAT STEP 1: Input data model analysis STEP 2: Output data model analysis DATABASE SCHEMA PRODUCTION DATABASE STEP 3: Model mapping STEP 4: Definition of data processing rules DATA TRANSFER FILE STEP 5: Execution of processing rules PUBLICATION DATABASE DOWNLOAD SERVICE PHASE 2 ON THE FLY TRANSFORMATION OF PUBLICATION DATA Apply XSLT SEIS - CAFE Project final Define workshop XSLT - transformation Brussels transformation DATABASE SCHEMA GML APPLICATION SCHEMA AIR QUALITY 15

16 Model Mapping - example ORIGINAL DATA MODEL SEIS CAFE PILOT AIR QUALITY DATA MODEL FEATURE TYPE FEATURE ATTRIBUTE VALUE DOMAIN FEATURE TYPE FEATURE ATTRIBUTE VALUE DOMAIN Strefy nazwa strefy Datatype: Varchar2 Datatype: Zone zonename Minsize=1 CharacterString Maxsize=60 Strefy kod_strefy Datatype: Varchar2 Datatype: Zone zonecode Minsize=1 CharacterString Maxsize=60 Strefy zanieczyszczenia Datatype: Varchar2 Datatype: pollutant (foreign key to Zone Minsize=1 CharacterString Pollutant feature type) Maxsize=255 Strefy aglomeracja Datatype: Varchar2 Datatype: Zone zonetype Minsize=1 CharacterString Maxsize= 50 Strefy powierzchnia Datatype: Number Zone area Datatype: Number Strefy liczba_miesz Datatype: population (foreign key Datatype: Varchar2 Zone to Population feature Minsize=1 Number type) Maxsize= 255 Shp files Zone boundary source Datatype: (geospatial file/ LAU2 Zone geometry SDO_GEOMETRY list)