INSPIRE Technical Implementation

11

Modèle TN-02.018-1.2

Technical implementation of Technical implementation of

INSPIRE: feedINSPIRE: feed--back from back from

experiencesexperiences

Lisbon – 27 February 2013

[email protected]

2

PlanPlan

•• Introduction Introduction

•• MetadataMetadata

•• Services Services

•• InteroperabilityInteroperability

3

IntroductionIntroduction

•• SourcesSources

–– Implementation of INSPIRE in IGN FranceImplementation of INSPIRE in IGN France

–– KEN INSPIRE workshops:KEN INSPIRE workshops:••KEN : Knowledge Exchange NetworkKEN : Knowledge Exchange Network

••Members: National Mapping and Cadastral AgenciesMembers: National Mapping and Cadastral Agencies

••October 2012 : INSPIRE servicesOctober 2012 : INSPIRE services

••February 2013: strategy to implement INSPIRE specifications February 2013: strategy to implement INSPIRE specifications

on interoperabilityon interoperability

–– European projects (ESDIN, Humboldt)European projects (ESDIN, Humboldt)

–– Other (INSPIRE conferences, Other (INSPIRE conferences, ……..)..)

4

IntroductionIntroduction

•• Colour coding Colour coding

Best practice : what is good, what works wellBest practice : what is good, what works well

Issue: what is not nice, what does not workIssue: what is not nice, what does not work

Potential solution , lesson learnt from experience : what may helpPotential solution , lesson learnt from experience : what may help

5

Metadata

6

BenefitsBenefits

Main benefit of INSPIRE is to reveal hidden data setsMain benefit of INSPIRE is to reveal hidden data sets

7

We have made political decision to document all our products by INSPIRE

metadata even if they are not in INSPIRE scope.

The European Commission is happy to harvest also metadata for products out of

INSPIRE scope

(UK)

We have made political decision to document all our products by INSPIRE

metadata even if they are not in INSPIRE scope.

The European Commission is happy to harvest also metadata for products out of

INSPIRE scope

(UK)

Which data sets for INSPIRE?Which data sets for INSPIRE?

We document all our products by INSPIRE metadata even if they are not in INSPIRE

scope ….

but we make some filtering to avoid too many error reports from the European

Commission (Germany)

We document all our products by INSPIRE metadata even if they are not in INSPIRE

scope ….

but we make some filtering to avoid too many error reports from the European

Commission (Germany)

•• Is it possible to have a broader scope than INSPIRE? Is it possible to have a broader scope than INSPIRE?

8


We document all our data sets that are in the INSPIRE scope by INSPIRE metadata

even if they won’t/ can’t be made interoperable …

but we make some filtering and we declare to the European Commission only

those to be made interoperable (Sweden)

We document all our data sets that are in the INSPIRE scope by INSPIRE metadata

even if they won’t/ can’t be made interoperable …

but we make some filtering and we declare to the European Commission only

those to be made interoperable (Sweden)

There is misunderstanding about the data sets to be documented by INSPIRE

metadata:

-All those in the scope of INSPIRE *

-Only those that will be made interoperable

There is misunderstanding about the data sets to be documented by INSPIRE

metadata:

-All those in the scope of INSPIRE *

-Only those that will be made interoperable

* With first option, there is risk to get bad indicators for Monitoring

and Reporting

9


Reference documentReference document

The identification of INSPIRE data sets is an iterative process and in many countries,

the list of INSPIRE data sets evolves every year.

The identification of INSPIRE data sets is an iterative process and in many countries,

the list of INSPIRE data sets evolves every year.

We began the identification of INSPIRE data sets using the few lines describing a

theme in the INSPIRE Directive.

According to the - coming soon- specifications for annexes II and III, there will be

more data sets and more data producers involved for some themes (Sweden –

theme Geology)

We began the identification of INSPIRE data sets using the few lines describing a

theme in the INSPIRE Directive.

According to the - coming soon- specifications for annexes II and III, there will be

more data sets and more data producers involved for some themes (Sweden –

theme Geology)

10


GranularityGranularity

The solution might be to manage parent-child relationship between the product

(data set series) and the data set, in order to provide metadata at relevant

granularity.

The solution might be to manage parent-child relationship between the product

(data set series) and the data set, in order to provide metadata at relevant

granularity.

What is a data set? How big should it be?

“We have a lot of predefined data sets. INSPIRE requires to document them by

metadata … but it makes the search by users more difficult.”

-Too small: not convenient for discovery

