Efficient & effective data management for research projects : ILRI's Data Ma...
OZRI_presentation_Nik&Rod
1. 1
Department of Environment & Climate Change NSW
Spatial Capture and
Attribution of Natural
Resource Management
Investment
Nik Henry and Rod Waski
2. 2
Speaker Background
Nik Henry
• Mapping and Surveying
• On ground activities, Land Use and Land
degradation
Rod Waski
• Programming and Design
• Spatial tool and database development
3. 3
Topics for this Presentation
• Organisational Perspective
• System Architecture
• Live Demonstration
• Questions and Answers
4. 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. 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
16. 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. 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. 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. 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. 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. 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
23. 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. 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
28. 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.
30. 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
33. 33
Spatial Feature Attribution
Selected area, line and point features are
tagged with a unique number (LMID)
Three stage hierarchical display of
attribute description.
NSW government agencies recognised a need for a wide suite of natural resource spatial data sets.
On-ground works and land management practices are an important datasets that include;
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 of feral animals
Development of a consistent standardised approach was needed.
Why detailed recording of funded land management treatments?
Provide spatial record of funded works, accurate location and extent of works
Provide accurate information about activities undertaken
Provide linkages to funding sources, targets and proposed outcomes
Map products for contracts, clients and CMA
Provide compliance - were the works completed?
Project monitoring, works evaluation and output reporting.
Long term planning and regional project development
Input to a range of models – groundwater and surface flow
Land Management Database is a customisation of ArcMap for recording on-ground works with linkages to funded projects.
Attributed spatial features are exported as feature classes to a centralised database in Parramatta.
Primary user is the NSW Catchment Management Authority’s whom manage and control NRM investment strategies
Allows reporting (using Crystal Reports) against a range of criteria, that includes management action targets or funded project outputs.
Reporting at district, catchment, State and federal levels, includes agencies or groups that are responsible for natural resource investment.
The application has been developed over six (6) years with the input of key user and stakeholder groups.
Tool developed by Rod Waski (NSW DECC) and Amanda Walmsley (ex NSW government)
Microsoft Visual Basic 6.
Active-X dynamic link library (dll).
High levels of automation achieved with use of the ESRI ArcObjects libraries.
Microsoft Jet Engine libraries to read and write information to the database
High speed Wide Area network servicing over 30 offices, allowing locally developed data to be uploaded to central database.
The application has been developed over six (6) years with the input of key user and stakeholder groups.
Tool developed by Rod Waski (NSW DECC) and Amanda Walmsley (ex NSW government)
Microsoft Visual Basic 6.
Active-X dynamic link library (dll).
High levels of automation achieved with use of the ESRI ArcObjects libraries.
Microsoft Jet Engine libraries to read and write information to the database
High speed Wide Area network servicing over 30 offices, allowing locally developed data to be uploaded to central database.
The application has been developed over six (6) years with the input of key user and stakeholder groups.
Tool developed by Rod Waski (NSW DECC) and Amanda Walmsley (ex NSW government)
Microsoft Visual Basic 6.
Active-X dynamic link library (dll).
High levels of automation achieved with use of the ESRI ArcObjects libraries.
Microsoft Jet Engine libraries to read and write information to the database
High speed Wide Area network servicing over 30 offices, allowing locally developed data to be uploaded to central database.
The application has been developed over six (6) years with the input of key user and stakeholder groups.
Tool developed by Rod Waski (NSW DECC) and Amanda Walmsley (ex NSW government)
Microsoft Visual Basic 6.
Active-X dynamic link library (dll).
High levels of automation achieved with use of the ESRI ArcObjects libraries.
Microsoft Jet Engine libraries to read and write information to the database
High speed Wide Area network servicing over 30 offices, allowing locally developed data to be uploaded to central database.
Database modelled and designed using Visio.
Local ESRI Geo-databases use front-end and back-end solution, providing data and lookup tables.
ESRI Geodatabases that supports a “one-to-many-to-many” relational model with over 40 tables.
Data is spatially recorded as points, lines or areas and stored locally in specifically designed LMD Geodatabases.
The Centralised (EDB) database uses Oracle spatial 10 with SDE 9.X elements.
A series of database keys are checked out with each LMD database, called LMID’s.
These keys are unique across the WAN and each LMD Geodatabase is allocated 1000 LMID’s
The local databases can upload data to the EDB using a customised ArcToolbox append functionality.
Spatial integrity is maintained through this customised append function, which only replaces data within the specific database LMID key range.
Provides a NSW standardised attribution list (1459) compiled within a three stage hierarchy.
Enables customisation for all users, allowing users to limit the attributions available within the three stage hierarchy.
Provides for multi-selected attribution of area, line and point spatial features
Enables up-loading of attributed feature classes to the a centralised database for compilation
Provides instant reporting on all data up-loaded to the central database (EDB)
