INSPIRE Drafting Team „Data Specifications“

13th EC GI&GIS Workshop - Data Specifications - Clemens Portele - July 2007

INSPIRE Drafting Team „Data Specifications“ Clemens Portele (Chair)

13th EC GI&GIS Workshop - Data Specifications - Clemens Portele - July 2007 - 2 -

ScopeThe development of INSPIRE Implementing Rules forharmonised spatial data follows a two-step approach:1. Development of conceptual framework and

specification methodology. This work started in the Preparatory Phase and will be concluded in the Transposition Phase.

2. Development of data specifications for each data theme listed in the annexes of the Directive. This work will be carried out based on the conceptual framework and specification methodology, based on the INSPIRE roadmap in the next five years. The work foreseen in the Transposition Phase puts the emphasis on the Annex I spatial data themes.


Conceptual framework and specification methodology deliverables

Deliverable Target date 1)

D 2.3: Scope and Definition of Annex I/II/III Themes

April 2007

D 2.5: Generic Conceptual Model April 2007

D 2.6: Methodology for the development of data specifications

August 2007

D 2.7: Implementing rules for exchange of spatial data / data encoding guidelines

December 2007

These deliverables are under the responsibility of the Drafting Team “Data Specifications”

1) Target dates are for drafts for SDIC/LMO consultation


D2.3Definition of Annex Themes and Scope

Identifies definitions and scope of spatial data themes

Based on existing reference material, especially INSPIRE position papers

Consultation with SDICs/LMOs closes July 6

Starting point for the development of Data Specifications

Overview description

of each theme

DT DS SDICs and LMOs

DT DS Thematic Working Groups

comments

D2.3 v2.0 „Definition of Annex Themes and Scope“

Data Specifications for the Annex Themes


D2.5Generic Conceptual Model

Addresses the definition of a generic conceptual model for spatial objects across the data themes

Consultation with SDICs/LMOs closes July 6 Based on the ISO 19100 series Structured according to the identified

components of data harmonisation

(C) Reference model

(H) Object referencing modelling

(G) Coordinate refe-rencing and units model

(A) INSPIRE Principles (B) Terminology

(D) Rules for applicationSchemas and feature catalogues

(K) Identifier Management

(L) Registers and registries

(I) Data translation model/guidelines

(T) Conformance

(E) Spatial and temporalaspects

(F) Multi-lingual text andcultural adaptibility

(M) Metadata (N) Maintenance (O) Quality

(P) Data Transfer (R) Multiplerepresentations

(J) Portrayal model

(Q) Consistency between data

(S) Data capturing


D2.5Generic Conceptual Model

Generic Conceptual Model will be updated based on comments by SDICs and LMOs

Further input for the revision: Questionnaire on the use of the

elements of spatial and temporal schema

Questionnaire on unique identifiers Proposed study on translation

between different schemas Proposed testing of data

specification development process


D2.6 - Methodology for the development of data specifications

Facilitates the process of creating harmonised data specifications for the data themes

Review by Consolidation Team, Drafting Teams and European data harmonisation projects in May 2007

Version for SDIC/LMO consultation planned for August 2007

In parallel a test of the proposed data specification development process is planned



The process of developing INSPIRE data specifications

Requirements Requirements Requirements As - is analysis

Gap analysis

Use Case Development




Requirements and Feature Types

Identification


Identification


Identification


Identification

App Schema Development App Schema Development App Schema Development

Data Product Specification Development

Implementation , testing and validation



Implementation , testing and

validation ( using WFS)

Requirements Requirements Requirements As - is analysis

Gap analysis






Identification


Identification


Identification

Requirements and Sp.Object Types

Identification

App Schema Development App Schema Development App Schema Development

Data Specification Development







Relationship between the framework documents, the consolidated registers and the INSPIRE data specifications

D a ta s p e c if ic a t io n d e v e lo p m e n t f r a m e w o r k(o r ig in a l d ra f ts d e v e lo p e d b y D T D S , re s p o n s ib le : C T a d v is e d b y D T D S )


D 2 .3D e f in it io n o f th e m e s

D 2 .5 G e n e r ic c o n c e p tu a l

m o d e l

D 2 .6 M e th o d o lo g y

D 2 .7 E n c o d in g g u id e l in e s

C o n s o lid a te d r e g is te rs ( re s p o n s ib le : C T )

C o n s o l id a te d r e g is te r s ( re s p o n s ib le : C T )

D r a f t D a ta S p e c if ic a t io n ( re s p o n s ib le : T W G s )

D r a f t D a t a S p e c if ic a t io n ( re s p o n s ib le : T W G s )

AX _L age

+ l a ge be z e i ch n u n g : A X _L a g e b e z eic h n u n g

+ e rfra ge S t a n d a rd p o sit i o n () : AA _ Pu n ktg e o m e t ri e

AA _NRE O< <Fe a ture >> M

AX _ La g e be z e ich n un g+ un v e rsc h lu e sse lt : Ch a ra ct e rS tr i n g+ ve rsch l u e sse l t : A X _V e rsch l u e sse l te L a g e b e ze i ch n u n g

< <U ni o n >>

AX _ La g e be ze i ch n u n gM it Ha u sn u m m e r+ h a u sn u m m e r : Ch a ra cte rS tr i n g+ o rt st e il [0 . .1 ] : C h a ra ct e rS t ri n g

