Title: NRDT Phase 3
1Natural ResourceDatabase Template
Joe Gregson Natural Resource GIS Coordinator
Inventory and Monitoring Program Natural Resource
Information Division National Park Service
2NRDT Phase Version 3
- An Improved Model for IM Natural Resource
Databases - Chris Dietrich, Lisa Nelson,and Joe Gregson
Inventory and Monitoring Program
3NRDT A Brief History
- Fall 2001
- NRDT development begins
- Develop Phase 1
- Spring 2002
- Beta test Phase 1
- Develop and release Phase 2
- Fall and Winter 2004
- Functional re-assessment of Phase 2
- Draft Version 3 for review and comment
- Version 3 released
4NRDT What and Why?
- A standard data model with application tools to
facilitate data sharing and integration with
other databases and GIS at parks and networks - NRDT has a history of successful implementation
- Many Phase 2 databases created
- Concept of Location_ID and tabular GIS data
adopted by others
5NRDT Functional Re-assessmentand Database
Revision Project
- Chartered by National Monitoring Coordinator (and
popular demand) - NRDT User Survey (of Phase 2)
- Revision Team
- Recruitment
- RD revised database model and issues
- Review and revise first drafts, test results
- Address major issues from NPS-wide review
- NPS-wide User Review (of Version 3)
- Finish Products, Post Results, Close Out
6Functional Re-assessment
- Phase 2 NRDT User Survey Results
- Primary key structure was not optimal
- Core relationships did not model many of field
sampling protocols very well - Therefore, interface design (forms, queries,
reports, etc.) unnecessarily difficult - Not clear how to integrate with GIS
7NRDT User Survey
- Sent to all Data Managers
- Questions about
- Primary key structure
- Usefulness of Phase 2 database structure
- Need for integration with GIS
- Need for a data transfer/export standard
- Most important vital signs being studied
- Desired tools and functionality for NRDT
- Need for a NRDT mandate from IM
8NRDT Revision Team
- NRDT Revision Team formed to assess issues and
provide redesign expertise - Seven IM data managers (new and senior)
- Three IM program analysts
- Seven networks from across the NPS
- Professional backgrounds
- Computer Information Systems RDBMS
- Geographic Information Systems
- Biology, Ecology, Forestry, Geology
9NRDT Revision Team
- Rose Cook - Sierra Nevada IM Network
- Chris Dietrich - IM National Office (Fort
Collins) - Joe Gregson - IM National Office (Fort Collins)
- Mark Hart - Great Lakes IM Network
- Susan Huse - Northeast Coastal Barrier IM
Network - Lisa Nelson - IM National Office (Fort Collins)
- Velma Potash - Cape Cod N.S. Data Manager
- Gareth Rowell - Heartland IM Network
- Brian Witcher - South Florida/Caribbean IM
Network - Christina Wright - Southeast Coast IM Network
10Revision Team Guiding Principals
- Assume legacy databases need not be changed
- Develop an improved core database model that
better matches the most common field protocols - Define an extendable core that is well-designed
and optimized for ease of interface design - Facilitate connection to GIS applications
- Anticipate possible future need for data roll-up
or integration at park, network, regional levels
Inventory and Monitoring Program
11Version 3 Core
- Optimized for the majority of protocols
- Simplifies core table relationships
- Simplifies interface design
- Provides core common tables and fields necessary
for data integration/roll-up - Formalizes link(s) to GIS
- Backwards compatibility with Phase 2
12Phase 2 Model
Core Tables
Protocol-specific Tables
13Version 3 Core Model
Protocol-specific Tables
Core Tables
Metadata
14Version 3 Extended Core
- Provides tables, fields and relationships to
handle second-tier commonalities - Provides the flexibility needed to model all
field sampling protocols
15Version 3 Extended Model
Protocol-specific Tables
Extended Core Tables
Metadata
16Version 3 Data Sharing
- Primary key issues resolved in a way that
facilitates data sharing and integration - GUIDs (Globally Unique Identifiers) create unique
record keys for shared data - Keys auto-generated in the backend
17Version 3 Integration
- Improved integration with other IM data systems
- Dataset Catalog metadata
- NR-GIS Data Store metadata
- NPSpecies taxonomic lookup tables and species
evidence - GIS integration/spatial data analysis
18Version 3 GIS Functionality
- Issues with storing locations resolved in a way
that facilitates integration with GIS - Formalized GUID link to GIS features
- Conforms to established NPS GIS standards
19Version 3 NRDT Standardizaton
- Extended core for 2nd level commonalities
- NRDT Data Standards Committee (BOFAT)
- Standard fields tables for common protocols
- Facilitates rapid application development
- Promotes service-wide consistency
- IM Recommended Naming Standards for Inventory
and Monitoring Databases - Table/field naming convention promotes
consistency throughout IM databases - Preserves investment in NRDT applications
20Example NRDT Database for Rapid Application
Development
- NER developed a startup V. 3 application
- A conversion SOP to facilitate creation of new
NRDT Version 3 databases with little code editing - Saltmarsh monitoring example
- 2 protocols
- Vegetation
- Nektons
- gt1000 event records
- User SOP for the Saltmarsh database
21NRDT Version 3 Timeline/Closeout
- Formal Version 3 review in Dec. 2004
- Final documentation and initial example completed
in Jan. 2005. - NRDT Version 3 documentation, survey results,
review comments, and initial example now on NRDT
website - Development of field applications and additional
examples can begin anytime - Direct tech. support and database development by
WASO IM will end in March 2005 - NRDT and NR-GIS Data Store training tentatively
set for May 2005
22Related NRDT Events
- NRDT Version 3 examples needed, send to Chris
Dietrich for posting - Get the latest NRDT News and Version 3
athttp//science.nature.nps.gov/im/apps/template
/ - Database object naming convention was sent out
for service-wide review in January 2005, revision
due in February - NRDT Standards (BOFAT) Committee resumed work in
January 2005 - NRDT and GIS standards web application
development will start in April 2005
23National Park ServiceInventory and Monitoring
Program
24Conceptual Database Relationships w/ NR Systems