-Too big : not convenient for download

What is a data set? How big should it be?

“We have a lot of predefined data sets. INSPIRE requires to document them by

metadata … but it makes the search by users more difficult.”

-Too small: not convenient for discovery

-Too big : not convenient for download

11

It is difficult to get good quality, INSPIRE compliant metadata from other data

providers. Situation may be even worse for annexes II and III themes.

It is difficult to get good quality, INSPIRE compliant metadata from other data

providers. Situation may be even worse for annexes II and III themes.

Some countries are organising help for metadata providers: guidelines, Wiki, …

This help is generally provided in national language.

Some countries are organising help for metadata providers: guidelines, Wiki, …

This help is generally provided in national language.

Metadata qualityMetadata quality

12

• Which software are you using to host your metadata?

Technical aspectsTechnical aspects

13

MethodologyMethodology

•• For a given data producer, how to identify the data For a given data producer, how to identify the data

sets to be documented by INSPIRE metadata? sets to be documented by INSPIRE metadata?

–– Are you the owner/producer of data?Are you the owner/producer of data?

••Ex: data from IGP is to be documented by IGP not by data usersEx: data from IGP is to be documented by IGP not by data users

••Ex: coEx: co--production => find agreement in order that only one producer production => find agreement in order that only one producer

does the workdoes the work

–– Is your data in the INSPIRE scope?Is your data in the INSPIRE scope?

••In digital formatIn digital format

••Related to territory of a Member StateRelated to territory of a Member State

••From a public body From a public body

••Related to at least a theme of annexes I, II and IIIRelated to at least a theme of annexes I, II and III

–– Can you benefit from exceptions?Can you benefit from exceptions?

••Public security, IP rights, privacy, Public security, IP rights, privacy, ……

••Case of municipalities (less obligations / INSPIRE)Case of municipalities (less obligations / INSPIRE)

14

Methodology Methodology

The matching with INSPIRE themes may be coarse (especially if same

data appears in other data set)

IGN has declared the main theme (e.g. there are also buildings and administrative units in

BD Parcellaire)

15

Network services

16

Discovery services

Technical aspects

GeoNetwork CSW is a good solution regarding INSPIRE requirements.

(Germany – UK)

GeoNetwork CSW is a good solution regarding INSPIRE requirements.

(Germany – UK)

17

Discovery services

Technical aspects

Storing data and metadata at same place helps to fulfill INSPIRE requirements.

(Germany)

Coupling data and metadata is also a solution.

(France)

Storing data and metadata at same place helps to fulfill INSPIRE requirements.

(Germany)

Coupling data and metadata is also a solution.

(France)

Synchronisation of data and metadata is a difficult topic.

18

Discovery services

Conformance

The validation results may vary according the version of XML schema (ISO or OGC) and

according to the parser.

Even the Commission had 2 validators giving different results.

The harvest by Commission generates too many reports with too many errors, making

impossible to analyse them.

(Sweden, UK)

The validation results may vary according the version of XML schema (ISO or OGC) and

according to the parser.

Even the Commission had 2 validators giving different results.

The harvest by Commission generates too many reports with too many errors, making

impossible to analyse them.

(Sweden, UK)

IOC TF might create an integrated XML schema (with the best of OGC and ISO) or OGC

and ISO might converge.

IOC TF might create an integrated XML schema (with the best of OGC and ISO) or OGC

and ISO might converge.

19

• What is the general architecture of your INSPIRE view service(s)? services or

WMTS services, or both?

View services

Technical aspects

There is no obvious solution for view service architecture.

20

• Which software do you use to provide the view services?

WMS services or WMTS services, or both?

Balance between commercial and open-tools solutions.

View services

Technical aspects

21

you provide WMS services or WMTS services, or both?

•Do you provide WMS services or WMTS services, or both?WMS services or

WMTS services, or both?

View services

Technical aspects

22

The management of layers is complex: grouping of layers, layers for data out of INSPIRE,

matching existing data to INSPIRE themes, …

“Naming of layers is mandatory but impossible for existing data”

(France – Sweden – Belgium)

The management of layers is complex: grouping of layers, layers for data out of INSPIRE,

matching existing data to INSPIRE themes, …

“Naming of layers is mandatory but impossible for existing data”

(France – Sweden – Belgium)

View services

Layers

23

There are open-source tools (Deegree, Geoserver, Mapserver) that are compliant

with INSPIRE requirements (at least, with IR). Commercial solutions (ESRI,

Intergraph) also claim INSPIRE compliance.

