Workshop 1.4: ESPON Database

ESPON Internal Seminar29-30 November 2011

Kraków,Poland

ESPON M4D Project - LIG (Grenoble Computer Science Lab) Partner Jérôme Gensel, Benoit Le Rubrus, Anton Telechev, Marlène Villanova-Oliver

Outline

2

1. ESPON Data Base v1: Status

1. On the way to ESPON Data Base v2

1. First Results

1. Agenda

Outline

3

1. ESPON Data Base v1: Status

1. On the way to ESPON Data Base v2

1. First Results

1. Agenda

4

The ESPON DB Workflow

ESPON DB file repository

External World

ESPON Projects

INPUTDATA

ESPON Database

Data and metadata search

Filling the metadata and uploading data

Data checking, correction and harmonization

Data and metadata exportation

5

Access to the ESPON DB v1ESPON Web Site -> Scientific tools

http://www.espon.eu/main/Menu_ScientificTools/ESPON2013Database/

ESPON Web Site -> Scientific tools -> Applicationhttp://database.espon.eu

6

Access to the ESPON DB v1

7

Access to the ESPON Data Sets

8

Access to Regional (NUTS) Data

3 steps1. Query2. Select3. Download

9

1. Query

Query Regional (NUTS) Data

10

Query Regional (NUTS) Data

2. Select

11

Query Regional (NUTS) Data

3.Download

12

Query Regional (NUTS) Data

3.Download

13

Access to Other Data

2 steps1. List all2. Download one

14

List then Download Local Data

1. List all

15

Download Local Data

2. Download one

16

To Sum Up

Query, Select,Then Download

ListThen Download

17

Difficult Questions

What is available?

What can I expect as results?

How to get the result of such a question: What is the

population of Kraków region?

18

Some Metadata Shortcomings

Missing Keywords

The 0/1 Theme Problematic

No Precise Codification for Indicators Names

No Precise Indication for Units of Measure

No Full INSPIRE Compliance

Outline

19

1. ESPON Data Base v1: Status

1. On the way to ESPON Data Base v2

1. First Results

1. Agenda

1. INSPIRE Compliance

2. Integration of New Geographical Objects

3. User Friendliness

Three (Main) Requirements

20

1. INSPIRE Compliance

2. Integration of New Geographical Objects

3. User Friendliness

Three (Main) Requirements

21

Why New Metadata Specifications?• When producing a dataset and its metadata, a data

provider is required to follow some rules about the information layout…

• These rules help us to process (parse and syntactically check) these data and metadata files automatically

• To overcome the limitations (incomplete, lack of explicitness, not always used…) of the existing Metadata Specifications

22

Why New Metadata Specifications?• Create a “legal” reference frame for data exchange

• Explain each detail of data/metadata structures for data providers

• Prepare a solid basis for the creation of automatic database integration tools

• Create a public and official interface for data exchange for any interested party

23

Evolution of the Specifications• The core is the same as before, with

several evolutions:• Compatibility with INSPIRE Directive

has been reached• New fields and properties have

been added• to describe more precisely data• to improve automatic checking

24

Evolution of the SpecificationsThe New Specifications cover:

• the rules for data layout• the rules for metadata layout• the rules for statistical units integration (new!)

They hold in a 150 page document…… Available also in HTML

25

New Model: a Brief Introduction• The Abstract Metadata Model is very simple

• It is almost the same as before, except:• Many elements have new fixed names• A new element Spatial Binding

• to ensure compatibility with INSPIRE• to check the spatial references

26

New Model: a Brief Introduction• Each element or property described by

the Specifications is now represented homogeneously

28

Example: the Indicator Identification Element

V 1

29

Example: the Indicator Identification Element

V 1V 2

INSPIR

E

COMPLI

ANT

30

Specifications Metadata v2

The Metadata v2 SpecificationsReference Document:

http://database.espon.eu/metaspecif(on-line in December 2011)

31

Metadata v2 Excel FileGuidelines/examples: please consult the

Chapter 3 of the “Metadata v2 Specifications”

32

Some Metadata Shortcomings

Missing Keywords

The 0/1 Theme Problematic

No Precise Codification for Indicators Names

No Precise Indication for Units of Measure

No Full INSPIRE Compliance

33

New Metadata Specifications…

Consequences• Metadata v1 Editor is now

disabled…• We will upgrade the existing

metadata to comply with the new specifications

From now on…• Please, use our Excel temporary

Solution

…Until June 2012• Metadata v2 Editor Delivery

1. INSPIRE Compliance

2. Integration of New Geographical Objects

3. User Friendliness

Three (Main) Requirements

34

35

ESPON Data Base SchemaNeeds to be Updated

• To store the New Metadata

Needs to be Extended• To store New Geographical Objects

and Nomenclatures• WUTS (World NUTS 0)• Urban Objects (UMZ, FUA…)

1. INSPIRE Compliance

2. Integration of New Geographical Objects

3. User Friendliness

Three (Main) Requirements

36

37

Research Criteria UsefulnessResults of ESPON Database Survey – March 2011

38

Query Interface v2 (Prototype)

Where?

What?

When?

39

The Spatial View

Where?

40

Where? At European Scale

41

Where? At Urban Scale

42

Where? At Global Scale

43

The Thematic View

What?

44

Search by Indicator Name

45

Search by Theme

46

Indicators of the Selected Theme

47

The Temporal View

When?

48

Temporal Selector

Outline

49

1. ESPON Data Base v1: Status

1. On the way to ESPON Data Base v2

1. First Results

1. Agenda

50

Work Done since June 2011

• A Critical Analysis of the ESPON DB v1• Lessons Learned and Experience from

the Phase 1• Remarks of the ESPON CU

• Metadata Specifications

• Nomenclature Integration Specifications

• Database Schema upgrade

51

Interface Updates (Dec. 2011) Overview of indicators

52

Interface Updates (Dec. 2011) Disabled

• Metadata Editor v1… replaced temporarily by an Excel file compliant with the Metadata Specifications reference document… before the delivery of the Metadata Editor v2

• Not so useful search criteria• Selection by geographical objects (only

NUTS)• Selection by publication date

Outline

53

1. ESPON Data Base v1: Status

1. On the way to ESPON Data Base v2

1. First Results

1. Agenda

54

AgendaDecember 2011:

• Interface Updates: overview of indicators, selection criteria…

Spring 2012:

• Draft Metadata Editor v2

June 2012:

• Draft Query Interface v2 (for NUTS geographical objects)

55

Thanks from the M4D Partners

56

Thanks from the M4D Partners

57

Jérôme Gensel (Jerome.Gensel@imag.fr)- Coordination

Benoit Le Rubrus (Benoit.Le-Rubrus@imag.fr)- Logistics Management and Development

Anton Telechev (Anton.Telechev@imag.fr)- Development

Marlène Villanova-Oliver (Marlene.Villanova-oliver@imag.fr)- DB and Interface Design and Financial Management

http://steamer.imag.fr

UJF LIG STeamer M4D Staff