OREGON/WASHINGTON DATA FRAMEWORK IMPLEMENTATION

1. OREGON/WASHINGTON DATA FRAMEWORK IMPLEMENTATION Stanley Frazier, OR/WA State Data Administrator Pamela Keller, Burns District GIS Coordinator

2. Principles & Guidelines • Holistic: Complete view of all spatial data relevant to natural resource management. Provides a “home” for future data. • Cross-Program: One set of data used by many. • Hierarchical: Higher levels provide key properties for lower levels. • Spatial First: Spatial characteristics are key to design. • Core Attributes: Standardize key attributes only, link to program-centric or detailed information. • Definitions: Entities carefully defined for logic and consistency and to avoid duplication. • Simple : Simple data structures and attribute formats for easier maintenance, robustness and transferability. • Master Data: The base component data that is used to create various application views and analysis data.

3. History • 2001-2002 ArcGIS Transition Plan(from Libraries to SDE) included Geodatabase Design; OR/WA Data Plan written that laid out steps that have been followed since. • 2004-2005 Conceptual Model Design. Involvement from OR/WA program leads and data stewards, GIS Coordinators, WO and others; Assistance from ESRI. • 2006 Logical Model Design. Briefings to FUG, ITIB, National CIO Council, Field Managers Forum, Data Steward Interviews. • 2007-present Physical Implementation. Approvals from National Field Committee, SLT (8/2007), ITIB (3/2008).

4. Overview • Higher levels model overall logic and relationships and provide key spatial and attribute properties to lower levels. • Higher levels do not translate into unique ArcGIS datasets- only the lowest level. • Three categories at the highest level: Resources, Activities and Boundaries. • Highest level natural resource management business process can be described as “Activities carried out on or using natural Resources within administrative Boundaries”.

5. UML Charts • Unified Modeling Language charts show: --Groupings of spatial entities into categories and sub-categories. --Attribute inheritance and domains. --Relationships between spatial entities. --Relationships between spatial entities and external tables or databases. • Can be directly converted into a geodatabase.

9. Data Framework Implementation ODF Implementation • Framework provides the data standard umbrella for all OR/WA BLM GIS data. • Final detailed data standards developed according to priorities set by State Leadership Team and GIS user community. • Implemented data standards include creation of the Geodatabase and population with District data.

10. Mini-Model “Mini Model” reduces the 3 charts to one page in order to easily see all the categories and theme groups as a whole and is useful for various project tracking views Green boxes - theme group (abstract entity) White boxes - feature classes (concrete entity) Orange boxes – implemented ODF standards Blue boxes - other standards already in place Yellow boxes – Treatment theme group under development With Treatments Group we will have implemented more than half of the framework.

12. Treatments • Human alterations to the landscape for the purpose of natural resource management including use, enhancement and protection. • A group of themes that need to be designed together. • The scope and importance of this group of themes demands fresh involvement and guidance– stepping back to logical design. • UML Chart created specifically for Treatments.

14. Starting Proposal Seven Polygon Feature Classes representing major treatment types: BURN (prescribed fire) TCUT (cutting of trees, pruning) REVEG (seeding, tree planting) MECH (shrub removal, earth removal or alteration) CHEM (application of pesticides or fertilizer) BIO (biological control using foraging species, predators or parasites) EXCL (exclosure for protection) Completed treatments kept separate from proposed or planned Treatments. Each of the above has a corresponding proposed treatment pair: BURN_P, TCUT_P, REVEG_P, MECH_P, CHEM_P, BIO_P, EXCL_P Within each feature class, multiple treatments over time create polygons stacked on top of each other.

15. Tying Treatments Together Multiple treatments on a single feature class or on different feature classes can be associated with each other (“linked”) with a common name (TRT_NAME) and number (TRT_ID). Individual treatments in a group of treatments can be uniquely identified with a sequential number (TRTCOMP_ID). Example: An area was cut, then burned then seeded. There are 3 polygons on 3 different themes (they can be the same extent or different). Each has the same TRT_NAME and TRT_ID, but different TRTCOMP_ID.

16. Tying Treatments to Programs Treatments can be associated with a particular program using several attributes: BUDGET_CD contains activity and program element. BENEFIT contains the predominant reason or purpose for the activity. PROGRAM is the program that initiated the activity.

17. Primary Data Fields Additional Core attributes describe the basic facts: What (the feature class itself plus attribute TYPE) When (attribute COMPLT_DT or START_DT) Who (attributes WORKAGENT and BUDGET_CD) How (attributes METHOD and TARGET) Why (attributes BENEFIT and PROGRAM)

18. Other Themes in Treatments Group Treatments may have associated constructed features (like fences). Structures are point and line features (STRCT_POINT and STRCT_ARC) that can be related to a treatment by TRT_ID. Treatments and/or Structures are prescribed and authorized by a management plan. The PLANBDY theme contains project and planning area boundaries (large and small) with unique identifiers (PLANID). Treatments and Structures use PLANID to link to their associated plan.

19. Monitoring Over Time • Monitoring (including survey & research) is something done on entities that already exist (does not create new spatial features). • Sampling is data collected at a specific point and time and the data can be used for a variety of purposes including monitoring of treatments. Sampling is a point feature class not part of this design effort. • One-time monitoring can be handled with a simple attribute (TRT_MONITOR) on the treatment feature classes. Repeated monitoring over time can be handled by a one-to-many link to an external table.

20. Primary Associated Databases & Applications • Micro*StormsOR/WA; Includes Vegetation, Sampling and predominantly TCUT and MECH treatment themes. • TSIS/TSARS OR/WA; Includes TCUT, MECH and PLANBDY treatment themes. • NFPORS National Interagency; Includes TCUT, BURN, MECH and CHEM as well as PLANBDY. • IRDA Regional Interagency; Includes ALL treatment themes, but only if BENEFIT = ‘Riparian’. • RIPS National BLM; Includes all treatment themes except PLANBDY. • ARIMS OR/WA; Includes Structures. Existing databases and related tables will be flattened if possible (one-to many table relationships that are essentially one-to-one can be combined).

21. PROCESS • Review Known Databases / Datasets • Collect Data from Field Offices • Create Draft Design Diagram • Hold Initial Meetings with “SME”s • Treatment Type Meetings • Draft Data Standard • Test with Use Cases and Validate Against Query, Analysis & Reporting Needs. • Review and Comment • Final Data Standard / Corp. Feature Classes

22. PROGRESS TO DATE • Identified Databases / Datasets • Developed Draft Design • Collected Data (still in process) • Initial SME Meetings • Timber Focus Meetings / ORWA Micro*Storms Redesign Plan • PLANBDY (Project/Plan Boundaries) Data Standard and Geodatabase

23. Stan Frazier OR/WA State Data Administrator (503) 808-6009, Stan_Frazier@or.blm.gov Pam Keller Burns, Oregon District GIS Coordinator (541) 573-4486, Pamela_Keller@or.blm.gov