(foss4GI survey)

The INSPIRE extensions (e.g. multilingualism) raise some issues.

Multilingualism is really required in some countries (Belgium)

Multilingualism is also an issue for other services.

View services

Tools

24

WMS may be used with reasonable performances if levels of zoom are well-defined.

There is big interest in case of continuous update.

(Rhine-Palatinat)

WMS is flexible but need more resources on server side and may be slow for large

scale data.

Many NMCAs use WMTS to get better performances.

(Sweden, …)

View services

Technical aspects

25

There are (at least) two tools to check compliance of view services to INSPIRE:

neogeo and the GDI test suite.

They do not check exactly same topics and look complementary.

Moreover, JRC has also a tool for conformance : GeoPortal proxy.

View services

Conformance

26

Currently, we can not ensure 7 days / 24 hours availability of services. Services are

always available in principle but in case of failure/issue, we can guarantee quick

come back to normal situation only during office hours.

(Sweden)

View services

Conformance

27

The display of INSPIRE layers gives bad rendering (poor INSPIRE legends); it is

almost meaningless for some themes (AD, GN). Users prefer viewing

cartographic products, traditional maps, at least as background.

(Sweden)

The display of INSPIRE layers gives bad rendering (poor INSPIRE legends); it is

almost meaningless for some themes (AD, GN). Users prefer viewing

cartographic products, traditional maps, at least as background.

(Sweden)

Display of vector data is more flexible and may adapt to various use cases but

this requires additional efforts (let users combine layers, improve legends, …).

(Germany)

View services

Use

28

• Do you provide download of predefined data sets or direct

access through, for example, WFS?

– all : predefined data sets

– Denmark : WFS in future for harmonised data

or WMTS services, or both?

• NMCAs currently deliver existing data (not yet harmonised)

Download services

Technical aspects

29

• Will you be providing an ATOM feed to satisfy the Download

Service obligations?

Download services

Technical aspects

30

Download services

Technical aspects

• What software (if any) do you use to provide download services?

31

or WMTS services, or both?

Download services

Technical aspects

Download of tiled/ raster / coverage data raises issues.Download of tiled/ raster / coverage data raises issues.

32

Transformation services are generally considered as useless by NMCAs:

-Coordinate transformation: already offered by WFS

-Schema transformation: requires too much knowledge from users

Transformation services are generally considered as useless by NMCAs:

-Coordinate transformation: already offered by WFS

-Schema transformation: requires too much knowledge from users

Transformation services may be useful in case of very specific national CRS or to

be offered as help to “small” data providers.

Transformation services may be useful in case of very specific national CRS or to

be offered as help to “small” data providers.

Transformation services

Use

33

Use of INSPIRE services is poorly monitored;

When user feed-back exist , use of INSPIRE services is rather weak

compared to use of other existing services.

Use of INSPIRE services is poorly monitored;

When user feed-back exist , use of INSPIRE services is rather weak

compared to use of other existing services.

INSPIRE services might be more widely used once data is harmonised.INSPIRE services might be more widely used once data is harmonised.

Network services

Use

34

Data interoperability

35

Some potential short-term users :

-X-border users

-Research projects

-Environmental agencies (for reporting to EEA)

Few users and use cases are expected at short term for INSPIRE data.

“We are not aware of any use case. We do it because of legal obligation “ BKG

Expected benefits

Users

Real benefit will come in long term with annex III data

annex III data available and interoperable => more applications => more use of

annexes I and II data

INSPIRE specifications are best practice and may be integrated / taken into account

into data producers internal specifications.

36

INSPIRE data models are complex and we are unsure that GIS tools may

handle INSPIRE data (IGN France) .

Expected benefits

Users

We are conducting a survey among GIS software providers:

-to get better understanding of current status

-to encourage GIS providers to take INSPIRE rules into account

We are conducting a survey among GIS software providers:

-to get better understanding of current status

-to encourage GIS providers to take INSPIRE rules into account

37

Responsibility

•• What to do when several data producers for same What to do when several data producers for same

theme?theme?

•• Definition of responsibilities is at different stages in Definition of responsibilities is at different stages in

Member StatesMember States

–– DoneDone

–– In progressIn progress

–– Not yet defined Not yet defined

38

Responsibility

•• 3 3 ““responsibility modelsresponsibility models””

–– Single: one producer for a themeSingle: one producer for a theme

–– Node: several producers with coordinationNode: several producers with coordination

–– Multiple: whoever has, publishesMultiple: whoever has, publishes