< <Fe a tu re >>

AX _ L a g e b e ze ich n un g M itP se u d o n u m m e r

+ p seu d o n u mm e r : C h a ra ct e rS t ri n g+ l a u f e n d e Nu m m e r [0 . .1 ] : Ch a ra cte rS tr i n g+ o rt st e i l [0 . .1 ] : C h a ra ct e rS t ri n g

<< Fe a t u re > >

A X _ La g e be z e i chn u n gO h n e H au s nu m m e r

+ zu sa t zZur L ag e b e ze ic h nu n g [ 0 ..1 ] : Ch a ra ct e r St r in g+ o rt st e i l [0 .. 1 ] : Ch a ra c te rSt r in g

<<Fe a t u re >>

A X _ V ersc h lu e sse l te L ag e b e ze ich n u n g

+ l a n d : Ch ara ct e r Stri n g+ re g i e ru n g sb e z irk [ 0. . 1 ] : C h a ra c te rS t r in g+ kre is : C h a ra ct e r Str i n g+ g e me in d e : Ch a ra c t e rS tr i n g+ l a g e : Ch ara ct e r Stri n g

( fr om K ata loge)

<<D ata Typ e >>

D r a ft A p p lic a t io n

s c h e m aIS O 1 9 1 0 0< < A p p l i c a t i o n S c h e m a > >

A F IS -A L K I S - A T K IS A n w e n d u n g s s c h e m a

< < A p p l i c a t i o n S c h e m a > >

W e b F e a tu r e S e r vi c e E rw e it e r u n g e n

C o n s o lid a te dU M L m o d e l

G lo s s a r y

F e a tu r ec a ta lo g u e

r e g is te r

C R S /U o Mr e g is te r

p ro v id e s b a s e lin e

m a y p ro v id e c h a n g e re q u e s ts


s h a ll p ro v id e c h a n g e re q u e s ts


C o d e lis tr e g is te r

F e a tu r e c o n c e p t

d ic t io n a r y

D r a f t fe a tu r e

c a ta lo g u e

p ro v id e sf ra m e w o rk







m o d e l


m o d e l





C o n s o lid a te d r e g is te rs ( re s p o n s ib le : C T )

C o n s o l id a te d r e g is te r s ( re s p o n s ib le : C T )

D r a f t D a ta S p e c if ic a t io n ( re s p o n s ib le : T W G s )

D r a f t D a t a S p e c if ic a t io n ( re s p o n s ib le : T W G s )

AX _L age





< <U ni o n >>


< <Fe a tu re >>



<< Fe a t u re > >



<<Fe a t u re >>



( fr om K ata loge)

<<D ata Typ e >>


s c h e m a

AX _L age





< <U ni o n >>


< <Fe a tu re >>



<< Fe a t u re > >



<<Fe a t u re >>



( fr om K ata loge)

<<D ata Typ e >>


s c h e m aIS O 1 9 1 0 0< < A p p l i c a t i o n S c h e m a > >




C o n s o lid a te dU M L m o d e lIS O 1 9 1 0 0





C o n s o lid a te dU M L m o d e l

G lo s s a r yG lo s s a r y


r e g is te r


r e g is te r




m a y p ro v id e c h a n g e re q u e s ts




C o d e lis tr e g is te rC o d e lis tr e g is te r


d ic t io n a r y


d ic t io n a r y

D r a f t fe a tu r e

c a ta lo g u e

D r a ft fe a tu r e

c a ta lo g u e




D2.7 – Guidelines for the encoding of spatial data

Specifies guidelines for the encoding of spatial data for the purpose of exchange between two systems

Data encoding of spatial objects will be specified as part of the data specifications

Data exchange is understood primarily as “access to data via services” which includes but is not limited to a download of a whole dataset closely related to the Download service

Review by Consolidation Team and Drafting Teams planned to start in August 2007


D2.7 – Guidelines for the encoding of spatial data

General approach based on the recommendations of CEN TR 15449 on encoding: ISO 19136 (GML) is promoted as the ESDI

encoding method when transferring spatial objects

ISO/TS 19139 is promoted as the ESDI encoding method when transferring information related to spatial data such as metadata, feature catalogues and dictionaries

The encoding of spatial objects will in general be model-driven, i.e. determined by the application schema

Coverage data will in general use existing encodings for the range part of the coverage function


Technical Architecture Overview High-level overview of the current understanding of the technical

architecture of INSPIRE Illustrate the required elements within the infrastructure, their

relationships and the responsible party for drafting the relevant specification

Two purposes: Support the discussion within and between the parties involved

in the drafting of the technical specification of the individual elements (identify gaps and needs for additional collaboration)

Help SDICs and LMOs to better understand the context of the different deliverables that are being created and which will typically be send to SDICs and LMOs for consultation

Developed since September 2006 mainly be the 3 technical drafting teams and JRC

Proposed to be published as a non-paper


Development of data specifications for each data theme

Requests: Call for

SDICs/LMOs for participation in data specification development

Call for candidate specifications

User requirements survey

Initial set of Thematic Working Groups to start end of 2007


Thank you very much for your interest

Clemens Porteleinteractive instruments GmbH

Trierer Straße 70-7253115 BonnGermany

+49 228 91410 73 [email protected]

Documents

INSPIRE Drafting Team „Data Specifications“