krakow2010
DESCRIPTION
The ideas about spatial planning metadata profile of Plan4all projectTRANSCRIPT
Co-funded by the Community programmeeContentplus
European Network of BestPractices for Interoperabilityof Spatial Planning Information
WP 3
1. Analysis of requirements given by national legislation
2. Plan4all metadata profile design
WP 3 Metadata profile
Profiles1. Spatial plan metadata
2. Web services metadata
3. Spatial Data Theme metadata (dataset level) - WP4
4. Spatial Data Theme metadata (feature level) - WP4
Use of metadata Discovery (CSW) Documentation (dataset)
Discovery
Evaluation
Use
Spatial plan structure
Map 1Map 1
Textdocument
Textdocument
Map 2Map 2 Map 3Map 3
Textdocument
Textdocument
Textdocument
Textdocument
Spatial Plan Structure
Layer Layer Layer Layer
Profile: ISO 19115 / 19119 subset INSPIRE compliant Some extra queryables
SP metadata available during SP design process Documentation of SP adoption legislative steps
Requirements
SP Metadata componets
Spatial plan metadata (M)Spatial plan metadata (M)
Dataset MetadataDataset
Metadata
Application schema
Application schemaDataset
MetadataDataset
MetadataDataset
MetadataDataset
Metadata
parentIdentifier
softwareDevelopmentFile uri
Plan4all specific
1. SP Level (national / regional / local / sublocal): hierarchyLevelName
2. Organization roles (mapped to ISO codes)
3. Keywords – from Plan4all glossary
4. Application schema – link to external file
5. Text documents – distributionInfo//linkage
6. Multilingual metadata
Steps
Preparation phasePreparation phase In forceIn force
9.
Co
min
g i
nto
fo
rce
11
. E
xp
ira
tio
n
1. W
ork
star
t –
proc
ure
men
t ap
pro
val
10. R
epor
t on
pla
n's
appl
icat
ion
app
rova
l
4. C
once
pt
draf
t –
star
tin
g th
e di
scus
sion
3. S
pec
ifica
tion
- a
ppr
oval
2. S
pec
ifica
tion
– s
tart
ing
the
dis
cuss
ion
6. B
efor
e ap
pro
val -
sta
rtin
g th
e d
iscu
ssio
n
5. I
nst
ruct
ions
for
pre
par
atio
ns -
app
rova
l
7. B
efor
e ap
pro
val-
op
inio
n o
f a
reg
i. off
ice
8.
Be
fore
ap
pro
va
l -
iss
ue
10. R
epor
t on
pla
n's
appl
icat
ion
app
rova
l
Mapping: •lineage/*/processStep (preparation phase, revisions, …)•extent/*/temporalElement (in force) 9 - 11•citation/*/date (publication) - 8
Steps
MS specific
Source
Lineage
Plan 3
Plan 1Plan 2
Feature N
Generalized INSPIRE Theme
Feature level metadataInherited ?Links ?
metadata metadata
metadata
Recommendations for INSPIRE
1. Add status property to each INSPIRE theme ! gmd:MD_ProgressCode ? (planned,completed,obsolete,…) Own mapping? exiting / planned , true / false …
2. Add lineage metadata to each INSPIRE theme !