•• Coordination may be done by various ways: Coordination may be done by various ways:

–– Coordinator, leading actor Coordinator, leading actor

–– Working groupsWorking groups

–– Agreements between data producersAgreements between data producers

39

Technical issues may remain, when sharing responsibilities between data producers:

-by feature types (Netherlands): no user friendly (no association, various LoD,

several services)

-by geometry / semantics (Norway)

Responsibility

“Main benefit of INSPIRE interoperability is to force various data producers to sit

together, to discuss and to find agreement.”

INSPIRE improves organisation of geo-information at national level.

Definition of national standards (common data models) based on INSPIRE looks

good solution.

Definition of national standards (common data models) based on INSPIRE looks

good solution.

40

Ambition

•• What to do when a data producer has more data What to do when a data producer has more data

than required by INSPIRE?than required by INSPIRE?

•• It is allowed to extend INSPIRE models It is allowed to extend INSPIRE models

•• Option 1 Option 1

–– Do not extend INSPIRE modelDo not extend INSPIRE model

–– Keep existing productsKeep existing products

–– Have INSPIRE in complement of existing dataHave INSPIRE in complement of existing data

•• Option 2Option 2

–– Extend INSPIRE model Extend INSPIRE model

–– Publish INSPIRE data in replacement of existing dataPublish INSPIRE data in replacement of existing data

41

There will be interoperable INSPIRE data before the legal dead-line

(Poland, Netherlands…)

Ambition

Keep it simple, apply only INSPIRE requirements (challenging enough).

Expect some user feed-back before being more ambitious.

Let’s INSPIRE prove itself

Keep it simple, apply only INSPIRE requirements (challenging enough).

Expect some user feed-back before being more ambitious.

Let’s INSPIRE prove itself

There is limited ambition for short term. INSPIRE will be in complement of existing

products, very few extensions are expected.

42

Priorities

Priorities are generally not driven by expected benefits / user

requirements.

Priorities are mainly driven by:-INSPIRE road map

(annex I and/or new products)

-Feasibility

(AU, CP, GN, AD, PS before HY, TN)

Priorities are generally not driven by expected benefits / user

requirements.

Priorities are mainly driven by:-INSPIRE road map

(annex I and/or new products)

-Feasibility

(AU, CP, GN, AD, PS before HY, TN)

43


•• Step 1 : Identification of the source data setsStep 1 : Identification of the source data sets

•• The list of data sets already declared for INSPIRE The list of data sets already declared for INSPIRE

(metadata) may have to be reviewed for (metadata) may have to be reviewed for

interoperabilityinteroperability

–– Distinction between:Distinction between:

•• Production databaseProduction database

•• External productsExternal products

–– Case of similar data sets Case of similar data sets

•• Reference data set => to be made interoperableReference data set => to be made interoperable

•• Copies Copies

44


•• Step 2 : matching between source data sets and Step 2 : matching between source data sets and

INSPIRE modelINSPIRE model

45


•• Step 2 : matching between source data sets and Step 2 : matching between source data sets and

INSPIRE modelINSPIRE model

•• Matching tables Matching tables –– Derive automatically matching table from INSPIRE data Derive automatically matching table from INSPIRE data

modelmodel•• Avoid fastidious manual workAvoid fastidious manual work

•• Avoid interpretation errorsAvoid interpretation errors

–– No perfect model of matching tableNo perfect model of matching table•• High level (features, attributes) : missing correspondencesHigh level (features, attributes) : missing correspondences

•• Detailed (data types, code lists) : difficult to handleDetailed (data types, code lists) : difficult to handle

–– Often an iterative processOften an iterative process•• Matching table more detailedMatching table more detailed

•• Possibly new data sourcesPossibly new data sources

46

Methodology

Involve several persons to define the matching between existing data and INSPIRE

-Knowledge of source data

-Knowledge of INSPIRE theme specification

-Knowledge of transformation process, transformation tool.

Involve several persons to define the matching between existing data and INSPIRE

-Knowledge of source data

-Knowledge of INSPIRE theme specification

-Knowledge of transformation process, transformation tool.

INSPIRE specifications are complex and require a lot of knowledge.

47


•• Step 3: analyse, decideStep 3: analyse, decide

•• Missing data Missing data –– Generally not an issue as most concepts in INSPIRE are Generally not an issue as most concepts in INSPIRE are

““voidablevoidable”” (to be provided if available)(to be provided if available)

–– But a recommendation for new data captureBut a recommendation for new data capture

