# Presentation: 641174

## Rocky Mountain NetworkBrent Frakes

## The 7 Deadly Sins (DS) of the I&M Recommended GIS Directory Structure (DS)

- Brent Frakes

## WELCOME TO THE 
LABRYNTH

- WELCOME TO THE
- LABRYNTH

## Goal & Purpose of Presentation

- Renew discussion
- Define shortcomings of current DS
- Present an alternative as starting point

## Status of Current Directory Structure

- On I&M Web site
- Parks and Networks are (?) using this
- Directory structure has taken on a life of its own

- Still Sinning!

## DS #1: Draft Version and Outdated

- Unlike most of I&M products, there has been minimal formal discussion
- Draft has become the de facto standard among some parks and networks

## DS #2: Metadata Separate from Data

## DS#3: Confusing Levels (hierarchy)

- Data
- Images (This is data too!)
- Shared (This has data too!)
- Tools
- Workspace

## DS #4: Does not distinguish between project and official data

- Must not house “project” and “official” data in same location – this only causes confusion and data contamination

## DS#5: Duality of Where Information Could Be Housed

## DS#6: Combines Data with Synthesized & Non-Data Products

## DS#7: Lack of Documentation

- Without clarification, the DS is left up to individual interpretation
- No guidelines that provide vision on expansion or changes through time

## Discussion & Recommendations

- More intuitive: One should be able to find almost anything without a synoptic view of how the data is structured. Role of DS is to be an intuitive maze
- Common standard(s) : structural and procedural guidelines
- Clearly separate “finalized” and “working” project data
- Other national structures – SDSFIE (spatial data standards for facilities, infrastructure, & environment)
- KISS
- Keep all data together – don’t split GIS/non-GIS – Group by theme, not data type
- Address DS

## Example

- BASEDATA (read only at root level and below)
**PARKCODE (????)**
- Air (Description of content...)
- Boundary(Description of content...)
- Census
- DEM
- DRG
- Fire
- Fauna
- Flora
- Geology
- Hydro
- Images
- Landcover
- Recreate
- Soil
- Structure
- Transportation
- Utility
- Wetland
- PROJECTS

- HELP ME!

## North Coast and Cascades NetworkRon Holmes

## Quality Assurance Checks: tools built in to Database, expedites error checking, fixing and reporting.

## List of quality assurance queries, number of records NOT meeting criteria and description

- One click runs many QA queries and shows immediate results summary.

## View and Fix Query Results:  enter Panel type here

- View and Fix Query Results:  enter Panel type here

- View and Fix Tab shows records with this error, allows immediate fix edits.

## Workplan database lists tasks, assignments, status, due dates, milestones and 

- Workplan database lists tasks, assignments, status, due dates, milestones and
- provides for time logging and summary reports

## Select Assignments, add to your list, your short list, assign Lead, Co-lead, Priority, etc.

## Daily work log utility: select from Task list, log time, select Assignment, subtasks

## Days allocated to each task by person – overview of intensive tasks, who’s doing what.

## Sensitive Information

