Kick-off meeting Tuesday, April 18, 2023

Anders ÖstmanImad Abugessaisa

PurposePurpose

• The methodology relates to the data specifications for the themes specified in Annex I-III.

• The main objective is to assure that INSPIRE specifications are balanced in terms of cost (CBC) and solving user needs.

• To make transformation from local data sets into INSPIRE compliant data sets feasible.

• Get feedback and discussion about the methodology.

Annex I testAnnex I test

• GeoTest focuses on transformation test.• The aim is to test how to transform data in local

schemas to data in INSIPRE schemas.

Conceptual level Conceptual level

• UML Class diagram for each THEMETHEME

– Application schema – Cross-theme relationships– Constraints– Feature types– Data types– Enumerations and code lists

class Addresses

Generic Conceptual Model

«featureType»Gazetteer::LocationInstance

+ geographicIdentifier: PT_FreeText+ alternativeGeographicIdentifier: PT_FreeText [0..*]+ geographicExtent: GM_Object+ admin: CI_ResponsibleParty

«lifeCycleInfo»+ dateOfCreation: Date [0..1]

«featureType»AddressComponent

«voidable»+ identifier: Identifier [0..1]+ alternativeIdentifier: CharacterString [0..1]+ status: Status [0..1]+ validFrom: DateTime+ validTo: DateTime [0..1]+ lastChange: DateTime

«voidable, lifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

«featureType»Address

+ identifier: Identifier+ geographicPosition: GM_Point+ geometryOrigin: GeometryOrigin

«voidable»+ status: Status [0..1]+ validFrom: DateTime+ validTo: DateTime [0..1]+ lastChange: DateTime

«voidable, lifeCycleInfo»+ beginLifespanVersion: DateTime+ endLifespanVersion: DateTime [0..1]

constraints{Locator}{ThoroughfareName}{AddressAreaName}{AdminUnitName}{AddressAdminUnit}{AddressComponentParent}{AddressLocator}{AddressCountry}

«featureType»AdminUnitName

+ name: GeographicalName [1..*]+ level: AdministrativeHierarchyLevel

«featureType»AddressAreaName

+ name: GeographicalName [1..*]

«featureType»ThoroughfareName

+ name: GeographicalName [1..*]

«dataType»LocatorDesignator

+ designatorValue: CharacterString+ type: LocatorDesignatorType

«featureType»Locator

+ designator: LocatorDesignator [0..*] {ordered}+ name: LocatorName [0..*] {ordered}+ level: LocatorLevel

«dataType»Base Types::Identifier

+ localId: CharacterString+ namespace: CharacterString

«lifeCycleInfo, voidable»+ versionId: CharacterString [0..1]

«featureType»PostalDescriptor

+ postName: GeographicalName [0..*]+ postCode: CharacterString [0..1]

constraints{PostNameEmpty}{PostCodeEmpty}

«dataType»GeometryOrigin

«voidable»+ base: GeometryBasis+ method: GeometryMethod

«dataType»LocatorName

+ nameValue: GeographicalName [1..*]+ type: LocatorNameType

+child0..*

+parent0..*

+instance 0..1

+gazetteerInstance«voidable» 0..1

+child«voidable»0..*

+parent«voidable»0..*

+address0..*

+component2..*{ordered}

Implementation level Implementation level

• XML encoded schemas for Annex I are offered from INSPIRE one XSD per theme.

• SIS offered application schemas for:– Väg- och järnvägsnät ( only)– Ytvattensystem– Belägenhetsadresser

• Distributed over a multitude of XSD documents.

Cost-benefit considerationsCost-benefit considerationsCBCCBC

During T. testing quantitative information will be collected about:– Efforts needed , e.g. as person-hours per dataset and Initial

investments necessary to implement the data transformation.– How existing tools and “know-how” have been exploited.– Resources needed for maintaining an operational

transformation service.– Time efficiency of the on-the-fly transformation services– Demand for the data being tested.– To what extent INSPIRE specifications can be used in the future

within organisations.– How participation in testing helps stakeholders to identify

corresponding or missing data and the processes necessary for implementation of INSPIRE within the Member State.

Strategy for transformation Strategy for transformation testingtesting

• During transformation test the following are to be tested per theme:– Data content and structure – Delivery– Data quality and metadata – Portrayal– Reference systems (might be needed!)

Testing strategy Testing strategy

• The main strategy in this testing is to use the ETL (extract-transform-load) approach. SW license available.

• In the future, when INSPIRE services are to be implemented new approach might be introduced.

Preliminary desk studyPreliminary desk study

• The objective is to gather some basic information about the data theme being tested. The study includes the following – Preliminary schema matching – Identification of source schema– Metadata survey– Investigate if there is any OGC compliance or services

using the source DS

PDS- stepsPDS- steps

Generation of Source GML Generation of Source GML datadata

• The objective of the extraction process is to identify costly procedures when generating GML data that conforms to the source schema.

• This problem is expected to increase in cases of:– when the source schema is not available– when data are loosely coupled to the source

schema

Steps to Generate GML Steps to Generate GML datadata

• Specify source schema in XML and constraints. • Extract sample data sets.• Convert sample data sets to GML/XML. • Quantification of data inconsistencies.

Generation of GML data .1.Generation of GML data .1.• Specify source schema in XML and geometric constraints.

• In addition to the schemas, some geometric constraints might also need to be specified, if not specified in the schema.

Specify source schema

Schema specified

Convert to XML

Yes

Schema has to be created

No

Generation of GML data .2.Generation of GML data .2.

• Extract sample data sets – Extract sample data sets from the entire source

database– The sample data sets shall be representative for

the quantification of problems that may occur– The extraction should be based on random

sampling

Generation of GML data .3.Generation of GML data .3.

• Convert sample data sets to GML/XML. – In case the extraction in stage 2 is not based on

XML/GML, then– A transformation from the export format to

GML/XML is required.

• Quantification of data inconsistencies– Study the consistency between the source data

and the schema

Transformation to INSPIRE Transformation to INSPIRE GML schemaGML schema

• The objective of the transformation test is to estimate the occurrence of costly procedures in a schema translation process. This is will be performed as1. Schema matching 2. Schema mapping3. Schema transformation

Schema matchingSchema matching

• Based on the preliminary schema matching study, a final matching is established. – Performed manually– Fragment-based Matching – Partial automation use schema matcher.

• Schema-level OR instance-level• Element-level OR structure-level

Schema mappingSchema mapping• The goal is to specify the transformation rules when

transforming from source schema to INSPIRE schema.

• Data transformation tools either from Humboldt experiences or other resources. Or others software license providers

• SDIC/LMO: Safe Software• SDIC/LMO: Snowflake Software (limited to

Oracle engine - GO Loader and GO Publisher• The HUMBOLDT editor (supports formal

description of application schemas) and the main transformation services in a Beta release

Schema transformationSchema transformation

• The goal here is not to do the actual transformation, instead to estimate the occurrence of costly procedure.

• Main issues to be reported to INSPIRE– Can local data be mapped to the INSPIRE schema?– Do existing data cover the content required?– Can local CRS be mapped to target CRS and is there

loss in precision?– What are the technical challenges for

transformations?

Thank you for your Thank you for your participationparticipation