•• Additional data Additional data –– Keep it out of INSPIREKeep it out of INSPIRE

–– Integrated it in INSPIRE => extend the INSPIRE modelIntegrated it in INSPIRE => extend the INSPIRE model

•• Common data with INSPIRECommon data with INSPIRE

–– The way to make it interoperable is let to data producerThe way to make it interoperable is let to data producer

•• Data transformation => shortData transformation => short--term solutionterm solution

•• Change internal model => longChange internal model => long--term solution term solution

48


•• Step 3: analyse, decideStep 3: analyse, decide

•• How to deliver INSPIRE dataHow to deliver INSPIRE data–– CRS : INSPIRE gives the choice between several CRSCRS : INSPIRE gives the choice between several CRS

•• Geocentric coordinatesGeocentric coordinates

•• Geographic coordinatesGeographic coordinates

•• Projected coordinates Projected coordinates

–– Format : Format :

•• INSPIRE formatsINSPIRE formats

–– GML for vector data GML for vector data

–– GML coverage, TIF, JPEG 2000 for gridded data GML coverage, TIF, JPEG 2000 for gridded data

•• Other (shapefile?)Other (shapefile?)

–– MediaMedia•• Direct accessDirect access

•• Predefined data setsPredefined data sets

49


•• Step 4: choose or define the target schemaStep 4: choose or define the target schema

•• The target schema may be :The target schema may be :

–– The INSPIRE schema (AU, GN, CP, AD, The INSPIRE schema (AU, GN, CP, AD, ……) )

–– One of the INSPIRE schemas One of the INSPIRE schemas

•• Annexes II Annexes II –– III themes offer some flexibilityIII themes offer some flexibility

•• Different application schemas Different application schemas

–– Different aspects (physical waters/ water network for HY or vectDifferent aspects (physical waters/ water network for HY or vector/grid/TIN for EL or or/grid/TIN for EL or

2D/3D for BU)2D/3D for BU)

–– Core / extended models (BU, LC, Core / extended models (BU, LC, …….).)

–– Generic / example models (natural risks / flood)Generic / example models (natural risks / flood)

•• Extensible code lists or code lists only recommendedExtensible code lists or code lists only recommended

–– ProducerProducer--defined extensions defined extensions

50

Recommended method:

-Import INSPIRE application

schema

-To add new properties,

specialize INSPIRE feature

types

-New feature types may also

be added

class Prov iderDefined

Buildings Provider Defined Extension

Buildings2D

BuildingsBase

«featureType»

BuildingsBase::AbstractConstruction

+ inspireId: Identifier

«voidable, l ifeCycleInfo»

+ beginLifespanVersion: DateTime

+ endLifespanVersion: DateTime [0..1]

«voidable»

+ conditionOfConstruction: ConditionOfConstructionValue

+ dateOfConstruction: DateOfEvent [0..1]

+ dateOfDemolition: DateOfEvent [0..1]

+ dateOfRenovation: DateOfEvent [0..1]

+ elevation: Elevation [0..*]

+ externalReference: ExternalReference [0..*]

+ heightAboveGround: HeightAboveGround [0..*]

+ name: GeographicalName [0..*]

«featureType»

BuildingsBase::AbstractBuilding

«voidable»

+ buildingNature: BuildingNatureValue [0..*]

+ currentUse: CurrentUse [0..*]

+ numberOfBuildingUnits: Integer [0..1]

+ numberOfDwellings: Integer [0..1]

+ numberOfFloorsAboveGround: Integer [0..1]

«featureType»

BuildingsBase::

Building

«featureType»

BuildingsBase::

BuildingPart

«featureType»

Buildings2D::Building

+ geometry2D: BuildingGeometry2D

«featureType»

Buildings2D::BuildingPart

+ geometry2D: BuildingGeometry2D [1..*]

Building

+ address: AddressRepresentation [0..*]

+ officialArea: OfficialArea [0..*]

BuildingPart

+ address: AddressRepresentation [0..*]

+ officialArea: OfficialArea [0..*]

+parts

«voidable»0..*

Principles :

•Do not remove any INSPIRE

requirement

•Do not overwrite any

INSPIRE requirement

Extension by data

provider

51


•• Step 4: choose the method and the tools for Step 4: choose the method and the tools for

making data compliant with INSPIREmaking data compliant with INSPIRE

•• In case of data transformation, 2 main In case of data transformation, 2 main

stepssteps

–– Coordinate transformationCoordinate transformation

