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

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)

Objective

To set up European rules/guidelines for implementing UIDs aiming at a better interoperability for at cross-border/pan European level.

The technical challengeHow 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?

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)

European rules implementation: ideal solution

Implementation of external UIDs in NMCAs data systems and contents

External ID+ Life cycle

attributes

Data sources, NMCA

European external ID+ Life cycle

attributes

European data (national components)

+ European namespace

European external ID+ Life cycle

attributes

European data (seamless coverage)

External UID management

for Cross-border features

Use national localID and life cycle information

European rules implementation: intermediate solution

Implementation of external UID over the national spatial data infrastructure

Data sources, NMCA

Europeanexternal IDLife cycle attributes

European data (national componants)

Change detection process

between two releases

european external IDLife cycle attributes

European data (seamless coverage)

External UID management

for Cross-border features

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

Creation of European localID and life cycle information

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

Nathalie Delattre , IGN Belgium

Indicators monitoring the level of progress in UIDs implementation

Monitoring among NMCAs

large scale medium scale totalAustria yes 4 2 6Belgium yes 2 1 3Croatia no 0 0 0Cyprus no 3 1 4Czech Republic no 3 2 5Denmark yes 1 0 1Estonia no 1 0 1Finland no 1 4 5France yes 1 0 1Germany yes 0 1 1Great Britain no 3 1 4Greece no 0 0 0Hungary yes 0 2 2Iceland no 1 0 1Ireland no 3 0 3Norway yes 1 0 1Romania yes 0 0 0Poland 0 0 0Slovakia no 2 0 2Slovenia no 6 0 6Sweden yes 0 2 2The Netherlands yes 0 0 0

32 16 48

Number of datasetsCountry ESDIN member

UIDs Indicators

0%10%20%30%40%50%60%70%80%90%

100%

Existe

nce

Compli

ance

Adapt

abilit

y

Existe

nce

Compli

ance

Adapt

abilit

y

Existe

nce

Partia

l Com

plian

ce

Full C

ompli

ance

Partia

l Ada

ptab

ility

Full A

dapt

abilit

y

All Scale level

Large scale

Medium-small scale

Monitoring Results

Unique Identifier Life-cycle Information Life-cycle Rules

Amended European rules for implementing UIDsbased 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

3. Life-cycle Rules

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.

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.

Mandatory Simple feature modification

(geometric and/or semantic)

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.

Optional Feature Class modification

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 Split

curves, surfaces and multisurfaces only

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.

Optional Merge

curves, surfaces and multisurfaces only

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.

Optional Aggregate

curves, surfaces and multisurfaces

The UIDs and life-cycle attribute values must be deduced from the splits and merged which have occurred.

- Simple rules are mandatory

- Complex rules are optional

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

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

NM

CA

S o

n R

efer

enc

data

change detection process between two data deliveries

Level 1-2:Life-cycle information and UIDs are re-calculated (European localID)

Level 3 :National UIDs are used and Life cycle rules are compliant and possibly re-numbered when life cycle rules not compliant

European Level on pan-

European products

What could be achievable in longer term

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

NM

CA

s on

Ref

eren

ce D

ata

Eur

opea

n le

vel o

n pa

n-E

urop

ean

prod

ucts

change detection solution and data versioning

Pan-European products level

European/cross border community level

INSPIRE level

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

Together we are stronger!