Testing of INSPIRE Datasets

Markus Seifert1 Clemens Portele2 Astrid Feichtner1 1Secretariat for SDI in Bavaria 2interactive instruments GmbH

INSPIRE Conference 2013 June 25th, 2013

Testing of INSPIRE Datasets

INSPIRE Datasets

2

Original dataset

Dataset compliant to INSPIRE Data

Specification

Transformation

Testing of INSPIRE Datasets

INSPIRE Compliance

INSPIRE Dataset Metadata-Element „Conformity“ <gmd:dataQualityInfo> (…) <gmd:DQ_ConformanceResult> <gmd:specification> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>”INSPIRE Data Specification on buildings – Guidelines”</gco:CharacterString> </gmd:title> (…) </gmd:CI_Citation> </gmd:specification> (…) <gmd:pass> <gco:Boolean>true</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> (…) </gmd:dataQualityInfo>

3

Source: INSPIRE Metadata TG

Testing of INSPIRE Datasets

INSPIRE Compliance

INSPIRE Monitoring Template

4

(View Services)

http://testsuite.gdi-de.org Testsuite

Testing of INSPIRE Datasets

Background: AdV

• AdV: Working Committee of the Surveying Authorities of the States of the Federal Republic of Germany

• Surveying authorities need automated compliance tests for ◦ new national schema AFIS-ALKIS-ATKIS (AAA, GeoInfoDok 6.0.1)

◦ 12 INSPIRE Data Specifications, e.g. cadastral parcels, buildings, administrative units, orthoimagery

5

Testing of INSPIRE Datasets

Background: ESDIN

• eContentplus Project ESDIN (www.esdin.eu)

• Tools for testing compliance of transformed data sets with extended INSPIRE Data Specifications

• ESDIN Test Framework (ETF)

◦ based on soapUI

◦ available under BSD license

◦ further development within European Location Framework

6

Testing of INSPIRE Datasets

Background: INSPIRE ATS

• Data Specifications contain Abstract Test Suite (ATS) for testing of compliance with ◦ Commission Regulation No. 1089/2010 → Part 1 (normative) ◦ Technical Guidelines Requirements → Part 2 (informative)

• Example:

7

Source: INSPIRE Data Specification Buildings

Testing of INSPIRE Datasets

INSPIRE ATS Conformance Classes

8

Application Schema •Schema element denomination •Value type •Value •Attributes/associations completeness

•Multiplicity* •Abstract spatial object •Constraints •Geometry representation

Reference Systems •Datum •Coordinate reference system

•Temporal reference system •Units of measurement

Data Consistency •Unique identifier persistency •Version consistency •Life cycle time sequence •Update frequency

Metadata •Metadata for interoperability •Metadata encoding schema validation*

•Metadata occurrence* •Metadata consistency*

Information Accessibility •Code list publication •CRS publication •CRS identification •CRS http URI*

Data Delivery •Encoding compliance •Encoding schema validation*

Portrayal •Layer designation •Layer style*

Source: INSPIRE Data Specification Buildings, modified *ATS Part 2

Testing of INSPIRE Datasets

The Pilot Project’s To-Do List

• Define test categories and test criteria (first step: compliance with AAA, GeoInfoDok 6.0.1)

• Implement prototype ◦ web-based, automated testing tool ◦ black box testing ◦ extensible → additional test cases and criteria can be added

• Execute tests using German topographic and cadastral data (GML-files)

• Evaluate feasibility of test criteria and extensibility

• Explore possibilities of integration with “GDI-DE Testsuite” operated by the Coordination Office of the SDI-Germany 9

Testing of INSPIRE Datasets

Test Criteria: Examples

10

Value Test Description All attributes or association roles whose value type is a

code list or enumeration take the values set out therein. Precondition Codelists have to be accessible via a registry.

Test Method / Benchmark

Access code list and verify the existence of the value (the registry returns the expected GML, HTML or SKOS document)

Testing of INSPIRE Datasets

Test Criteria: Examples

11

Geometry Representation Test Description The geometry attribute type of a cadastral parcel object

has to be GM_Surface or GM_MultiSurface. Precondition

Test Method / Benchmark

Inspect the geometry property of each cadastral parcel feature and verify that The geometry attribute type of a cadastral parcel object has to be gml:Surface or gml:MultiSurface.

Testing of INSPIRE Datasets

Prototype Implementation

Note: This is work in progress 12

Testing of INSPIRE Datasets

Test reports in HTML

13

Note: The ELF project will improve the presentation of reports

Testing of INSPIRE Datasets

Limitations

• Test criteria written against any instance data as a test item → Not a general test that the software that generated the

instance document is working correctly

• Some test criteria require access to the whole data set

• Performance limitations when running tests on large instance documents

• Geometry tests use JTS Topology Suite and thus are limited by the capabilities of the software

Testing of INSPIRE Datasets

Conclusions

• Compliance testing for datasets goes beyond GML schema validation

• Automated testing of certain Data Specification requirements is feasible

• INSPIRE-ATS has to considered

• Further development to be discussed with AdV and GDI-DE

• Automated Test tools are needed

15

Testing of INSPIRE Datasets

Questions

16

Contact: Astrid Feichtner Geschäftsstelle Geodateninfrastruktur Bayern (Secretariat for SDI in Bavaria) Munich, Germany astrid.feichtner@lvg.bayern.de