1 Laboratory on Geoinformatics and Cartography 6. DATA MODELS, UNDERSTANDING THE UML DIAGRAMS AND OTHER FORMALISED DESCRIPTIONS Laboratory on Geoinformatics and Cartography 1. The infrastructures for spatial information in the Member States should be designed to ensure that spatial data are stored, made available and maintained at the most appropriate level; 2. that it is possible to combine spatial data from different sources across the Community in a consistent way and share them between several users and applications; 3. that it is possible for spatial data collected at one level of public authority to be shared between other public authorities; Well-known principles of INSPIRE (1/2) Laboratory on Geoinformatics and Cartography 4. that spatial data are made available under conditions which do not unduly restrict their extensive use; 5. that it is easy to discover available spatial data, to evaluate their suitability for the purpose and to know the conditions applicable to their use. Well-known principles of INSPIRE (2/2) Laboratory on Geoinformatics and Cartography To not reach the bad feeling from INSPIRE… what user wantspromised solution requirements description proposed concept realisation Převzato z: http://geekfun.pl/pm_build_swing.gif, upraveno Laboratory on Geoinformatics and Cartography One of the main SDI goals server 1 server 2 server 3 server 4 klient Laboratory on Geoinformatics and Cartography • Natural disasters do not stop at national borders – 20% of the EU citizens (115 million) live within 50 km from a border • 70% of all fresh water bodies are part of a trans-boundary basin Cross-border concern Images adopted from Cetl, V. 2013 2 Laboratory on Geoinformatics and Cartography 16.08.2001 Vertical and positional coordinate reference systems in Europe Images adopted from Cetl, V. 2013 Laboratory on Geoinformatics and Cartography Consequences of spatial data islands Adopted from: Fichtinger, Klien and Giger, 2009 • Inconsistent data - geometrically - attribute -semantically - … Laboratory on Geoinformatics and Cartography Cartographic consequences server 1 client server 2 server 3 Laboratory on Geoinformatics and Cartography • Article 7: “[…] technical arrangements for the interoperability and, where practicable, harmonisation of spatial data sets and services […]” – What does that mean? • Based on existing initiatives and international standards for the harmonization of spatial data sets Data models in INSPIRE Laboratory on Geoinformatics and Cartography • A common framework for the unique identification of spatial objects, to which identifiers under national systems can be mapped in order to ensure interoperability between them; • The relationship between spatial objects; • The key attributes and the corresponding multilingual thesauri commonly required for policies which may have an impact on the environment; • Information on the temporal dimension of the data; • Updates of the data Addressing following aspects of spatial data Laboratory on Geoinformatics and Cartography Broader view on INSPIRE data models Implementing Rules (IR) Coordinatereferencesystems Geographicalgridsystems Protectedsites Elevation Geology Statisticalunits Mineralresources Annex I Data specifications Landcover Buildings Energyresources … … … Annex II Data specifications Annex III Data specifications D2.3 Definition of Annex Themes & Scope D2.5 Generic Conceptual Model D2.6 Methodology for Specification Development D2.7 Guidelines for Encoding Conceptual framework Common requirements (IR articles) Parts for all 34 themes Common types (Annex I) 3 Laboratory on Geoinformatics and Cartography • Implementing rules (Commission Regulation 1089/2010 and 1253/2013) – Legally binding in all EU Member States – Defined according to the cost-benefit analyses • Technical Guidelines (Data specifications) for all 34 spatial data themes – Technical basis for Implementing rules – Explanations and examples to guide you through the implementation process Documents for all INSPIRE data models Laboratory on Geoinformatics and Cartography Data specification example: HY - Hydrography Laboratory on Geoinformatics and Cartography WaterCourse Node WaterCourse Link Data specification example: HY - Hydrography Laboratory on Geoinformatics and Cartography WFDCoastalWater WFDLakeWFDTransitionalWater WFDRiver Data specification example: HY - Hydrography Laboratory on Geoinformatics and Cartography WatercourseNode Watercourse Link Basin Catchment SpringOrSeep Rapids DamOrWeir Lock Watercourse StandingWater HydroPowerPlant PumpingStation Pipe Embankment Shore LandWaterBoundary Crossing Wetland WFDCoastalWater WFDLake OceanRegion WFDTransitionalWater WFDRiver Data specification example: HY - Hydrography Laboratory on Geoinformatics and Cartography WatercourseNode Watercourse Link Basin Catchment SpringOrSeep Rapids DamOrWeir Lock Watercourse StandingWater HydroPowerPlant PumpingStation Pipe Embankment Shore LandWaterBoundary Crossing Wetland WFDCoastalWater WFDLake OceanRegion WFDTransitionalWater WFDRiver Data specification example: HY - Hydrography SurfaceWater beginLifeSpanVersion DateTime endLifeSpanVersion DateTime geometry GM_Primitive inspireID Identifier levelOfDetail MD_Resolution localType LocalisedCharacterString origin OriginValue persistence HydrologicalPersistenceValue tidal Boolean 4 Laboratory on Geoinformatics and Cartography Expression in the UML Laboratory on Geoinformatics and Cartography Structure of a data specification (1/3) Laboratory on Geoinformatics and Cartography Structure of a data specification (2/3) Laboratory on Geoinformatics and Cartography Structure of a data specification (3/3) Laboratory on Geoinformatics and Cartography Requirements vs. recommendations