Anette Breu DATA HARMONISATION STEP BY STEP

Anette Breu DATA HARMONISATION STEP BY STEP

Data harmonisation theory Ins tytucj a class overview PodmiotEwidencyjnyLubWladajacy «invariant» {self.administrativelevel < self.lowerlevelunit.administrativelevel} Consider if this should be a datatype or if the attributes should be added to AdministrativeUnit +przynalezy_do 1 JednostkaEwidencyjna Obreb +lezy_w_obszarze Budynek UdzialWladania +wladanie 0..1 +polozony_na JednostkaRejestrowa Dzialka_ewidencyjna UdzialWlasnosci +wlasnosc conceptual data model (UML) «featuretype» Administrativ eboundary + border: GM_Curve + boundarylevel: BoundaryLevelType [0..1] + boundarystatus: BoundaryStatusType [0..1] + country: CountryCode [0..1] + edge: TP_Edge [0..1] + meaningofline: MeaningOfLineType [0..1] We need a definition of AdminstrativeAreaType «featuretype» «datatype» Administrativ eunit AdministrativeLevelType +upperlevelunit 1 + administrativelevel: AdministrativeLevelType + level: AdministrativeHierarchyLevel + area: GM_Surface + nationallevelname: PT_FreeText [] + country: CountryCode + face: TP_Face [0..1] + geographicalname: PT_FreeText +lowerlevelunit + unitcode: CharacterString «enumeration» AdministrativeHierarchyLevel 1 «enum» +administrativearea 1st order (country level) = 1 2nd order = 2 «featuretype» 3rd order = 3 Administrativ eunitarea 4th order = 4 5th order = 5 + administrativearea: AdministrativeAreaType 6th order = 6 + area: GM_Surface + face: TP_Face [0..1] «enumeration» Administrativ eareatype «enum» Main area of administrative unit = 1 Branch area of administrative unit (e.g. exclaves, islands) = 3 Special area (e.g. condominium, non-cadastre area, forest) = 4 (Coastal) water area of administrative unit = 5 Inland water, lakes = 7 +maz PodmiotGrupowy Instytucja OsobaFizyczna +zona 1 Malzenstwo 1 {nie PodmiotGrupowy} +sklada_sie PodmiotEwidencyjnyLubWladajacy UdzialDzierzawy {nie Malzenstwo +zarzad +jest_w_posiadaniu niepodmiotgrupowy} +udzial_posiadania JednostkaEwidencyjna +przynalezy_do 1 UdzialWladania UdzialWlasnosci +wladanie +wlasnosc 0..1 Obreb +nieruchomosc_wladnaca +lezy_w_obszarze JednostkaRejestrowa +nieruchomosc_zwiazana PrawaZwiazane Dzierzawa +prawo_zalezne implementation model (e.g. database or GML schema) +budynek Budynek Lokal_samodzielny +obciaza_nieruchomosc +polozony_na Dzialka_ewidencyjna +przedmiot_dzierzawy 1.* PrzedmiotDzierzawy +obciaza_nieruchomosc +obciaza_nieruchomosc or or

Data harmonisation theory (II) Matching Tables conceptual data model (UML) conceptual data model (UML) encoding rules implementation model (e.g. database or GML schema) Transformation Tool encoding rules implementation model (e.g. database or GML schema)

Approach: GIS4EU - define the mapping from source to target learn from previous projects RISE & HUMBOLDT Develop a common process for all Thematic Working Groups within the project Getting to know the source data models! Expert knowledge about the source data model / schema is essential either by means of a formal schema description or by means of access to those people, who have developed the data model or who are advanced users of it Important role of data providers: they offer the necessary expertise about the source models they can provide the formal descriptions

GIS4EU - define the mapping from source to target (II) Analysing the target, i.e. the INSPIRE data specifications Bring both conceptual schemas together i.e. create matching tables Drawback: lack of suitable tools Solution: comparison table (Excel) Matchingtable GIS4EU approach: Define the structure of the matching table Each GIS4EU TWG included one representative from the INSPIRE TWGs responsible for filling the INSPIRE part data providers took over the responsibility to fill the matching tables with the suitable information of their own data models and to document the challenges encountered

Important findings The perfect match between source models and target models is the exception! Important to consider the different backgrounds and purposes of data models an original cartographic data model does not fit well to INSPIRE data specifications Need for complex transformations in order to create virtual features and attributes that match the target model Requirement: define gradual INSPIRE compliance

From concept to implementation