U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

GIS Metadata


BLM OR Harvest Treatments Polygon

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Harvest Treatments Polygon

Abstract:
HARV_POLY: This dataset represents completed harvest land treatments on BLM managed lands in the states of Oregon and Washington. Harvest treatments are the cutting and removal or trees or biomass.

Supplemental information:
Treatments are human alterations to the landscape for the purpose of natural resource management, including use, enhancement, and protection. A treatment creates something new; it creates a new physical entity on the landscape. This distinguishes treatments from attributes or information about treatments. Treatments are areas (polygons), zones of alteration. 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)

  1. How should this data set be cited?

    U.S. Department of Interior, Bureau of Land Management (BLM), 20170719, BLM OR Harvest Treatments Polygon.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.415402
    East: -117.026423
    North: 45.881362
    South: 41.993142

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar date: 20170719
    Currentness reference:
    ground condition

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (59391)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 2e-008. Longitudes are given to the nearest 2e-008. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    OSODBA.HARV_POLY_new
    Harvest Treatment data (Source: BLM)

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    TRT_ID
    Unique number identifier for the treatment entity.  Multiple "units" of a treatment are given unique TRT_IDs and TRT_ID is unique across all treatment feature classes.  Multiple units or phases of a treatment project are tied together by TRT_NAME, PLANID, NFPORS_PROJID or CONTRACTID as applicable. (Source: BLM)
                      

    TRT_NAME
    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. (Source: BLM)
                      

    UNIT_NUM
    The unique harvest unit identifying number matching the given unit number in the Timber Sale Information System (TSIS) and contract Exhibit A map. (Source: BLM)
                      

    EA_UNIT
    The unique harvest unit identifying number matching the given unit number in the Timber Sale Information System (TSIS) and contract Exhibit A map. (Source: BLM)
                      

    PROJ_NAME
    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. (Source: BLM)
                      

    HARV_TYPE
    General type of harvest activity. (Source: BLM)
                      

    TRT_STATUS
    Status of the treatment action. Used in conjunction with TRT_DATE. (Source: BLM)
                      

    ValueDefinition
    Completed
    Treatment action  completed

    TRT_FY
    The BLM Fiscal year the treatment occurred in or is planned for.  Automatically calculated from TRT_DATE.  If TRT_DATE is UNKNOWN or populated only with the year, TRT_FY will be "UNKN". (Source: BLM)
                      

    SALE_DATE
    Date the timber is planned or when it was sold based on the TSIS linked database.  This date does not change once a timber contract is approved and is different from the TRT_DATE which follows the "Active" and "Completed" phase of the TRT_STATUS. (Source: BLM)
                      

    SALE_FY
    Auto calculated fiscal year when a timber sale is planned (from TRT_DATE) or when a timber sale has been sold (from SALE_DATE) after the HARV_POLY unit is linked to TSIS. (Source: BLM)
                      

    HARV_RX
    Term describing forest treatment designed to change stand structure to meet management goals. (Source: BLM)
                      

    TRT_DATE
    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. (Source: BLM)
                      

    HARV_METH
    Specific method of harvesting. (Source: BLM)
                      

    REASON
    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. (Source: BLM)
                      

    REASON2
    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. (Source: BLM)
                      

    TRT_TARG
    Target (affected species) of the treatment action. (Source: BLM)
                      

    ValueDefinition
    Juniper
    Juniper
    Duff/Slash
    Duff/Slash
    Cheatgrass
    Cheatgrass
    Shrub
    Shrub
    Bitterbrush
    Bitterbrush
    Big Sagebrush
    Big Sagebrush
    Mixed Sagebrush
    Mixed Sagebrush
    Native Grass
    Native Grass
    Native Grass/Forb
    Native Grass/Forb
    Mixed Grass-Native and Non-native
    Mixed Grass-Native and Non-native
    Grass/Shrub
    Grass/Shrub
    Ponderosa Pine
    Ponderosa Pine
    Douglas Fir
    Douglas Fir
    Pine/Fir Mix
    Pine/Fir Mix
    Conifers-Non Juniper
    Conifers-Non Juniper
    Mixed Tree-Conifer/Hardwood
    Mixed Tree-Conifer/Hardwood
    Hardwood
    Hardwood
    Oak Woodland
    Oak Woodland
    Hardwood/Shrub
    Hardwood/Shrub
    All Vegetation
    All Vegetation
    Weeds
    Weeds
    Medusahead Rye
    Medusahead Rye
    Crested Wheatgrass
    Crested Wheatgrass
    Biomass
    Biomass
    Livestock
    Livestock
    Rodents
    Rodents
    Big Game
    Big Game
    Herbivore
    Herbivore
    Rust Fungi
    Rust Fungi
    None
    For contingency or control area
    Unknown
    Unknown

    BLM_ORG_CD
    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. (Source: BLM)
                      

    ValueDefinition
    OR000
    Oregon/Washington BLM
    ORB00
    Burns District Office
    ORB05
    Three Rivers Field Office
    ORB06
    Andrews Field Office
    ORC00
    Coos Bay District Office
    ORC03
    Umpqua Field Office
    ORC04
    Myrtlewood Field Office
    ORE00
    Eugene District Office
    ORE05
    Siuslaw Field Office
    ORE06
    Upper Willamette Field Office
    ORL00
    Lakeview District Office
    ORL04
    Klamath Falls Field Office
    ORL05
    Lakeview Field Office
    ORM00
    Medford District Office
    ORM05
    Butte Falls Field Office
    ORM06
    Ashland Field Office
    ORM07
    Grants Pass Field Office
    ORM08
    Glendale Field Office
    ORP00
    Prineville District Office
    ORP04
    Central Oregon Field Office
    ORP06
    Deschutes Field Office
    ORR00
    Roseburg District Office
    ORR04
    Swiftwater Field Office
    ORR05
    South River Field Office
    ORS00
    Salem District Office
    ORS04
    Cascades Field Office
    ORS05
    Marys Peak Field Office
    ORS06
    Tillamook Field Office
    ORV00
    Vale District Office
    ORV04
    Malheur Field Office
    ORV05
    Baker Field Office
    ORV06
    Jordan Field Office
    ORW00
    Spokane District Office
    ORW02
    Wenatchee Field Office
    ORW03
    Border Field Office

    PLANID
    The official name/identifier for the plan or project authorizing the action.  Provides link to project or planning area boundary polygon. Domains are too lengthy to list.  Contact the State Data Administrator for a copy. (Source: BLM)
                      

    ValueDefinition
    Too lengthy to list. Contact the State Data Administrator for a copy.
    Oregon Washington BLM

    BUDGET_CD
    Primary funding program activity for a treatment. (Source: BLM)
                      

    INITIATIVE2
    The second (if any) initiative, priorities or plan objective the treatment falls under. (Source: BLM)
                      

    INITIATIVE
    The initiative, priorities or plan objective the treatment falls under. (Source: BLM)
                      

    ValueDefinition
    HLI
    Healthy Lands Initiative
    ESR
    Emergency Stabilization and Rehabilitation
    BARR
    Burned Area Rehabilitation and Restoration
    HFI
    Healthy Forests Initiative
    WUI
    Wildland-Urban Interface
    HFR
    Hazardous Fuels Reduction
    STEW
    Stewardship Contracting
    ARRA
    American Recovery and Reinvestment Act of 2009
    CWPP
    Community Wildfire Protection Plan
    JFS
    Joint Fire Science

    CLASSIFIER
    Name (mixed case, first and last) of the subject matter specialist most knowledgeable about the treatment (contact). (Source: BLM)
                      

    WORKAGENT
    "Who" did the work (or the type of procurement instrument). (Source: BLM)
                      

    ValueDefinition
    Force Account
    Federal labor force
    Service Contract
    Service Contract
    IDIQ Contract
    Non-Stewardship. IDIQ (Indefinite delivery/indefinite quantity)
    Stewardship Contract
    Stewardship Contract
    Permittee
    Permittee
    Coop Agreement
    ODFW, ODA, County, etc.
    Grantee
    Grantee
    Volunteer
    Volunteer
    Timber Sale
    Timber Sale Purchaser
    Landowner
    Landowner
    Unknown
    Unknown

    LOCAL_LINK
    District legacy identifier or database link for a treatment (other than RIPS and NFPORS). (Source: BLM)
                      

    CONTRACTOR
    Contractor name for the contract identified by CONTRACTID. (Source: BLM)
                      

    MS_ID
    Linking field to the MicroStorms Application.  Automatically generated by that application when necessary. (Source: BLM)
                      

    CONTRACTID
    Timber sale, stewardship, planting, weed control or other contract number.  Might be the Task Order number if that is more relevant. (Source: BLM)
                      

    NFPORS_TRTID
    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. (Source: BLM)
                      

    NFPORS_PROJID
    Ties different treatments for the same project together by giving them the same Project ID. (Source: BLM)
                      

    NISIMS_ID
    INF_GUID from the National Invasive Species Information System (NISIMS).  Linking field to the NISIMS database. (Source: NISMS)
                      

    RIPSKEY
    RIPS Key.  Currently 6 characters, all digits, but this may change.  Links to RIPS (Range Improvement Project System) database application (Source: BLM)
                      

    GIS_ACRES
    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 (Source: BLM)
                      

    TRT_ACRES
    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. (Source: BLM)
                      

    ARCH_CLEAR
    Date the proposed treatment area received archaeological clearance. (Source: BLM)
                      

    BOT_CLEAR
    Date the proposed treatment area received botanical clearance. (Source: BLM)
                      

    WILD_CLEAR
    Date the proposed treatment area received wildlife clearance.  YYYYMMDD or YYYYMM or YYYY format. (Source: BLM)
                      

    COORD_SRC
    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. (Source: BLM)
                      

    ValueDefinition
    CFF
    Lines duplicated or buffered from Cartographic Feature Files (USFS)
    DEM
    Digital Elevation Model (30 m or better accuracy) used for creation of contours
    DIS
    Lines generated to connect discontinuous features
    DLG
    Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs
    DOQ
    Screen digitized linework over Digital Orthoquad backdrop
    DRG
    Screen digitized linework over Digital Raster Graphic backdrop
    GCD
    Lines snapped to Geographic Coordinate Database Points
    GPS
    Lines obtained from a Global Positioning System device
    IMG
    Linework derived from interpretation of satellite or other non-photographic imagery
    MAP
    Digitized linework from hardcopy map
    MTP
    Lines duplicated from Digital Master Title Plat
    SOURCEL
    Source Layer from BLM GIS
    SRV
    Survey methods were used to create the linework (e.g., COGO)
    TIGER
    Tiger Data
    TRS
    Coordinates only given as a legal description (township, range, section)
    UNK
    Unknown coordinate source
    WODDB
    WODDB Photogrammetric

    ACCURACY_FT
    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. (Source: BLM)
                      

    COMMENTS
    Free text for comments. (Source: BLM)
                      

    SHAPE.AREA
    Feature geometry. (Source: ESRI)
                      

    SHAPE.LEN
    Feature geometry. (Source: ESRI)
                      

    Entity and attribute overview:
    For complete and up to date listing of attributes and domains look in the "Treatments Spatial Data Standard"
    http://www.blm.gov/or/datamanagement/index.php
