Implementing INSPIRE UIDs and life-cycle information in a European SDI.

Transcription

1 Implementing INSPIRE UIDs and life-cycle information in a European SDI. Nathalie Delattre, IGN Belgium Work team: Romain Kereneur, IGN, France Noémie Grémeaux, IGN, France Marcus Brühl, BKG, Germany Esa Tiainen, NLS, Finland

2 User Needs Maintenance of reference information in user databases. Not only Unique IDentifiers but also life-cycle information ( get change only updates ) European contract European users request pan-european datasets with external UIDs and life-cycle information workable at European level within the next three years EuroBoundaryMap ( Administrative regions at scale 1:100k) EuroRegionalMap ( Geo topographical data at scale 1:250k) EuroGlobalMap (Geo topographical data at scale 1:1000k)

3 Objective To set up European rules/guidelines for implementing UIDs aiming at a better interoperability for at cross-border/pan European level. The technical challenge How to implement UIDs and life-cycle information that are maintained at national level but that must be operable at a pan- European level by enabling incremental update?

4 European rules for UId implementation Two types of UIDs : (INSPIRE compliant) created and maintained by NMCAs : <European namespace> <NMCA localid> - created and maintained at supra national level: <European namespace> <European localid> Adopt INSPIRE life cycle attributes versionid beginlifespanversion endlifespanversion Same life cycle rules across Europe : 10 life cycle rules defined Definition of the lifespan cycle of a INSPIRE feature, (new, modified or deleted)

5 European rules implementation: ideal solution Implementation of external UIDs in NMCAs data systems and contents Data sources, NMCA European data (national components) European data (seamless coverage) External ID + Life cycle attributes + European namespace European external ID + Life cycle attributes External UID management for Cross-border features European external ID + Life cycle attributes Use national localid and life cycle information

6 European rules implementation: intermediate solution Implementation of external UID over the national spatial data infrastructure Data sources, NMCA European data (national componants) European data (seamless coverage) Change detection process between two releases European external ID Life cycle attributes External UID management for Cross-border features european external ID Life cycle attributes Creation of European localid and life cycle information Different scenarios must be considered depending on the level of progress in implementation of each NMCA to ensure homogeneous and reliable UID and life cycle information delivery in the pan-european databases

7 UIds implementation at cross-border/pan European level: How this can be achievable, how to proceed? Nathalie Delattre, IGN Belgium

8 Indicators monitoring the level of progress in UIDs implementation

9 Monitoring among NMCAs Number of datasets Country ESDIN member large scale medium scale total Austria yes Belgium yes Croatia no Cyprus no Czech Republic no Denmark yes Estonia no Finland no France yes Germany yes Great Britain no Greece no Hungary yes Iceland no Ireland no Norway yes Romania yes Poland Slovakia no Slovenia no Sweden yes The Netherlands yes

10 Full Adaptability Monitoring Results UIDs Indicators 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Unique Identifier Life-cycle Information Life-cycle Rules All Scale level Large scale Medium-small scale Existence Compliance Adaptability Existence Compliance Adaptability Existence Partial Compliance Full Compliance Partial Adaptability

11 Amended European rules for implementing UIDs based on monitoring results 1. UID structure proposed in the European rules has been widely accepted by all NMCAs 2. Life-cycle attributes: versionid: optional, beginlifespanversion: mandatory, endlifespanversion: optional

12 Compliancy European Rules Description Mandatory Creation A new UID is created The versionid is set to 1. The beginlifespanversion is set to the current date. The endlifespanversion is left empty. 3. Life-cycle Rules Mandatory Suppression The endlifespanversion of the last version of this object is set to the current date; The UID is never reused. Mandatory Stability The UID is kept; The life-cycle attributes are not modified. - Simple rules are mandatory - Complex rules are optional Mandatory Simple feature modification (geometric and/or semantic) Optional Feature Class modification The UID is kept. Its versionid is incremented. Its beginlifespanversion is set to the current date. The endlifespanversion of the previous version of the object is set to the current date. A new UID is created The versionid is set to 1. The beginlifespanversion is set to the current date. The endlifespanversion is left empty. Optional Optional Optional Split curves, surfaces and multisurfaces only Merge curves, surfaces and multisurfaces only Aggregate curves, surfaces and multisurfaces One of the resulting objects retains the UID of the original object. Its versionid is incremented. Its beginlifespanversion is set to the current date. The endlifespanversion of the previous version is set to the current date. The second resulting object is given a new UID Its versionid is set to 1. Its beginlifespanversion is set to the current date. Its endlifespanversion remains empty. The resulting object gets the UID of one of the original objects. The corresponding versionid is incremented. The beginlifespanversion is set to the current date. The endlifespanversion of the previous version of this object is set to the current date. The endlifespanversion of the other original object is set to the current date. The UIDs and life-cycle attribute values must be deduced from the splits and merged which have occurred.

13 Implementing European rules on UIds in the light of what is achievable among NMCAS: SHORT TERM PERSPECTIVE Four levels of progress : Level 4 (ESDIN) : UIDs Implemented + life cycle information + all life cycle rules NMCAS on Referenc data Level 3: UIDs Implemented + life cycle information + basic life cycle rules Level 2 (INSPIRE): UIDs implemented and INSPIRE compliant Level 1: no UIDs implemented or compliant change detection process between two data deliveries Level 3 :National UIDs are used and Life cycle rules are compliant and possibly renumbered when life cycle rules not compliant Level 1-2:Life-cycle information and UIDs are re-calculated (European localid) European Level on pan- European products

14 What could be achievable in longer term NMCAs on Reference Data Level 4 (ESDIN) : never in a consensual way Level 3: can be commonly reached with the amended European rules Level 2 : can be commonly reached by all of them Pan-European products level European/cross border community level INSPIRE level change detection solution and data versioning European level on pan-european products

15 Conclusion INSPIRE regarding UIDs implementation will not sufficiently meet interoperability at European level. European Rules set up in the framework of the ESDIN project should enable historical versioning of pan-european datasets and incremental update delivery at European level. Ideal solutions is that NMCAs adopt the European rules for national perspective If not possible, intermediate solution will be implemented by using a change detection solution and data versioning at European level ( tools) Change detection tools could be applied to national purpose

16 Together we are stronger!