Post on 15-Apr-2017
1
Department of Environment & Climate Change NSW
Spatial Capture and Attribution of NaturalResource ManagementInvestment
Nik Henry and Rod Waski
2
Speaker Background
Nik Henry Mapping and Surveying On ground activities, Land Use and Land
degradationRod Waski Programming and Design Spatial tool and database development
3
Topics for this Presentation
Organisational Perspective
System Architecture
Live Demonstration
Questions and Answers
4
Organisational Context Manage natural resource investment Develop and manage natural resource
datasets Use these spatial datasets for Planning,
Reporting, Monitoring and Evaluation Currently maintain these important datasets
- Land Use- Salinity Outbreaks- Groundwater Bores- Soil profiles and Soil Landscapes- Land Capability
5
Examples of Natural Resource Investment
Establishment of localised native vegetation Riparian bed stabilisation and bank protection
works Fencing off areas of significant vegetation Location of troughs and tanks for water
supply infrastructure Removal and control of noxious weeds Trapping and control of feral animals
6
Vegetation Establishment with Grazing Activities
7
Native Vegetation Corridor Establishment
8
9
Landholder Cropping Management
10
11
Landholder Saline Site Management Activities
12
Landholder Gazing Management Activities
13
14
Community Involvement with Monitoring
15
Community Involvement with On-ground Activities
16
Spatial Recording of Investment
Spatial record of on-ground works Detailed information about works Map products Data for Compliance processes Project monitoring Data for Long term planning Input to a range of models
17
The Land Management Database
Primary user is the NSW Catchment Management Authority’s
A customisation of ArcMap Provides a consistent standardised
process Features compiled automatically on a
centralised database. Provides instant reporting (using Crystal
Reports) against a range of criteria Links to other natural resource datasets
18
Background Developed over six (6) years The organisation had a significant Arcview
3.3 user base. Recently implemented Oracle spatials and
was beginning to use ArcGIS 8.1 New to ArcObjects development and how
it interacts with our new spatial infrastructure
19
Background - continued Many workshops and data modelling
sessions. Discussions with our DBA’s who were
implementing our Oracle Spatial systems. Preliminary programming was undertaken
in 2003 however the project stalled in 2004 when Amanda left the organisation.
In 2005 further development occurred and it was implemented on ArcGIS 9.0
20
Implementation The programming to export to the Central
database was completed in 2005. Went through our change control
procedure to the production database. We could now easily demonstrate the
benefits of a centralised database for corporate reporting.
Began marketing the LMD to the CMAs and within our organisation.
21
Development Environment
Microsoft Visual Basic 6. Active-X dynamic link library (dll). ESRI ArcObjects libraries. Microsoft Jet Engine libraries High speed Wide Area network
22
EDB
Users operate independently and store data centrally
23
Database Environment Modelled and designed using Visio. Front-end and back-end solution “one-to-many-to-many” relational model. Points, lines or areas stored locally Centralised (EDB) database uses
Oracle spatial 10 with SDE 9.X elements.
24
Database Key Management
Database are checked out with each LMD database
Keys are unique across the WAN
Upload of spatial data using Append function
Spatial integrity maintained locally
25
LMD Feature Classes on EDB
26
Spatial Feature Description Rels
One unique number (LMID) per spatial feature
To many sub-
typesTo many activities
27
28
Application Updates
The system Automatically updates itself across the WAN from the EDB.
One xml file on EDB controls the system versioning and updating functions.
All LMD Geodatabases link to lookup tables stored in an external reference database, no domains.
Allows easy update and management of the reference data for description or attribute list.
29
Updating Functions
30
Features of the LMD Tool
Standardised attribution list (1859) Customisation for all users, limit available
attributions. Detailed attribution of area, line and point
spatial features Up-load of attributed feature data Instant reporting once data up-loaded
31
Simplified General ProcessStart ArcGIS
1.0 CreateDatabase
4.0 ExportFeatures
3.0 AttributeFeatures2.0 Digitise
Features
EDBP
Close ArcGISlmd_template
32
Database Setup and Links
Contract or agreement numbers
33
Spatial Feature Attribution
Selected area, line and point features are tagged with a unique number (LMID)
Three stage hierarchical display of attribute description.
34
Spatial Feature Assessments
35
Reporting Enabled
Financial numbers - WBS element