Back to Top

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • U.S. Department of Interior, Bureau of Land Management (BLM)

  2. Who also contributed to the data set?

    OR/WA BLM

  3. To whom should users address questions about the data?

    Carolina Hooper
    Bureau of Land Management, Oregon State Office
    Plans Forester
    1717 Fabry Road Southeast
    Salem, OR97306
    US

    (503) 315-5927 (voice)
    chooper@blm.gov
Back to Top

Why was the data set created?

This dataset is used for district, state, and regional needs for management and query of land management treatment.

Back to Top

How was the data set created?

  1. Where did the data come from?

    Type of source media: None
    Source contribution:
    Data is inputed from various district sources.

  2. What changes have been made?

    Date: unknown (change 1 of 1)
    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.

    Person responsible for change:
    Pamela Keller
    Bureau of Land Management, Burns District Office
    GIS Coordinator
    28910 Hwy 20 West
    Hines, OR97738-9424
    US

    (541) 573-4486 (voice)
    pkeller@blm.gov

Back to Top

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    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.

  2. How accurate are the geographic locations?

    Unknown

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Treatments are dynamic themes that are subject to frequent edits and changes.

  5. How consistent are the relationships among the observations, including topology?

    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

Back to Top

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access constraints: PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and may 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 original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may 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 for 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 information may be updated without notification. DATA STEWARD APPROVAL: Leanne Mruzik, state data steward for HARV_POLY, approved the use of this dataset on August 3, 2016.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Specialist
    P.O. Box 2965
    Portland, OR97208
    US

    (503 808-6565 (voice)
    ehiebent@blm.gov

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    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.

  4. How can I download or order the data?

    • Availability in digital form:


    • Data format:
      in format Arc GIS (version Feature Class) Winzip

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

    Arc GIS, Winzip

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20120130
Last reviewed: 20170320

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR97208
US

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
r2mills@blm.gov
Hours of Service: 8:00-4:00
Contact Instructions:
None

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top