Cultural Heritage Asset Management Plans

Transcription

Cultural Heritage Asset Management Plans
Cultural heritage asset
management plans
(CHAMP) Project
Project data sources,
transformation and submission
Jay Carver- Task Manager
The problem...
• No inventory of cultural heritage on
network
• No data on quantification location or
condition
• Data searches on ad hoc basis
• Data not available from existing single
source
• Related ad hoc costs
• No method of measuring performance
The Solution...
Design a GIS database application to
manage heritage assets within the
HA estate –
Outcome – Cultural Heritage topic in
ENVIS
We can go from this….
To this….
HAGIS/Envis/
Cultural Heritage data
• HA have populated records at national
level
• Data will be provided on HAGIS and
• Area shapefile datasets to MAC’s and
DBFO’s (SP’s) supplied by servicepoint+
• Data updates to HAGIS will be made
quarterly by SP’s – Envis Governance
• Data refreshment between HAGIS & NMR
and HER’s shall be managed by EMT
Data refreshment
• HA EMT to develop data exchange routines with
data providers
• NMR datasets
– EMT will check NMR records for changes every
quarter and incorporate changes to HAGIS controlled
version
• HER datasets
– EMT will check HER records annually for changes
• Service provider
– ID any changes to NMR records or HER records as
and when
– Document changes in quarterly data submission to
HAGIS
Implementation...
the CHAMP process...
Start
Envis
D-base
structure
HAGIS
Dataset
HA supplied data
CHMP
Management
Action
Plan
Desk top review
Condition survey
Review
Analysis of
In SP and external Results
HAGIS dataset - supplied to SP’s
• GIS Mapping Database (that represents the location of all
heritage assets within HA estate and buffer zones)
• Point, poly line and polygon shapefiles
• Attached Database - that records feature and management
information within HAGIS application [and locally in your GIS]
• Other attachments – request original data copies as reference
source
Data sources
• Level 1 – English Heritage maintains
record of all statutorily protected and
registered assets- source: NMR at
Swindon• Level 2 each local authority (County
Council/Municipality/National Park) holds
regional d-base of non-statutory assets
Stage and
OBJECTIVE
Scope and
sources
Key output
Cultural Heritage Asset Management
Plans (CHAMP) – data structure
CHMP Part 1
Inventory
Develop ENVIS
Inventory with
Level 1 and 2 data
Nationwide
Network Areas
1-14
ENVIS CH Inventory
data structure
Level 1
HA supplied
designations:
WHS
SAM
HPG
BATField
HWRECK
Level 1
NMR supplied
designations:
LB's
Level 2
HER supplied
data:
Events
Findspots
Sites
CHMP Part 2
Management Plans
Further develop
ENVIS Inventory
with Level 3 data
Prepare CHMP's
Level 3
TPI data:
Inventory &
Events
Develop for
Network Areas
on rolling basis
Level 3
Network Area
Surveys:
Field survey
Desk study
Aerial Photographs
Lidar
Asset photographs
Protection_Grade
Listed_Grade
Grade_Number
Local_SMR
Short_Desc
Feature_class
Type
Class
Form
Value
Condition
Period
Authority
Creator
Owner
Other_Party
Site_Name
Bibliography
Event_Type
Event_Code
Asset_status
ENVIS EMI
data structure
Impacts
Vulnerability
Priority
EMI records:
Condition
Action
Stage and
OBJECTIVE
Scope and
sources
Key output
CHMP Part 1
Inventory
Develop ENVIS
Inventory with
Level 1 and 2 data
Nationwide
Network Areas
1-14
ENVIS CH Inventory
data structure
Level 1
HA supplied
designations:
WHS
SAM
HPG
BATField
HWRECK
Level 1
NMR supplied
designations:
LB's
Level 2
HER supplied
data:
Events
Findspots
Sites
Protection_Grade
Listed_Grade
Grade_Number
Local_SMR
Short_Desc
Feature_class
Type
Class
CHMP Part 2
Management Plans
Further develop
ENVIS Inventory
with Level 3 data
Prepare CHMP's
Level 3
TPI data:
Inventory &
Events
Develop for
Network Areas
on rolling basis
Level 3
Network Area
Surveys:
Field survey
Desk study
Aerial Photographs
Lidar
Asset photographs
Condition
Period
Authority
Creator
Owner
Other_Party
Site_Name
Bibliography
Event_Type
Event_Code
Asset_status
ENVIS EMI
data structure
Impacts
Vulnerability
Priority
EMI records:
Condition
Action
Management
• Level 1 data – the key assets that need
monitoring and management – legal and
mandatory duty
• Level 2 data – often supporting information
and locally important assets that may need
management
Key SP tasks for managing
CHAMP dataset
• Manage current dataset- provide updates
• Change/ Update/revise attribute data in existing
records– E.g. condition information added, status change,
change to spatial record
• Create new records
– When new ‘event’ carried out – e.g. watching brief..
– When asset moved – new spatial record
– When newly registered asset assigned by authority
(link to EMT data refreshment)
• Should/can records be deleted?
ENVIS CH Inventory
data structure
Protection_Grade
Listed_Grade
Grade_Number
Local_SMR
Short_Desc
Feature_class
Type
Class
Form
Value
Condition
Period
Authority
Creator
Owner
Other_Party
Site_Name
Bibliography
Event_Type
Event_Code
Asset_status
ENVIS EMI
data structure
Impacts
Vulnerability
Priority
EMI records:
Condition
Action
Cultural Heritage Asset Management
Plans (CHAMP) – data structure
IAN/84/07 part 4
Annex A.5.1
Mapping database
•Estate
boundary
•Buffer zone
•Points,
lines and
polygons
Data coverage
• Level 1
– 1km
• Level 2100m
http://www.englishheritage.org.uk/nmr
• Access NMR
Level 1 data for
all England
• Spatial data and
reduced attribute
data
NMR download page
Data transformation process
DATA PROCESS FOR EACH NETWORK AREA/LEVEL 1/LEVEL 2
CREATE SHAPEFILE FOR SEARCH AREA
SUBMIT DATA REQUEST FORM
RECEIVE GIS FILE
SAVE ATTRIBUTE DATA IN EXCEL
MATCH RE-USABLE DATA FIELDS IN MS ACCESS
LOAD REUSABLE ATTRIBUTE DATA INTO MS ACCESS
EDIT EACH RECORD IN MS ACCESS AND ADD MADATORY DATA
EXPORT ATTRIBUTE DATA BACK TO SHAPE FILE
CHECK SPATIAL LOCATION IN GIS MAP VIEW
COMPLETE DATASET SIGN OFF FORM AND SUBMIT TO HA
Key issues - ENVIS
• Data field names
• Controlled values (LUT’s) and external
wordlists
• Controlled field types
• Controlled character lengths
• Controlled GIS file formats and rules
– No Multipoint files
Key issues- transformation of
source data
• GIS record and attribute data mostly separated (PDF
and word files)
• Cut and paste/interpretation needed hence specialist
task
• Inconsistent attribute data – hence specialist task
• Edit field data to match ENVIS character length – hence
specialist task
• Multipoint files common - explode
• ‘Duplicates in Level 2 and Level 1 records’ – delete
• Joining datasets for submission
• Look out for field format change when exporting data
from Access and ArcView
LUT’s
• Look up tables control data values for
several fields
• These are controlled and available from
ATOS
• Only accept controlled versions
• Don’t write your own…
Other controlled content
• Some fields controlled by external word
lists Example:TYPE_field..NMR www.link
• Links to these provided in DMRB guidance
Software tools
MS EXCEL
ARC VIEW
GIS
MS
PROJECT
SOFTWARE
TOOLS
Resources used
to manage data
Option to create
ad hoc forms…..
MS
WORD
MS
ACCESS
MS ACCESS
IMPORT
ADD IN
MS ACCESS
CHANGE
CASE
ADD IN
DBF Manager
Transformation
MS Access Add in
MS Access sign in page
MS Access main data table page
Tools to control data integrity
Completion form/receipt
CHMP LEVEL 1 COMPLETION FORM
Network Area: 4
NMR Ref: 27257
Ref: S004/1
NMR contacts: Graham Deacon (SAM); Nigel Wilkins (LB, RPG, RHB)
Datasets
Intial
Final
Comments
checklist checklist
1. LB_Points
y
y
2. LB_Polygons
y
y
3. SAM
y
y
4. RPG
y
y
5. RHB
y
y
6. WHS
n/a
n/a
7. HW
n/a
n/a
Signed as correct in accordance with EnvIS guidance
Folder name:
Area_4_HA_submitted_18.07.08
Acknowledged:
11 August 2008
Completion date:
18 July 2008
Ref:
Envis_In_024
Submission date:
21 June 2008
From:
J Macdonald
Submitted to:
John Macdonald
Assyst Ref:
R19115
REVISION SCHEDULE
No.
Requested Reason
Date resubmitted
by
1
VJ Bulsara
Reformat numeric fields; combine point and polygon
datasets into two shapefiles
31 October
1
Signed as correct in accordance with EnvIS guidance
Folder name:
CH_polygons_31.10.08
Acknowledged:
ListedBuildingPoints_24.10.08
Completion date:
24 October 2008
30 October 2008
3 November 2008
Ref:
31 October 2008
Envis_In_030
Envis_In_031
Submission date:
(as above)
From:
VJ Bulsara
Submitted to:
VJ Bulsara
Assyst Ref:
19115

Similar documents