20260116 07180900 1.0 FALSE prot_poly 003 Geographic GCS_North_American_1983 Angular Unit: Degree (0.017453) <GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433],AUTHORITY[&quot;EPSG&quot;,4269]]</WKT><XOrigin>-400</XOrigin><YOrigin>-400</YOrigin><XYScale>999999999.99999988</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>8.983152841195215e-09</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><LeftLongitude>-180</LeftLongitude><WKID>4269</WKID><LatestWKID>4269</LatestWKID></GeographicCoordinateSystem> 20260406 06570500 20260406 06570500 150000000 5000 dataset external 5a5e623f2f1754e1ac1730244bffa682caeb0e82 Scott Kiefer Bureau of Land Management (BLM), Oregon State Office GS0301 - Geographic Information System Specialist P.O. Box 2965 Portland OR 97208 US skiefer@blm.gov Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown True Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GS0301 - Geographic Information System Specialist Role: Unknown 20240805 ArcGIS Metadata 1.0 Eric Hiebenthal Bureau of Land Management GIS Data Specialist (503 808-6565 P.O. Box 2965 Portland OR 97208 US ehiebent@blm.gov 2018-04-30 Arc GIS Feature Class Winzip Winzip Arc GIS, Winzip 3 https://navigator.blm.gov/home https://gbp-blm-egis.hub.arcgis.com/pages/oregon File Geodatabase Feature Class BLM-STATE Oregon Washington BLM-THEME Disturbance Fire Forest Vegetation NONE Completed Exclosures Land Use Planning Protection Treatments U.S. Department of the Interior, Bureau of Land Management (BLM) BLM OR Exclosure Protection Treatments Polygon 2026-04-06 Bureau of Land Management Portland, Oregon PROT_POLY: This dataset represents completed treatments involving fenced exclosures or protective devices on trees or soil surfaces on BLM managed lands in the states of Oregon and Washington. The entire area is considered "treated" with protection measures. The individual structures or devices used may or may not be captured on a separate theme (STRCT_ARC and/or STRCT_PT). This dataset is used for district, state, and regional needs for management and query of land management treatment. Bureau of Land Management (BLM), Oregon State Office biota Completed Disturbance economy environment Exclosures farming Fire Forest Land Use Planning location Oregon Protection Treatments Vegetation Washington The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM. None, these data are considered public domain. These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification. BLM OR Prescribed Fire Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php BLM OR Biological Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php BLM OR Mechanical Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php BLM OR Revegetation Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php BLM OR Chemical Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php BLM OR Harvest Treatments Polygon 2012-02-01 Bureau of Land Management http://www.blm.gov/or/gis/data.php ESRI Arc Catalog 10.4 -125 -116 41.5 49.5 publication date 2026-04-06 BLM (Bureau of Land Management) A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm) -125 -116 49 42 external 2608c4652e5464ee4d9afaf59bf794e2f513fa7b Sean Jeronimo Bureau of Land Management (BLM), Oregon State Office GS0460 - Forester (503) 315-5927 1717 Fabry Road Southeast Salem OR 97306 US sjeronimo@blm.gov Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown True Name: Sean Jeronimo Organization: Bureau of Land Management (BLM), Oregon State Office Position: GS0460 - Forester Role: Unknown Non classified None Last metadata review date: 20240222 Non classified None These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification. None, these data are considered public domain. Description: Instance of Treatments Existing group. Geometry: Polygons may overlap entirely or in part. Topology: No. Integration Requirements: None, although polygons that represent the same extent should be duplicated to avoid slivering (see Editing Procedures section). Treatments are dynamic themes that are subject to frequent edits and changes. Many features were imported from the legacy data and the attributes are very incomplete. However, newer features will have more complete information and over time the dataset will become more accurate. Unknown Legacy data may be introduced to the dataset by manuscripting on maps and digitizing, GPS, on-screen digitizing using a DOQ or DRG backdrop, duplicating lines from ownership, roads or stream layers, or a combination of these. Treatment boundaries that are based on identifiable physical features such as roads, ridgelines, streams, or on ownership changes should utilize those source line features to illustrate the cartographic relationship. New treatment polygons and edits of existing polygons will be added and noted by district staff. Unknown Pamela Keller Bureau of Land Management, Burns District Office GIS Coordinator (541) 573-4486 28910 Hwy 20 West Hines OR 97738-9424 US pkeller@blm.gov Information from BLM District offices None None Information from BLM District offices 0 EPSG 6.5(3.0.1) TRT_PROT_POLY Feature Class 0 This dataset represents completed treatments involving fenced enclosures or protective devices on trees or soil surfaces on BLM managed lands in the states of Oregon and Washington. BLM OBJECTID OBJECTID OID 4 0 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. SHAPE SHAPE Geometry 0 0 0 Feature geometry. ESRI Coordinates defining the features. TRT_NAME TRT_NAME String 60 0 0 Free text name that identifies the treatment entity, preferably with a place reference and treatment type reference. The name is one-to-one with TRT_ID and the two together provide more reliable identification as long as neither is changed. Naming conventions need to be standardized by programs and/or offices and enforced in order to avoid confusion and loss of information. BLM UNIT_NUM UNIT_NUM String 10 0 0 The unique harvest unit identifying number matching the given unit number in the Timber Sale Information System (TSIS) and contract Exhibit A map. BLM PROJ_NAME PROJ_NAME String 100 0 0 District-assigned name for a project that encompasses several treatment types and/or treatment units. It is not the same as the plan or project authorizing the action (PLANID) and there may be many PROJ_NAME for one PLANID. BLM FRST_TRT Forestry Treatment String 1 0 0 Indicates if the treatment was completed for the forestry program. PROT_TYPE PROT_TYPE String 30 0 0 Type of treatment that protects the land surface or vegetation. Spatial extent is the area protected, not each individual protection structure or device. BLM Fencing Fencing BLM Tubing-Install Tree protection BLM Tubing-Maint Tree protection BLM Tubing-Remove Tubing-Remove BLM Netting Tree protection BLM Bud Capping Bud Capping BLM Ravel Cards Ravel Cards BLM Shade Cards Shade Cards BLM Mulching Apply protective mulch, netting or mat on soil BLM Trapping Trapping BLM Repellent Repellent BLM Baiting Baiting BLM TRT_STATUS TRT_STATUS String 12 0 0 Completed Treatment action completed BLM Status of the treatment action. Used in conjunction with TRT_DATE. BLM TRT_FY TRT_FY String 4 0 0 The BLM Fiscal year the treatment occurred in or in which it is planned. Automatically calculated from TRT_DATE. If TRT_DATE is UNKNOWN or populated only with the year, TRT_FY will be UNKN. BLM TRT_DATE TRT_DATE String 8 0 0 Date the treatment was completed or planned start date. TRT_STATUS provides the necessary information to know whether the treatment is completed or not. YYYYMMDD or YYYYMM, or YYYY format. BLM REASON REASON String 30 0 0 The intended main or primary reason for the action or benefiting resource. Only reasons or benefits that are officially acknowledged and recognized for a particular treatment should be considered, and REASON will contain only the most important. A secondary reason or benefit can be listed in REASON2. Some choices are more general and the most specific choice should be used, e.g. Sage-grouse rather than Birds-General. It is expected that specific species of concern will be added as needed. BLM TRT_DATE_ACC Treatment Date Accuracy String 7 0 0 Describes the accuracy of the TRT_DATE field. The default value for this field is "Day." REASON2 REASON2 String 30 0 0 A secondary reason for the treatment or benefiting resource. Only reasons or benefits that are officially acknowledged and recognized for a particular treatment should be considered. Additional reasons or benefits (same domain) can be listed in a linked table. Some choices are more general, and the most specific choice should be used, e.g. Sage-grouse rather than Birds-General. BLM TRT_TARG TRT_TARG String 30 0 0 Juniper Juniper BLM Duff/Slash Duff/Slash BLM Cheatgrass Cheatgrass BLM Shrub Shrub BLM Bitterbrush Bitterbrush BLM Big Sagebrush Big Sagebrush BLM Mixed Sagebrush Mixed Sagebrush BLM Native Grass Native Grass BLM Native Grass/Forb Native Grass/Forb BLM Mixed Grass-Native and Non-native Mixed Grass-Native and Non-native BLM Grass/Shrub Grass/Shrub BLM Ponderosa Pine Ponderosa Pine BLM Douglas Fir Douglas Fir BLM Pine/Fir Mix Pine/Fir Mix BLM Conifers-Non Juniper Conifers-Non Juniper BLM Mixed Tree-Conifer/Hardwood Mixed Tree-Conifer/Hardwood BLM Hardwood Hardwood BLM Oak Woodland Oak Woodland BLM Hardwood/Shrub Hardwood/Shrub BLM All Vegetation All Vegetation BLM Weeds Weeds BLM Medusahead Rye Medusahead Rye BLM Crested Wheatgrass Crested Wheatgrass BLM Biomass Biomass BLM Livestock Livestock BLM Rodents Rodents BLM Big Game Big Game BLM Herbivore Herbivore BLM Rust Fungi Rust Fungi BLM None For contingency or control area BLM Unknown Unknown BLM Target (affected species) of the treatment action. BLM BLM_ORG_CD BLM_ORG_CD String 5 0 0 OR000 Oregon/Washington BLM BLM ORB00 Burns District Office BLM ORB05 Three Rivers Field Office BLM ORB06 Andrews Field Office BLM ORC00 Coos Bay District Office BLM ORC03 Umpqua Field Office BLM ORC04 Myrtlewood Field Office BLM ORE00 Eugene District Office BLM ORE05 Siuslaw Field Office BLM ORE06 Upper Willamette Field Office BLM ORL00 Lakeview District Office BLM ORL04 Klamath Falls Field Office BLM ORL05 Lakeview Field Office BLM ORM00 Medford District Office BLM ORM05 Butte Falls Field Office BLM ORM06 Ashland Field Office BLM ORM07 Grants Pass Field Office BLM ORM08 Glendale Field Office BLM ORP00 Prineville District Office BLM ORP04 Central Oregon Field Office BLM ORP06 Deschutes Field Office BLM ORR00 Roseburg District Office BLM ORR04 Swiftwater Field Office BLM ORR05 South River Field Office BLM ORS00 Salem District Office BLM ORS04 Cascades Field Office BLM ORS05 Marys Peak Field Office BLM ORS06 Tillamook Field Office BLM ORV00 Vale District Office BLM ORV04 Malheur Field Office BLM ORV05 Baker Field Office BLM ORV06 Jordan Field Office BLM ORW00 Spokane District Office BLM ORW02 Wenatchee Field Office BLM ORW03 Border Field Office BLM Combination of the BLM “State” and Field Office which has administrative responsibility for the treatment. The OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, and California, and vice versa. Similarly, the treatment may cross Resource Area or District boundaries and the administrative responsibility is assigned to one or the other. The unit can be identified only to the district or even state level. BLM PLANID PLANID String 100 0 0 The official name/identifier for the plan or project authorizing the action. Provides link to project or planning area boundary polygon. Too lengthy to list. Contact the State Data Administrator for a copy. BLM PE_CD PE_CD String 2 0 0 Program Element codes being reported against on the management action. BLM BUDGET_CD BUDGET_CD String 50 0 0 Primary funding program activity for a treatment. BLM INITIATIVE2 INITIATIVE2 String 20 0 0 The second (if any) initiative, priorities or plan objective the treatment falls under. BLM INITIATIVE INITIATIVE String 20 0 0 The initiative, priorities or plan objective the treatment falls under. BLM HLI Healthy Lands Initiative BLM ESR Emergency Stabilization and Rehabilitation BLM BARR Burned Area Rehabilitation and Restoration BLM HFI Healthy Forests Initiative BLM WUI Wildland-Urban Interface BLM HFR Hazardous Fuels Reduction BLM STEW Stewardship Contracting BLM ARRA American Recovery and Reinvestment Act of 2009 BLM CWPP Community Wildfire Protection Plan BLM JFS Joint Fire Science BLM WORKAGENT WORKAGENT String 40 0 0 “Who” did the work (or the type of procurement instrument). BLM Force Account Federal labor force BLM Service Contract Service Contract BLM IDIQ Contract IDIQ Contract-non-Stewardship. IDIQ (Indefinite delivery/indefinite quantity) BLM Stewardship Contract Stewardship Contract BLM Permittee Permittee BLM Coop Agreement ODFW, ODA, County, etc. BLM Grantee Grantee BLM Volunteer Volunteer BLM Timber Sale Timber Sale Purchaser BLM Landowner Landowner BLM Unknown Unknown BLM LOCAL_LINK LOCAL_LINK String 30 0 0 District legacy identifier or database link for a treatment (other than RIPS and NFPORS). BLM CONTRACTOR CONTRACTOR String 30 0 0 Contractor name for the contract identified by CONTRACTID. BLM CONTRACTID CONTRACTID String 50 0 0 Timber sale, stewardship, planting, weed control or other contract number. Might be the Task Order number if that is more relevant. BLM NFPORS_TRTID NFPORS_TRTID Integer 4 0 0 NFPORS Treatment ID (integer 9). For existing (completed) and proposed treatments. This ID together with the NFPORS_PROJID creates unique identifiers that are one to one with TRT_ID. BLM NFPORS_PROJID NFPORS_PROJID Integer 4 0 0 Ties different treatments for the same project together by giving them the same Project ID. BLM NISIMS_ID NISIMS_ID GUID 38 0 0 INF_GUID from the National Invasive Species Information System (NISIMS). Linking field to the NISIMS database. BLM RIPSKEY RIPSKEY String 6 0 0 RIPS Key. Currently 6 characters, all digits, but this may change. Links to RIPS (Range Improvement Project System) database application BLM GIS_ACRES GIS_ACRES Double 8 0 0 GIS polygon acres. This is necessary in order to compare to TRT_ACRES. Must be recalculated with every edit submission. Use the projection for the UTM zone the treatment unit falls in, and datum NAD83 with units meters. May not be relevant to Biological treatments BLM TRT_ACRES TRT_ACRES Double 8 0 0 These are actual acres treated or estimated acres proposed for treatment. Not derived from GIS but can be set to GIS_ACRES, if the entire polygon is considered treated. The TRT_ACRES may be substantially less than the total polygon acres, particularly for CHEM_POLY where treated acres (TRT_ACRES) is calculated as total gallons applied (GAL_MIX_AP) divided by MIX_RATE. May not be relevant to Biological (BIO) or Protection (PROT) treatments. BLM VMAP_TRT_ID VMAP Treatment Identifier Integer 4 0 0 Treatment Unique Identifier from the National VMAP dataset. NATL_FLAG National Flag Code String 40 0 0 Field to flag records that also exist in one of the national datasets. Records can be duplicates, partial duplicates, or potential duplicates. While this field is generic, within the context of this data standard, this field specifically flags records that may also exist in VMAP. This field will eventually apply to ESR, fuels, and RIPS data; currently only ESR data has been migrated to VMAP. For ESR records, VMAP attribute information was migrated from NFPORS, not the ORWA Treatment datasets. VMAP spatial information was migrated from completed VTRT treatments with a successful NFPORS_ID join. Records flagged as duplicate records have a successful NFPORS_TRTID join with VMAP and similar geometry and data attribute values in selected fields. There may be attributes disagreement between some data fields. The national datasets are the authoritative dataset. If program users determine VMAP contains the best data information duplicate records can be deleted from the OR/WA datasets. Records flagged partial duplicate records have a successful NFPORS_TRTID join with VMAP but differ in their geometry, data attributes values, or both. Efforts should be made to resolve the differences and update the information in VMAP. Records flagged as potential duplicate records have been identified as associated with program data that has been migrated to VMAP, e.g., ESR, but there is no successful NFPORS_TRTID join. Efforts should be made to associate these records with data in VMAP and update the information in VMAP. PROGRAM_AREA Program Area String 30 0 0 The business area source of the record. TRT_MONI TRT_MONI String 20 0 0 Acceptable Acceptable BLM Mixed Result Mixed Result BLM Unacceptable Unacceptable BLM Result as determined from post treatment inspection. Questions asked will be different for different treatment types. For prescribed burn (BURN), these might include: 1. Was consumption of the targeted fuels inadequate, adequate, or excessive? 2. Were targeted mortality levels inadequate, adequate, or excessive? 3. Was soil heating acceptable or unacceptable? 4. Did any unacceptable damage to non-targeted resources or resource values occur? For chemical treatment of weeds (CHEM) the question might be “Are there any weeds left?” For exclosures (PROT), the question might be whether the targeted animals were effectively excluded. For seedings (REVEG), the questions might include: 1. What was the germination percentage? 2. What percent survived 1 year? 3. What was the coverage? BLM ARCH_CLEAR Archaeological Clearance Date String 8 0 0 Date the proposed treatment area received archaeological clearance. BLM BOT_CLEAR Botany Clearance Date String 8 0 0 Date the proposed treatment area received botanical clearance. YYYYMMDD or YYYYMM or YYYY format or "UNKNOWN". BLM WILD_CLEAR Wildlife Clearance Date String 8 0 0 Date the proposed treatment area received wildlife clearance. YYYYMMDD or YYYYMM or YYYY format or "UNKNOWN". BLM COORD_SRC COORD_SRC String 7 0 0 CFF Lines duplicated or buffered from Cartographic Feature Files (USFS) BLM DEM Digital Elevation Model (30 m or better accuracy) used for creation of contours BLM DIS Lines generated to connect discontinuous features BLM DLG Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs BLM DOQ Screen digitized linework over Digital Orthoquad backdrop BLM DRG Screen digitized linework over Digital Raster Graphic backdrop BLM GCD Lines snapped to Geographic Coordinate Database Points BLM GPS Lines obtained from a Global Positioning System device BLM IMG Linework derived from interpretation of satellite or other non-photographic imagery BLM MAP Digitized linework from hardcopy map BLM MTP Lines duplicated from Digital Master Title Plat BLM SOURCEL Source Layer from BLM GIS BLM SRV Survey methods were used to create the linework (e.g., COGO) BLM TIGER Tiger Data BLM TRS Coordinates only given as a legal description (township, range, section) BLM UNK Unknown coordinate source BLM WODDB WODDB Photogrammetric BLM The actual source of the GIS coordinates for the polylines. If the line is copied from another theme and already has COORD_SRC, it should be reviewed and may need to be changed for use in this dataset. BLM ACCURACY_FT ACCURACY_FT SmallInteger 2 0 0 How close, in feet, the spatial GIS depiction is to the actual location on the ground. There are several factors to consider in GIS error: scale and accuracy of map-based sources, accuracy of Global Positioning System (GPS) equipment, and the skill level of the data manipulators. A value of “0” indicates no entry was made. This is the correct value when the COORD_SRC is another GIS theme (Digital Line Graphs (DLG), Geographic Coordinate Database (GCD), Digital Elevation Model (DEM)) because the accuracy is determined by that theme. However, if COORD_SRC is MAP (digitized from a paper map) or GPS, a value of “0” indicates a missing value that should be filled in either with a non-zero number or “-1.” A value of “-1” indicates that the accuracy is unknown and no reliable estimate can be made. BLM TRT_GUID Treatments Unique Identifier GUID 38 0 0 The unique identifier for treatments. This field is auto populated with GUID value during record creation. GlobalID GlobalID GlobalID 38 0 0 System generated unique identifier. SHAPE_Length SHAPE_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. SHAPE_Area SHAPE_Area Double 8 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. Attributes are provided that give basic information about source, type, and accuracy of the line data. More information may be found in the data standard if available: https://www.blm.gov/or/gis/data.php