Transcript Cadastral Geo-DBMS research

INSPIRE data specification
– focus on cadastre
INSPIRE-werksessie voor bronhouders Bijlage I , 15 januari 2008, Amersfoort, The Netherlands
Peter van Oosterom
July 17, 2015
1
GIS
Vermelding
technology
onderdeel organisatie
Overview
1. INSPIRE data specification
2. INSPIRE cadastral parcels
3. Discussion points
July 17, 2015
2
Harmonizing geoinformation in Europe
• Concerns about 34 different types of data sets
• 27 different countries with 22 languages (and more
influence; e.g. Iceland, Norway and Switzerland are
also involved)
• Agreement on content during exchange, considering
consistency (within, but also) between:
• Themes
• Scales (levels of detail)
• Borders
July 17, 2015
3
Themes (annex I and II)
Annex I:
•Coordinate reference systems
•Geographical grid systems
•Geographical names
•Administrative units
•Addresses
•Cadastral parcels
•Transport networks (water,..)
•Hydrography
•Protected sites
July 17, 2015
Annex II:
•Elevation
•Land cover
•Orthoimagery
•Geology (aquifiers,..)
4
Themes (annex III)
•Statistical units
•Buildings
•Soil
•Land use
•Human health and safety
•Utility and Government services
(water supply, sewage,..)
•Environmental monitoring facilities
•Production and industrial facilities
(water abstraction,..)
•Agricultural and aquaculture
facilities
•Population distribution –
demography
July 17, 2015
•Area management/restriction/
regulation zones & reporting units
(areas around drinking water,..)
•Natural risk zones
•Atmospheric conditions
•Meteorological geographical features
•Oceanographic geographical features
•Sea regions
•Bio-geographical regions
•Habitats and biotopes
•Species distribution
•Energy resources
•Mineral resources
5
INSPIRE components (drafting teams)
metadata*
* technical: under JRC responsibility
** legal/procedural: under Eurostat
data specification*
responsibility
network services*
access and rights of use for
Community institutions and bodies**
• monitoring and reporting mechanisms**
•
•
•
•
INSPIRE is a Framework Directive
Detailed technical provisions for the issues above will be laid
down in Implementing Rules, Once adopted, Implementing
Rules become European legislative acts and national law in
27 Member States and in some EFTA countries
July 17, 2015
6
Time table metadata and data
in years after 15 may 2007
Implementing
rules
metadata
Metadata
(+after
rules)
Implementing
rules
data
New
data
(+after
rules)
Annex I
1
2008
(+2 =) 3
2010
2
2009
(+2 =) 4 (+7 =) 9
2011
2016
Annex II
1
2008
(+2 =) 3
2010
5
2012
(+2 =) 7 (+7 =) 12
2014
2019
Annex III
1
2008
(+5 =) 6
2013
5
2012
(+2 =) 7 (+7 =) 12
2014
2019
July 17, 2015
Existing
data
(+after
rules)
7
Data specifications, results until today
Deliverable
Status
D 2.3: Scope and Definition of Annex I/II/III Themes
based on INSPIRE position papers, Selected reference materials
submitted by the SDICs and LMOs
Version 3.0
D 2.5: Generic Conceptual Model
based on ISO 19101, 19103, 19107, 19108, 19109, 19110,
19111, 19112, 19115, 19123, 19126, 19131, 19136, 19139,
ISO/IEC 19501, OGC 06-103r3
Version 3.1
D 2.6: Methodologies for data specifications
based on Methodology developed by the RISE project
Selected reference materials submitted by the SDICs and LMOs
Version 3.0
D 2.7: Implementing rules for exchange of spatial data
based on ISO 19118, 19136, 19139
INSPIRE Generic Conceptual Model
Version 3.0
July 17, 2015
not yet theme specific data specification
8
Data Specifications - Approach
Annex I
Annex II
Mineral Resources
…
Energy Resources
Buildings
Statistical Units
…
Geology
Orthoimagery
Elevation
…
Protected Sites
Geographical Grids
Coordinate Reference Systems
Implementing Rules comprising data (product) specifications for 34 themes
Annex III
Conceptual Framework
D2.3
Definition of Annex
Themes & Scope
July 17, 2015
D2.6
D2.5
Methodology for
Generic Conceptual Model
Specification Development
9
D2.7
Guidelines for Encoding
General principles
INSPIRE lays down general rules to establish an infrastructure for spatial
information in Europe
- for the purposes of Community environmental policies and
- policies or activities which may have an impact on the environment
INSPIRE must be based on existing data
Harmonisation in INSPIRE must be done based on user requirements:
- pan-european use cases
- cross-border use cases
- linked with environment
Harmonisation has to be feasible and cost-benefits have to be analysed.
July 17, 2015
10
Overview
1. INSPIRE data specification
2. INSPIRE cadastral parcels
3. Discussion points
July 17, 2015
11
Stakeholders’ participation
Data specifications are developed by Thematic Working
Groups consisting of domain experts proposed by the
stakeholders (SDIC/LMO) and a facilitator and editor
nominated my the Commission
8 Thematic Working Groups on Annex I data
July 17, 2015
12
The context
1. Identification of main stakeholders:
• PCC
• EuroGeographics Expert Group on Cadastre
• FIG
• UN WPLA
• EURODIN (eContent + project)
2. Identification of relevant standards : LADM a new work
item proposal to ISO/TC 211 (by FIG)
3. Use a classification based on the one provided by WG-CPI
survey
• Land market
- Agriculture
• Environment
- Spatial planning
• Infrastructures
- Public administration
• Public safety
- Socio-economic analysis
July 17, 2015
13
Definition of cadastral parcel
• In the INSPIRE Directive:
• “areas defined by cadastral registers or equivalent”
• not very explicit (specially for MS having sub-parcels or
“over-parcels”)
• TWG CP explanation
• single part of earth surface with homogeneous rights
• 5 Core elements (WG-CPI): Geometry, Surface (area/size),
Identifier, Georeferencement, Temporal information, and
many optional ones…
July 17, 2015
14
D2.6 Methodology for the
development of data specifications
Use
Use Case
Case
Development
Development
Requirements
Requirements
As-is analysis
Gap analysis
July 17, 2015
Requirements
Requirements
and
Feature
Types
and Sp.Object
Feature Types
Types
Identification
Identification
Data Data
Product
Specification
App
App Schema
Schema
Development
Development
Implementation
Implementation,,
testing
testing and
and
validation
validation
validation
(using WFS)
validation
Step-wise methodology
Guideline for the
INSPIRE
Thematic Working Groups
(TWGs)
15
The first three steps…
• As-is analysis
• General overview (from WG-CPI survey in 2005)
• More detailed information on 11 countries
• Requirements
• INSPIRE (D2.5)
• Available use cases/check-lists
• TWG CP members expertis
• Gap analysis/first proposals
• Discussion papers
• Discussion during TWG CP meetings
July 17, 2015
16
Content Data Product Specification
ISO 19131 based
1
2
3
4
5
6
7
Scope (of the Document)
Overview
Specification scopes
Data product
identification
Data content and
structure
Reference systems
Data quality
July 17, 2015
8
9
10
11
12
Metadata
Delivery
Data Capture (optional)
Portrayal
Additional information
(optional)
Annex A (normative) Abstract
Test Suite
17
class CadastralParcels
+upperLevelUnit
«featureType»
CadastralParcel
«voidable»
0..1
CadastralIndexSet
+
geometry: GM_Surface
+
geometry: GM_Surface
+
inspireId: Identifier
+
inspireId: Identifier
+
nationalCadastralReference: CharacterString
+
nationalCadastalIndexSetReference: CharacterString
+
nationalCalculatedArea: Area
+
label: CharacterString
+
label: CharacterString
«voidable»
«voidable»
+
name: GeographicalName [0..*]
+
referencePoint: GM_Point [0..1]
+
level: CadastralIndexSetLevel
+lowerLevelUnit
+
originalMapScaleDenominator: Integer [0..1]
+parcel
+indexSet
«voidable» 0..*
estimatedAccuracy: Length [0..1]
«voidable»
levelName: LocalisedCharacterString [1..*]
+
+
referencePoint: GM_Point [0..1]
+
topology: TP_Face [0..1]
«voidable»
0..*
+
+
originalMapScaleDenominator: Integer [0..1]
+
estimatedAccuracy: Length [0..1]
«lifeCycleInfo, voidable»
0..1
+
beginLifespanVersion: DateTime
«lifeCycleInfo, voidable»
+
endLifespanVersion: DateTime [0..1]
+
beginLifespanVersion: DateTime
+
endLifespanVersion: DateTime [0..1]
constraints
{nationalAreaUoM}
constraints
{estimatedAccuracyUoM}
{indexLevelHierarchy}
{withTopology}
{estimatedAccuracyUoM}
{EndLifeSpanVersion}
{EndLifeSpanVersion}
+parcel
1..2
«voidable»
+boundary
0..*
«voidable»
«featureType»
CadastralBoundary
+
geometry: GM_Curve
+
inspireId: Identifier
+
estimatedAccuracy: Length
«voidable»
+
2nd-order = 2
«lifeCycleInfo, voidable»
+
beginLifespanVersion: DateTime
+
endLifespanVersion: DateTime [0..1]
July 17, 2015
constraints
{withTopology}
{EndLifeSpanVersion}
«enumeration»
CadastralIndexSetLev el
1st-order = 1
topology: TP_Edge [0..1]
{estimatedAccuracyUoM}
Clause 5, data content
and structure
(UML diagram,
DPS v2.0)
3rd-order = 3
18
class CadastralParcels
CadastralParcel
+
geometry: GM_Surface
+
inspireId: Identifier
+
nationalCadastralReference: CharacterString
+
nationalCalculatedArea: Area
+
label: CharacterString
«voidable»
+
referencePoint: GM_Point [0..1]
+
originalMapScaleDenominator: Integer [0..1]
+parcel
+index
+
estimatedAccuracy: Length [0..1]
«voida
+
topology: TP_Face [0..1]
«voidable»
0..*
«lifeCycleInfo, voidable»
+
beginLifespanVersion: DateTime
+
endLifespanVersion: DateTime [0..1]
constraints
{nationalAreaUoM}
{estimatedAccuracyUoM}
{withTopology}
July 17, 2015
19
{EndLifeSpanVersion}
+parcel
«voidable»
• Not visible: optional
association with
administrative unit
(to which the
parcel belongs)
1..2
+upperLevelUnit
«featureType»
«voidable»
0..1
CadastralIndexSet
+
geometry: GM_Surface
+
inspireId: Identifier
+
nationalCadastalIndexSetReference: CharacterString
+
label: CharacterString
«voidable»
+indexSet
«voidable»
0..1
+
name: GeographicalName [0..*]
+
level: CadastralIndexSetLevel
+lowerLevelUnit
+
levelName: LocalisedCharacterString [1..*]
«voidable» 0..*
+
referencePoint: GM_Point [0..1]
+
originalMapScaleDenominator: Integer [0..1]
+
estimatedAccuracy: Length [0..1]
«lifeCycleInfo, voidable»
+
beginLifespanVersion: DateTime
+
endLifespanVersion: DateTime [0..1]
constraints
{indexLevelHierarchy}
{estimatedAccuracyUoM}
{EndLifeSpanVersion}
July 17, 2015
20
«voidable»
+boundary
0..*
«voidable»
«featureType»
CadastralBoundary
+
geometry: GM_Curve
+
inspireId: Identifier
+
estimatedAccuracy: Length
«voidable»
+
topology: TP_Edge [0..1]
«lifeCycleInfo, voidable»
+
beginLifespanVersion: DateTime
+
endLifespanVersion: DateTime [0..1]
constraints
{estimatedAccuracyUoM}
{withTopology}
{EndLifeSpanVersion}
July 17, 2015
21
Constraints in the model
• EndLifeSpanVersion
Natural language: If set, the date endLifespanVersion
must be later than beginLifespanVersion.
OCL: inv: self.endLifespanVersion
.isAfter(self.beginLifespanVersion)
• withTopology
Natural language: Attribute topology for cadastral parcel
(TP_Face) is mandatory if topology for cadastral
boundary (TP_Edge) is delivered.
OCL: inv: self.boundary -> notEmpty() and
self.topology -> notEmpty() implies
CadastralBoundary.topology -> notEmpty()
July 17, 2015
22
Some other points
two identifiers: INSPIRE and national
coordinates in ETRS89 on Eurasian plate, else ITRS
recommendation: no gaps & overlaps between parcels
CadastralIndexSet: ‘below’ admin units until municip
rights and owners outside the scope
only linear interpolation (no circular arcs)
portrayal for 2 layers with default (each 2 versions):
• parcel outline black 1 pixel, label Arial 10 black
• index set outline black 2 pixels, label Arial 20 black
• encoding GML 3.2.1 (ISO 19136:2007)
•
•
•
•
•
•
•
July 17, 2015
23
XML/GML schema Cadastral Parcels
July 17, 2015
24
July 17, 2015
25
Roadmap TWG Annex I themes
•
•
•
•
•
•
•
•
•
Kick-off meeting: February 2008
Evaluation of user requirements: June 2008
As-it analysis and gap analysis: August 2008
First draft of data product specification: September 2008
Internal review of first draft (DT DS, CT, EIONET):
October 2008
Second draft of data product specification: November
2008
Review by SDIC/LMO: January 2009
Testing, revised DPS: March 2009
Submission to the INSPIRE Committee: May 2009
July 17, 2015
26
Overview
1. INSPIRE data specification
2. INSPIRE cadastral parcels
3. Discussion points
July 17, 2015
27
Attention points during testing
• ETRS89 coordinate transformation (from RD source):
• Accuracy
• Data valid after conversion; e.g. no intersections
• be careful with arcs  convert to straight lines
• estimatedAccuracy: at parcel, boundary, index set?
• GM_Surface/polygon obligatory for parcel (+index set)
• GM_Curve/polyline for boundary optional
• if boundary provides then topology attributes: TP_
• which area (surface size): compute, or use LKI, AKR?
• label is obligatory (last part of parcel number?)
• referencePoint must be within parcel (label place?)
July 17, 2015
28
Future attention points
•
•
•
•
•
•
3D Parcels needed?
all relevant attributes present?
parcels by topology only (no polygon)?
include products in WFS and WMS (portrayal) services
efficient conversion from LKI (coordinates, XML format)
relationship/integration with rights/owners
(INSPIRE ‘external associations’)
July 17, 2015
29
Land Administration Domain Model
ISO 19152 (LADM)
• Model includes:
• Spatial part (geometry, topology)
• Extensible frame for legal/admin part
• Object-orientation  express in UML
• Model Driven Architecture (MDA)
• FIG proposed LADM to ISO TC211, January 2008
• Accepted after voting by P-members
• ISO 19152 – started in Copenhagen/May 2008,
followed by Delft/Sept 2008 and Tsukuba/Dec 2008,
Next meeting Oslo/May 2009
July 17, 2015
30
Core of LADM
class ladm figure 1 core model
VersionedObject
LA_SpatialUnit
VersionedObject
LA_RecordedObj ect
VersionedObject +party
LA_Party
July 17, 2015
0..1
+rrr
VersionedObject +rrr
LA_RRR
1..*
0..*
0..*
+object
1
0..*
31
July 17, 2015
32
July 17, 2015
33
Development of LADM based version
of the INSPIRE cadastral parcels
•
•
•
•
Selection of relevant classes
Based on inheritance
Add attributes
Add constraints (to refine meaning)
July 17, 2015
34
LA_Spati al Uni tSet
LA_Spati al Uni t
+0..*
«FeatureT ype»
/deri ved LADM
CadastralParcel
«FeatureT ype»
CadastralIndexSet
0..1
geometry: GM_Surface
+
geometry: GM_Surface
+
i nspi reId: Identi fi er
+
i nspi reId: Identi fi er
+
nati onal Cadastral Reference: CharacterStri ng
+
nati onal Cadastral IndexSetReference: CharacterStri ng
+
nati onal Cal cul atedArea: Area
+
name: Geographi cal Name [0..*]
+
l abel : CharacterStri ng
+
l evel : Cadastral IndexSetLevel
+
ori gi nal MapScal eDenomi nator: Integer [0..1]
+
l evel Name: Local i sedCharacterStri ng [1..*]
+
esti matedAccuracy: Length [0..1]
+
ori gi nal MapScal eDenomi nator: Integer [0..1]
+
topol ogy: T P_Face [0..1]
+
esti matedAccuracy: Length [0..1]
+
psuID: Oi d [0]
+
oi dT ype: LA_SuOi dT ype [0]
+
type: LA_Spati al Uni tT ype [0]
+
l ayer: Integer [0]
+
0..*
/deri ved
::LA_Spati al Uni tSet
LADM
+
nati onal Cadastral IndexSetReference: Oi d
+
l evel : Integer
nati onal Vol ume: Integer [0]
+
l abel : CharacterStri ng
addressID: ExtAddress [0]
+
name: CharacterStri ng [0..1]
::LA_Spati al Uni t
+
referencePoi nt: GM_Poi nt [0..1]
+
nati onal Cadastral Reference: Oi d
+
oi dT ype: LA_SuOi dT ype [0..1]
+
psuID: Oi d [0..1]
::VersionedObject
+
l abel : CharacterStri ng [0..1]
+
begi nLi fespanVersi on: DateT i me
+
referencePoi nt: GM_Poi nt [0..1]
+
endLi fespanVersi on: DateT i me [0..1]
+
type: LA_Spati al Uni tT ype [0..1]
+
nati onal Cal cul atedArea: Integer [0..1]
+
Vol ume: Integer [0..1]
+
0..1
structure: LA_StructureT ype [0]
+
+
::VersionedObject
+
«enumerati on»
begi nLi fespanVersi on: DateT i me
+
CadastralIndexSetlev el
endLi fespanVersi on: DateT i me [0..1]
1st-order = 1
1..2
2nd-order = 2
/deri ved LADM
3rd-order = 3
0..*
LA_FaceStri ng
«FeatureT ype»
CadastralBoundary
Note:
+
geometry: GM_Curve
T he LADM attri butes i nheri ted by INSPIRE can have a more speci fi c
+
i nspi reId: Identi fi er
data type or cardi nal i ty i n INSPIRE (compared to LADM). T hi s has been
+
esti matedAccuracy: Length
i ncl uded i n the di agram. T hi s i mpl i es that an opti onal LADM attri bute
+
topol ogy: T P_Edge [0..1]
[0..1], mi ght not occur at al l i n INSPIRE as the cardi nal i ty can be set to
+
fsID: Oi d [0]
0; e.g. nati onal Vol ume. T hi s al so i mpl i es that an opti onal LADM
+
l ocati onByT ext: CharacterStri ng [0]
attri bute [0..1], mi ght be an obl i gatory attri bute i n INSPIRE; e.g. l abel .
+
producti onMethod: LI_Li neage [0]
July 17, 2015
35
Conclusion ISO-INSPIRE
•
•
•
•
•
Standardization is a condition for realizing the GII
Domain models (themes) contain knowledge
INSPIRE is mega-construction
ISO (TC211) is often the foundation
ISO 19152 / LADM and INSPIRE cadastral parcel have
different scope, but the overlap does fit
July 17, 2015
36
The end
(unless you want to know more)
• Questions?
July 17, 2015
37