Transcript Slide 1

Geodata for Everyone
- Model-driven development
and an example of INSPIRE
WFS service
Meixia Feng, Danish Geodata Agency
Outline
1. ”Free data” in Denmark – (the basic data programme)
2. Model-driven development for Geodata distribution
3. An example of INSPIRE WFS service
4. Questions and Answers
PAGE 2
Basic Data Programme
Basic Data Programme
Technical harmonization
*Interoperability*
Make all public
basic data FREE
Common public Data
Distributor
*One Point Accessibility*
Warm wash of
all public data
*Data quality*
A national board with
Responsibilities for
Implementation
*Governance*
PAGE 4
Model-driven development of Geodata
UML
PAGE 5
From Modeling To Documentation
Distribution
1
Enterprise Architect
documentation
UML (in Enterprise Architect)
• UML describing
business/production
• “Basic Data” Common model
rules and common metadata
attributers for object classes
• OCL defining constrains
• ISO19… series
• INSPIRE
PAGE 6
From Modeling To GML Schema
Distribution
Enterprise Architect
1
documentation
2
UML (in Enterprise Architect)
ShapeChange
GML schema (XSD)
(GML 2.1.2)
GML schema (XSD)
(GML 3.2.1)
PAGE 7
UML to GML Conversion
Conversion
PAGE 8
ShapeChange Flattener
Flattening
rule-trf-prop-flatten-types
Conversion
Flattening
rule-trf-prop-flatten-codelists
PAGE 9
From Modeling To Database Schema
Distribution
Enterprise Architect
1
documentation
2
UML (in Enterprise Architect)
ShapeChange
3
GML schema (XSD)
(GML 2.1.2)
SQL script (DLL)
GML schema (XSD)
(GML 3.2.1)
Database model (”geodatabank”)
PAGE 10
Database Schemas (DDL)
• Mapping inheritance
structures
each concrete class to its own
table
• Mapping object relationships
primary key and foreign key
• Mapping properties
each property to a column
• Performance tuning
PAGE 11
From Modeling To Database Schema
Distribution
Enterprise Architect
1
documentation
2
UML (in Enterprise Architect)
ShapeChange
3
GML schema (XSD)
(GML 2.1.2)
SQL script (DLL)
GML schema (XSD)
(GML 3.2.1)
4
masterdata
mapping
&
validation
Database model (”geodatabank”)
PAGE 12
From Modeling To Distribution
Distribution
Enterprise Architect
1
documentation
2
UML (in Enterprise Architect)
ShapeChange
GML schema (XSD)
(GML 2.1.2)
3
WFS
SQL script (DLL)
GML schema (XSD)
(GML 3.2.1)
GOPublisherWFS/
GeoServer
4
masterdata
5
GML (on-the-fly)
FME
mapping
&
validation
5
Database model (”geodatabank”)
5
QGIS
(internal users)
Download (GML, SHP, TAB …)
PAGE 13
Distribution as WFS
SIDE 14
Distribution as Download
PAGE 15
INSPIRE
•
Data should be collected only
once
•
Should be easy to find the
available geodata
•
Be easy to collect geodata
from different sources and
share geodata between many
users and uses
•
Be easy to be reused to
implement INSPIRE services
PAGE 16
From National Object To INSPIRE Theme
SIDE 17
From National Dataset To INSPIRE Dataset
Regions
Municipalities
CREATE OR REPLACE FORCE EDITIONABLE VIEW
"DAGI_10M_NOHIST_INS_D1". "ADMINISTRATIVEUNIT"
(
SELECT
objectid,
'dk.au.' || id_lokalid AS gmlid,
id_lokalid, AS inspireid_localid,
registreringfra AS beginlifespanversion,
registreringtil AS endlifespanversion,
geometri AS geometry,
….
FROM
DAGI_10M_NOHIST_L1.regionsinddeling
UNION ALL
SELECT
objectid,
'dk.au.' || id_lokalid AS gmlid,
id_lokalid, AS inspireid_localid,
registreringfra AS beginlifespanversion,
registreringtil AS endlifespanversion,
geometri AS geometry,
…
FROM
DAGI_10M_NOHIST_L1.kommuneinddeling
);
AdministrativeUnit
SIDE 18
Mapping Tool – GO Publisher Desktop
PAGE 19
Mapping National Data to Inspire Schema
• Attributes mapped from national datasets
• InspireId
o
localId = id.lokalId
• Geometry
o
gml:MultiSurface
• Attributes mapped to a constant
• InspireId
o
namespace=http://data.gov.dk/inspire-au
• language=dan
• Attributes mapped to a fixed codeList
• codeList
o
<au:country><gmd:Country codeListValue="DK"
codeList="http://inspire.ec.europa.eu/codeList/CountryCode"/>
</au:country>
• Attributes have no national data to map
• xsi:nil=“true” and nilReason=“Unknown” or “Unpopulated”
PAGE 20
Access to WFS with GIS Client
SIDE 21
SIDE 22
Benefits of Model-driven Development
• Automizes the process from modeling to distribution
• reduces the time taken to implement a new product
• Ensures consistency between the various implementation
schema
• Complies to INSPIRE data model and maximises the re-use
of national spatial data for the INSPIRE services
• a common development process for different basic data
registers
PAGE 23
Thank you for your attention!
PAGE 24