–– Schema transformationSchema transformation

52

Schema transformationSchema transformation

•• Possible tools Possible tools

–– Commercial toolsCommercial tools••FME possibly with Arc GIS pour INSPIREFME possibly with Arc GIS pour INSPIRE

••Go Publisher (Snowflakes)Go Publisher (Snowflakes)••……..

–– openopen--source toolssource tools••HALE (Humboldt Alignment Editor)HALE (Humboldt Alignment Editor)http:// community.esdihttp:// community.esdi--humboldt.euhumboldt.eu

••Talend StudioTalend Studiohttp:// fr.talend.com/productshttp:// fr.talend.com/products--datadata--integration/talendintegration/talend--openopen--studio.phpstudio.php

••exoWS devloped par le BRGMexoWS devloped par le BRGM

http://sourceforge.net/projects/exows/ http://sourceforge.net/projects/exows/

••GeoConverter devloped Navarra region (Spain) GeoConverter devloped Navarra region (Spain) http://www.geobide.es/productos/index.aspx.http://www.geobide.es/productos/index.aspx.

–– HomeHome--made tools (if developer skills)made tools (if developer skills)

53

•• (at least) 2 main methods: (at least) 2 main methods:

–– option 1option 1

••Make first model changes in a relational database and then move Make first model changes in a relational database and then move to to

GML GML

••The last phase may be ensured by WFS servers (Degree, The last phase may be ensured by WFS servers (Degree,

GeoServer, XtraServer, GeoServer, XtraServer, ……))

••ExamplesExamples

–– Arc GIS for INSPIREArc GIS for INSPIRE

−− Logical structure of annex I themes implemented by ESRI in relaLogical structure of annex I themes implemented by ESRI in relational tional

GeoDataBaseGeoDataBase

−− data producer makes its transformations of data model (e.g. avedata producer makes its transformations of data model (e.g. avec FME)=> c FME)=>

relational INSPIRE modelrelational INSPIRE model

−− the tool makes the format transformations and ensure the WFS flthe tool makes the format transformations and ensure the WFS fluxux

−− Implementation in IGNImplementation in IGN


54

Base de

données

–

structure

IGN

Base de

données –

structure

INSPIRE

PostGre – BD relationnelle

IGN data -

Shapefile

Scripts

SQLGeoServer

User

query

Data in

GML and

in

INSPIRE

schéma

INSPIRE

schema

(GML)

Out-of-line On-line)


* Similar method was used by partners of ESDIN project to offer data

through WFS, using degree instead of GeoServer

55

•• option 2 : make first the format transformation option 2 : make first the format transformation

and then define the transformation rules and then define the transformation rules

–– HALE : Humboldt Alignment EditorHALE : Humboldt Alignment Editor

••source and target schemas: GMLsource and target schemas: GML

•• range of available transformations (rename, select, frerange of available transformations (rename, select, fre--

classify, give default values, classify, give default values,

••Transformations to be defined once Transformations to be defined once

–– CST : Conceptual Schema TransformerCST : Conceptual Schema Transformer

•• makes the predefined transformations on source data makes the predefined transformations on source data

••To be launched on each data set (e.g. each update)To be launched on each data set (e.g. each update)

* Tool from research project* Tool from research project


56

Humbolt

Alignment

Editor

Conceptual

Schema

Transformer

Source

schema

(GML)

Target

Schema

(GML)

Transformation

rules (OML)

source data

(GML) in source

schema

Transformed data

(GML) in target

schema

* HALE may now work with other input formats


57

•• Step 5: make the required transformations Step 5: make the required transformations

•• Step 6 : check compliance to INSPIRE requirements Step 6 : check compliance to INSPIRE requirements

–– Annex A of Technical Guidelines (Abstract Test Suite) gives Annex A of Technical Guidelines (Abstract Test Suite) gives the steps (theory)the steps (theory)

–– The GML schema (.XSD file) may be used to check The GML schema (.XSD file) may be used to check conformance to data modelconformance to data model

–– Other potential tools Other potential tools

•• Schematron : for constraintsSchematron : for constraints

•• RadiusStudio (1spatial) : for rulesRadiusStudio (1spatial) : for rules

•• ??

–– Likely not everything can be checked automaticallyLikely not everything can be checked automatically

–– Political issue : who should checkPolitical issue : who should check


58

Thanks for your attentionThanks for your attention

Any question? Any question?

INSPIRE Technical Implementation

Documents

Transcript of INSPIRE Technical Implementation