- _Option 1 – The “Location Offset” Approach_ – Apply a random offset (e.g., 1,000 meters to _all_ coordinates.
- Advantages: Surest way to protect information that may be deemed sensitive at a future date.
- Disadvantages: Requires a distinction between actual coordinates and publishable coordinates.

**How do we handle publishing of monitoring plot locations?**

## Option 2 – The “Data Redaction” Approach – Prior to reporting or release, omit only the observations of sensitive taxa at permanent monitoring sites. 

Advantages: Does not obscure the locations of non-sensitive resources 

Disadvantages: Requires detailed screening and review of the data prior to sharing or publication by removing observations of sensitive taxa.

- Advantages: Does not obscure the locations of non-sensitive resources
- Disadvantages: Requires detailed screening and review of the data prior to sharing or publication by removing observations of sensitive taxa.

**How do we handle publishing of monitoring plot locations?**

## Northern Great Plains NetworkJoel Brumm

## Calcium Web Calendar

-  Calcium is an interactive web calendar application
-  The software is installed on a web server,
-    and is accessed through a web browser
-    (including administrative tasks)
-  Users can view, edit, and add events through
-     their web browser.
- Written in Perl and the source code is provided;
-    it produces plain HTML pages

## Slide 27

## Slide 28

## Slide 29

## Brown Bear Software

-  http://www.brownbearsw.com

## Rocky Mountain NetworkDavid Pillmore

## VegMap Fire and Fuels: Lessons Learned

- Patience and Pictures

## 2003 – Application to hold Fire and Fuels Data from ROMO Vegetation Map project

## Ability to bring up the plot photographs from inside the database was an afterthought

## Results in 2003/2004

- Initial excitement
- Then **NOTHING**

## 2006 – Vegetation Map/Fuels Crosswalk

## The photos facilitate comparison between picture based fuel models books and fire experts experience. 

- The photos facilitate comparison between picture based fuel models books and fire experts experience.

## GRSA Veg Map databases will have photos  

## Northern Colorado Plateau NetworkRuss DenBleyker

**Notes:**
Seeps and Springs Database
The NCPN Seeps and Springs database was written to store spring ecosystem data collected by the NCPN and SCPN I&M networks.  It is written in Access 2002 and consists of a front end database of data entry forms, queries, and code and a back end database of data tables.  The Seeps and Springs database requires the following references:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.5 Library
Microsoft DAO 3.6 Object Library
Microsoft Visual Basic for Applications Extensibility 5.3
Microsoft Word 10.0 Object Library
Microsoft ADO ext 2.8 for DDL and Security
The Seeps and Springs database was written to conform closely to NRDT guidelines and therefore uses GUID primary keys throughout.
The Seeps and Springs database will store one jpg site sketch map per site.  These maps are stored as Binary Large Objects and therefore will not consume large amounts of storage in the database.  In order to use the site sketch map feature, you must save ijl15.dll in the Windows\System directory on any computer on which you want to run it.
The Microsoft Word template Spring_Summary_Report.dot must be saved in the same folder as the Seeps and Springs database in order for the Spring Summary report to work.  The Spring Summary report runs very slowly, particularly in a network environment, so be sure to allow it to finish before editing the report.

## Shenandoah National Park Alan Williams

## Shenandoah National Park Alan Williams

## Upper Columbia Basin Network Leona Svancara

## Citizen Science 

***Citizen Science****** ***
***Upper Columbia Basin Network***

- Leona Svancara
- Data Manager / Spatial Ecologist

**Notes:**
The UCBN now has its own VIP program in which high school science students are brought into the network to assist with inventory and monitoring activities, as well as individual park resource management “knowledge-generating” (as opposed to manual labor i.e. weed pulling) projects. This “citizen science” initiative was founded on several key partnerships including those with the Oregon Museum of Science and Industry and the Rocky Mtn. CESU. 

## Oregon Museum of Science and Industry (OMSI) “tent-and-van” based research teams launched in 2004 to assist with inventories.

- OMSI’s Salmon Camp is participating in camas lily protocol development at the Nez Perce NHP Weippe Prairie and Big Hole National Battlefield.

**Notes:**
We began working with OMSI in the John Day Fossil Beds NM, where OMSI has a field school. In 2004 we launched a “tent and van” based high school bat research team to work in JODA, Craters of the Moon NM and P, and Hagerman Fossil Beds NM. We continued this in 2005 with a botany team that assisted several UCBN parks with mapping and survey projects. 

## Students use PDAs running ArcPad linked to GPS units for field data collection.  

- Students use PDAs running ArcPad linked to GPS units for field data collection.

- Custom forms limit data entry errors and facilitate data transfer.

**Notes:**
We have also emphasized stat-of-the-art technology, including PDAs with ArcPad and paired GPS units.

## “Mobile” mapping also includes the use of laptops running ArcView and/or ArcGIS to display, analyze, and report results while in camp.

- “Mobile” mapping also includes the use of laptops running ArcView and/or ArcGIS to display, analyze, and report results while in camp.

- Emphasis is on “start-to-finish” programs that engage students in objectives, data collection, analysis, and reporting.

**Notes:**
We have also emphasized stat-of-the-art technology, including PDAs with ArcPad and paired GPS units.

## Idaho Environmental Education Corp Sponsor Summer 2006

*Idaho Environmental Education Corp Sponsor** Summer 2006*

## Things to consider

-   Good QA/QC procedures
-   Training
-  Ease of Identification
-  Other learning experiences

*Things to consider*

## Pacific Island NetworkGordon Dicus

## PACN Protocol Development Example:

- Coral Reef Monitoring
- (“Benthic Marine Protocol”)

## Benthic Marine - Objectives

- Annually measure abundance (percent cover) of sessile marine benthic macroinvertebrate (corals, soft corals, sponge) and macroalgal (turf algae and large fleshy, articulated or crustose coralline algae) assemblages
- Annually measure recruitment rate of hard corals to uniform artificial surfaces (recruitment plates)
- Annually measure growth rate and survival of selected coral colonies of a common, Pacific species found in all parks
- Annually measure benthic small scale topography or rugosity
- Annually measure the incidence and severity of coral and algal disease and bleaching

## Benthic Marine - Parameters

***Benthic cover*** – capture digital photos along 25-meter transects, then identify substrate at randomly selected points within each photo (Photogrid software)
***Coral recruitment*** – deploy coral recruitment plates for 6 months, then identify and count settled recruits in lab
***Coral growth*** – tag discrete coral colonies along transects for repeat measure of length, width, and height
***Rugosity*** – drape light chain over substrate features along transects to get rugosity index
***Disease incidence*** – record presence or absence of disease-like conditions in each digital photo to derive a measure of disease prevalence for each transect

## Benthic Marine – Sampling Sites

## Benthic Marine – Sampling Design

- Know what you want to monitor, and where.
- Now, how do you decide best way to distribute sampling effort and to standardize measurements?....
*Send out the dive team!*

## Benthic Marine – Sampling Design

- Split panel design used at each park
- 15 permanent transects (sampled every year)
- 15 rotating transects (sampled only once)
- Transects established on hard substrate, along constant depth contour (10-20 m)
- Coral recruitment plates deployed on posts at both ends and midpoint of permanent transects (offset 3 m from transect)
- Randomly selected coral colonies along transect marked with metal tags for repeated growth measurements

## Benthic Marine –Protocol Development Team

- Pacific Island Coral Reef Program ecologists:
- Eric Brown, Kalaupapa National Historical Park
- Dwayne Minton, War in the Pacific NHP
- Peter Craig, National Park of American Samoa
- Larry Basch, Science Advisor (Hawaii Volcanoes NP)
- CESU technicians
- PACN core staff

## Benthic Marine –Protocol Development Strategy

- Statisticians consulted to establish realistic sample sizes that meet expectations on ability to detect change
- Portions of protocol narrative and SOPs assigned to team members
- Deadlines set for dissemination to other team members for review/edits
- Conference calls to discuss progress and schedule new work assignments
- Solicit informal review to improve protocol narrative and SOPs prior to formal WASO review

## Benthic Marine –Backend Database Structure

## Benthic Marine –Database Features

- Import routines for bringing in data from Photogrid (software used to characterize percent cover in transect photos)
- Incorporate data validation processes
- Import repeat data for set number of transect photos (based on second person’s Photogrid interpretation)
- Enter repeat data for set number of recruitment plates (based on second person’s lab analysis)
- Coordination with SFCN is ensuring compatibility with their coral reef monitoring data

## Benthic Marine Protocol Development –Conclusions

- Development of this protocol benefited from having a dedicated group of park staff that is accustomed to working together on coral reef issues
- Regular conference calls helped keep work on schedule, and team members were willing to pitch in when particular assignments fell behind schedule
- Once completed, this protocol and associated SOPs will serve as good examples or templates for other PACN protocol development efforts
- After WASO review, this protocol will be posted to the I&M website for other networks to use

## Rocky Mountain NetworkBrent Frakes

## The DM’s Pre-Emptive Strike:  DM Guidelines for Protocol Development

- <date/time>

**The DM’s Pre-Emptive Strike:  DM Guidelines for Protocol Development**

- Brent Frakes

## Background

- <date/time>

**Background**

- All monitoring protocols require a data management section
- Providing the protocol developers with guidance up front minimizes cleanup at a later date
- Guidance as part of Data Management Plan SOP

## ROMN DMP/IMP  http://www1.nrintra.nps.gov/im/units/romn/

- <date/time>

- ROMN DMP/IMP  http://www1.nrintra.nps.gov/im/units/romn/

## Table of Contents

- <date/time>

**Table of Contents**

- Introduction
- Guidelines
- Documentation Procedures
- Overview of Database Design
- Data Entry, Verification and Editing
- Data Reporting Recommendations
- Sensitivity & Ownership
- Data Archival/Storage Procedures
- Data Workflow
- Roles and Responsibilities
- Roles and Responsibilities
- Change History

## Other Points 

- <date/time>

**Other Points **

- List of _**minimum**_ recommended requirements
- Does not specify exactly how something should be done
- Rather, they indicates what should be explicitly addressed in the protocol document (i.e., focus on end result)

## Center for Urban Ecology Mark Lehman

## Northeast Temperate NetworkFred Dieffenbach

## Dashboards

- And
- Scorecards

**Notes:**
A NEWS, or web feed is a specially formatted file that is interpreted by an application known as an aggregator.  An aggregator can be a stand-alone program (e.g., feed demon), may be web based (e.g., Google Reader) or can be an add-in to another program like Internet Explorer (e.g., Lektora).  The content of the feed is dictated by the originator of the feed and can be updated frequently or not.  A feed is really just one additional way to communicate with an audience, and does not replace a well designed web page, periodic email messages, or other forms of  interaction.  However, publishing a feed offers an advantage over other electronic forms of communication because it does not require the originator to know the identity of the end user, and it does not require the end user to visit the originators web site to search for ‘breaking news.’  For example, when communicating by email, the names of the intended recipients must be known – if not, the message may not reach its destination.  Further, relying on the audience to periodically visit a web site in search of new content is not a viable strategy for organizations that release information on a sporadic basis.  Users quickly learn whether a site is likely to change, and will cease to visit those that are typically “static.”  Creating a feed ‘pushes’ the new content out to the audience and keeps those with an interest in the program informed of recent activities.
Assembling a collection of ‘feeds’ in an aggregator gives the user the ability to create a web-based newspaper that addresses their interests, and keeps the user apprised of up-to-date information.

## “Determine status and trends in selected indicators of the condition of park ecosystems to allow managers to make better-informed decisions. . .” 
“Provide early warning of abnormal conditions of selected resources to help develop effective mitigation measures and reduce costs of management.”
“Provide a means of measuring progress towards performance goals.”

- Goals of Vital Signs Monitoring

*“**Determine status and trends in selected indicators of the condition of park ecosystems to allow managers to make better-informed decisions. . .”*
*“**Provide early warning of abnormal conditions of selected resources to help develop effective mitigation measures and reduce costs of management.”*
*“**Provide a means of measuring progress towards performance**** ****goals.”*

- Excerpted from S. Fancy presentation at Austin, TX 2/8/2005

**Notes:**
The content of this slide was taken from a presentation by Steve Fancy at the Annual I&M meeting in Austin, Texas in 2005.  Of the goals presented by Fancy, I have focused on three that can be directly addressed by a Dashboard Application.

## Policy makers, Non-Scientists

- Scientists,
- Field-level Practitioners

**Science Environment**

**Public Environment**

*Effective *
*communication*

*Sound *
*Science*

- Use Assessment by experts to translate scientific findings for policy and decision-making

- Simple, clear public message

**Notes:**
This is another slide taken from Fancy, 2005 that illustrates how information is distilled into a message that is broadly understood.

## EI Indicator

**Science environment**

**Public environment**

**feedback**

**EI Framework**

**human dimension**

**stressors**

**EI Indicator**

**measures/data**

**statistics**

**models**

**EI Impaired**

**High EI**

**Concerned**

**Notes:**
This slide by Parks Canada, also delivered at the Austin 2005 annual I&M meeting, shows a similar pyramid of information but instead of stating that at the highest level the information is highly aggregated, it shows a meter.  This intuitive way of explaining the status or condition of a measure or index is the premise behind a dashboard.

## Status

- Caution:  May be a developing concern

- Good:  Resources in good condition

_**Status**_

|  |
| --- |
|  |
|  |

- Condition is Improving

- Condition is Unchanged

- Condition is Deteriorating

_**Trend**_

_**Confidence**_

- High

- Some

- Low

- Guess

**Notes:**
This slide, also by Steve Fancy shows a matrix of information about five different resource categories.  The presentation is intuitive, but as the size of the matrix grows it becomes difficult to read.

## But How Do You Do It?

**Notes:**
The concept of a graphical presentation is easier said than done.  In the prior slide, the colors, outlines, and arrows corresponding to the condition, trajectory, and confidence of a particular measure are manually created.  While the presentation may be easier to interpret, the need to create it manually would make this a very laborious task.  finding  an application that is designed to depict summary data graphically seemed necessary.

## Industry has relied on information dashboards for a number of years.
Dashboards integrate information from disparate sources by combining it into a single coherent presentation.
Dashboards can be tailored to the needs of user groups.
Additional details are typically available by “drilling-down” through visible objects.

- Industry has relied on information dashboards for a number of years.
- Dashboards integrate information from disparate sources by combining it into a single coherent presentation.
- Dashboards can be tailored to the needs of user groups.
- Additional details are typically available by “drilling-down” through visible objects.

## Slide 77

**Notes:**
This image shows an insurance company dashboard application.  The numbers are probably contrived, but the different images illustrate how information from disparte locations can be combined into a single user interface.

## Slide 78

**Notes:**
This is an image of a dashboard that presents four different Natural resource oriented categories.  The data are fictitious, but illustrative of how this kind of presentation can be adapted to a natural resource implementation.

## Slide 79

**Notes:**
This image shows the same four categories as the prior slide, but the “View Forest Summary” button has been pressed yielding a “drill-down” graph of the data behind the dial.

## Many large scale applications designed to meet corporate needs with lots of data.
Most applications are quite costly, and are packaged with consulting services.

- Many large scale applications designed to meet corporate needs with lots of data.
- Most applications are quite costly, and are packaged with consulting services.

- Research

**Notes:**
The world of dashboarding is full of high end applications that require specialized knowledge to deploy.

## Crystal Xcelsius

- One of few small scale dashboard applications.
- Scalable and upgradeable.
- Time intensive development.
- Based on MS-Excel data.
- Affordable

**Notes:**
After extensively searching the web we identified a small number of small scale applications that were affordable enough to test the dashboard concept.

## Crystal Xcelsius	-	http://www.xcelsius.com/Land/g_dashboards.html

- Crystal Xcelsius	-	_[http://](http://www.xcelsius.com/Land/g_dashboards.html)__[www.xcelsius.com/Land/g_dashboards.html](http://www.xcelsius.com/Land/g_dashboards.html)_

**Notes:**
This slide shows the Xcelsius application where dashboards are developed.

## Questions?