How to maintain cross border data consistency at state boundaries – A study based on data owned by the National Mapping and Cadastral Agencies Nathalie Delattre National Geographic Institute of Belgium Email: [email protected] Data edge-matching solutions and methodology : Organisational aspects • • • refers to the Article 10(2) of the INSPIRE Directive insure data edge matching results of good quality maintain cross border data through repeating updating. INSPIRE Data Supply Chain Maintain Core Data Core Data Sources National Mapping & Cadastral Agencies Transform into a standard data model and specifications (INSPIRE) National (INSPIRE) data component Data accessible to users NMCA 1 Viewing, Downloading INSPIRE NMCA 2 Core Data Sources Maintain Core Data Transform, into a standard data model and specifications (INSPIRE) National (INSPIRE) Data component Cross border INSPIRE data supply Chain Maintain Core Data National Mapping & Cadastral Agencies Transform into a standard data model (INSPIRE) Core Data Sources National (INSPIRE) data component Supra National Management Integrate cross border features NMCA 1 Edge matching Service Seamless data NMCA 2 Core Data Sources Maintain Core Data Transform into a standard data model (INSPIRE) National (INSPIRE) Data component Unique depiction of state boundaries (State boundaries data base of Europe) Data accessible to users Viewing, Downloading INSPIRE Quality Controlled Edge Matching Process XBDC Quality Measures Agreed DQ Rules Improved & Consistent DQ Web Service, Including EM evaluation Conformance Measures process Agreed EM Actions NMCA Data Expert Knowledge Update Actions Quality Report Source Data NMCA Adjacent NMCA Source Data Integrate /Conflate INSPIRE Data Evaluate Cross Border Quality Edge Match Not OK Update Edge Matched Data Edge matched Data OK Ref. Data EXDB CF Data Euro Cross-boundary Database (EXDB) The database storing EM information 1. Agreed depiction of State Boundaries ( centrally managed ) , serve as reference to national ones. 2. Connecting features storing edge matching information ( point/line features) EXDB Data Model class EuroCrossboundaryDatabase «dataType» EuroCrossboundaryDataset + + referenceScale: CharacterString datasetName: datasetNameValue [0..*] +dataset 1 +boundary 0..* «codeList» datasetNameValue + + + + «featureType» AgreedBoundary + + + + «enumeration» TechnicalStatusValue inspireID: Identifier geometry: Curve technicalStatus: TechnicalStatusValue lastUpdate: Date +boundary EuroRegionalMap EuroGlobalMap ExM_mediumScale ExM_smallScale Has to be revised according to ExM specification and specifications of future pan-European data products. edgeMatched notEdgeMatched 1..* +CF 0..* «featureType» ConnectingFeature + + + + «enumeration» StatusValue inspireID: Identifier status: StatusValue featureType: ExM_featureType edgeMatchingFeature: EdgeMatchingFeature [0..*] «featureType» PointConnectingFeature «featureType» LineConnectingFeature + + geometry: Point geometry: Curve approved proposedForAddition proposedForSuppression unsolved «codeList» ExM_featureType + + + + railwayLine schengenBorderPoint watercourse island Has to be expanded according to ExM specification. EXDB Data Sets User/Producer Controlled Edge Matching Process Using EXDB as ref data for EM of datasets Conclusions • Quality Controlled EM workflow ( Evaluation rules, EM rules) • User/Producer Controlled EM workflow ( decide of acceptable data for EM, decide of evaluation rules and EM rules) • Web EM service ( fully automated) • Based on agreed state boundaries and connecting features for sustainable EM process Jürgen Kerstin BKG Germany NLS Sweden Andreas BEV Austria Nathalie IGN Belgium Matt 1Spatial UK Noémie IGN France Marcus BKG Germany Gabriela Luc ANCPI Romania 1Spatial UK Esa NLS Finland Romain IGN France