Transcript Jérôme Gensel

Workshop 1.4: ESPON Database
ESPON Internal Seminar
29-30 November 2011
Kraków,Poland
Mu
ltiDim
en
sio
na
l
t
lopmen
& Deve
n
ig
s
e
se D
Databa
ESPON M4D Project - LIG (Grenoble Computer Science Lab) Partner
Jérôme Gensel, Benoit Le Rubrus, Anton Telechev, Marlène Villanova-Oliver
Outline
1. ESPON Data Base v1: Status
1. On the way to ESPON Data Base v2
1. First Results
1. Agenda
2
Outline
1. ESPON Data Base v1: Status
1. On the way to ESPON Data Base v2
1. First Results
1. Agenda
3
The ESPON DB Workflow
Filling the metadata
and uploading data

ESPON DB
file repository
ESPON
Projects
INPUT
DATA

Data checking,
correction and
harmonization
ESPON
Database
External
World

Data and metadata
exportation

Data and metadata
search
4
Access to the ESPON DB v1
ESPON Web Site -> Scientific tools
http://www.espon.eu/main/Menu_ScientificTools/ESPON2013Database/
5
Access to the ESPON DB v1
ESPON Web Site -> Scientific tools -> Application
http://database.espon.eu
6
Access to the ESPON Data Sets
7
Access to Regional (NUTS) Data
3 steps
1. Query
2. Select
3. Download
8
Query Regional (NUTS) Data
1. Query
9
Query Regional (NUTS) Data
2. Select
10
Query Regional (NUTS) Data
3.
Download
11
Query Regional (NUTS) Data
3.
Download
12
Access to Other Data
2 steps
1. List all
2. Download one
13
List then Download Local Data
1. List all
14
Download Local Data
2. Download one
15
To Sum Up
Query, Select,
Then Download
List
Then Download
16
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?
17
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
18
Outline
1. ESPON Data Base v1: Status
1. On the way to ESPON Data Base v2
1. First Results
1. Agenda
19
Three (Main) Requirements
1. INSPIRE Compliance
2. Integration of New Geographical Objects
3. User Friendliness
20
Three (Main) Requirements
1. INSPIRE Compliance
2. Integration of New Geographical Objects
3. User Friendliness
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
structures for data providers
data/metadata
• 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 Specifications
The 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
Example: the Indicator Identification Element
V1
28
Example: the Indicator Identification Element
V1
V2
29
Specifications Metadata v2
The Metadata v2 Specifications
Reference Document:
http://database.espon.eu/metaspecif
(on-line in December 2011)
30
Metadata v2 Excel File
Guidelines/examples: please consult the Chapter 3
of the “Metadata v2 Specifications”
31
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
32
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
33
Three (Main) Requirements
1. INSPIRE Compliance
2. Integration of New Geographical Objects
3. User Friendliness
34
ESPON Data Base Schema
Needs 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…)
35
Three (Main) Requirements
1. INSPIRE Compliance
2. Integration of New Geographical Objects
3. User Friendliness
36
Research Criteria Usefulness
Results of ESPON Database Survey – March 2011
by publication date
by NUTS version
by project
by study area
by NUTS level
by covered period
by theme
0%
10%
No opinion
20%
30%
Not used
40%
Useless
50%
60%
Moderately useful
70%
80%
90%
100%
Very useful
37
Query Interface v2 (Prototype)
What?
Where?
When?
38
The Spatial View
Where?
39
Where? At European Scale
40
Where? At Urban Scale
41
Where? At Global Scale
42
The Thematic View
What?
43
Search by Indicator Name
44
Search by Theme
45
Indicators of the Selected Theme
46
The Temporal View
When?
47
Temporal Selector
48
Outline
1. ESPON Data Base v1: Status
1. On the way to ESPON Data Base v2
1. First Results
1. Agenda
49
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
50
Interface Updates (Dec. 2011)
Overview of indicators
51
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
52
Outline
1. ESPON Data Base v1: Status
1. On the way to ESPON Data Base v2
1. First Results
1. Agenda
53
Agenda
December 2011:
• Interface Updates: overview of indicators,
selection criteria…
Spring 2012:
• Draft Metadata Editor v2
June 2012:
• Draft Query Interface v2 (for NUTS
geographical objects)
54
Thanks from the M4D Partners
Mu
ltiDim
en
sio
na
l
pment
Develo
&
n
g
i
se Des
Databa
55
Thanks from the M4D Partners
Mu
ltiDim
en
sio
na
l
ent
velopm
e
D
&
ign
se Des
Databa
56
UJF LIG STeamer M4D Staff
Jérôme Gensel ([email protected])
Coordination
Benoit Le Rubrus ([email protected])
Logistics Management and Development
Anton Telechev ([email protected])
Development
Marlène Villanova-Oliver ([email protected])
DB and Interface Design and Financial Management
http://steamer.imag.fr
57