. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR LUP Historic Boundary Polygon

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR LUP Historic Boundary Polygon

Abstract:
LUP_HIST_POLY: Land Use Planning Historicy Polygon (LUP_HIST_POLY) describes the planning or project area for the Land Use Planning Historic (LUP_HIST) dataset. For a more detailed description of the LUP_HIST dataset see the Supplemental Information section in this document or follow the link to the Plan Area Boundary Spatial Data Standard below. Data Standard Linkage: http://www.blm.gov/or/datamanagement/files/LUP_Revised_Data_Standard.pdf

Supplemental information:
The LUP_HIST (historic) dataset contains LUPs that have been superseded by newer LUPs or features of active LUPs that have since been replaced in LUP_CRNT through maintenance to more accurate features. There may be multiple, overlapping historic LUPs in any particular area. Superseded or dropped LUPs in progress or Activity Plan Boundaries are not retained on a special archive dataset, but can be found in normal data archives.

  1. How should this data set be cited?

    Bureau of Land Management, 20140926, BLM OR LUP Historic Boundary Polygon.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -125
    East: -119.8
    North: 49.5
    South: 37.5

  3. What does it look like?

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

    Calendar date: 20140926
    Currentness reference:
    publication date

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

  6. How does the data set represent geographic features?

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

      It contains the following vector data types (SDTS terminology):
      • GT-polygon composed of chains (8)

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

  7. How does the data set describe geographic features?

    LUP_HIST_POLY
    LUPA_ID is a national ten-character identifier that is an arbitrary serial identifier.  All OR/WA RMP's are numbered between LUPA1801 and LUPA2000.  These identifiers distinguish a unique occurrence of a BLM Land Use Plan.  These numbers are assigned by the State Planning Lead and only apply to RMPs.  For RMP's, LUPA_ID's can be associated with either completed plans (PLANID) or plans in progress (DRAFT_PLANID). Depending on software settings this value may appear as the ten-character code value or the ten-character code value and the subtype description of the LUP name.

    OBJECTID
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    PLAN_DATE
    The date the plan was implemented (YYYYMMDD format). (Source: BLM)
                      

    NEPA_ID
    The BLM's numbering convention for any new document developed to comply  with the NEPA.  Convention established by Instruction Memorandum 2008-199,  Change 1 (12/18/2008). Format:  DDC-ADC-AD-CCDC-FIYR-NDSN-TYP  DDC:  Department Designation Code; three-letter code used to identify the name  of the department within the Government (example:  DOI = Department of the  Interior). ADC:   Agency Designation Code; three-letter code used to identify the agency or bureau with the Government (example:  BLM = Bureau of Land  Management). AD:   Administrative Designation Code; two-letter code used to identify the  highest administrative unit involved (state, center, office, or Washington Office)  at the time the NEPA document is created (example: OR = Oregon). CCDC:   Cost Center Designation Code; four-digit code used to identify the  secondary administrative unit involved at the time the NEPA document is  created.  This is compatible with the FBMS (Fiscal and Business Management  System) numbering convention and equates to positions five through eight in the  FBMS Cost Center code structure (Examples: M050 = Butte Falls (Medford)  Field Office; P060 = Deschutes (Prineville) Field Office). FIYR:   Project Start Fiscal Year Date; four-digit code that identifies the 12- month period the Federal Government designates for the use of its funds (October  through September) at the time the NEPA document is created. NDSN:  The NEPA Document Sequence Number; four-digit chronological  number identifying each NEPA document assigned within an Administrative  Unit or Office Designation and beginning at 001 each fiscal year. TYP:  The NEPA Type Code; two or three letter code used to identify the  category of document used to comply with the NEPA (CX = Categorical  Exclusion, EA = Environmental Assessment, DNA =  Determination of NEPA Adequacy, EIS = Environmental Impact State (Source: BLM)
                      

    PLAN_SUBUNIT
    Unit identifier if the plan/project area is divided into subunits, usually only for activity plans (but not all activity plans are subdivided into subunits).  The subunits may not comprise the entire plan area.  The subunits may be disjoint and widely separated with no surrounding polygon.  The PLAN_SUBUNIT may be a simple number or letter and is only meaningful in context with the PLANID or DRAFT_PLANID (for example, there may be three polygons with PLAN_SUBUNIT's of "1," "2," and "3" and each having the same DRAFT_PLANID of "Chalk Juniper Cut").  The "Geographical Management Units" are examples PLAN_SUBUNITS for LUPs.  (Source: BLM)
                      

    VERSION_NAME
    Name of the corporate geodatabase version previously used to edit the record. InitialLoad = feature has not been edited in ArcSDE.  Format:  username.XXX-mmddyy-hhmmss = version name of last edit (hours might be a single digit; leading zeros are trimmed for hours only).  XXX=theme abbreviation (Source: BLM)
                      

    LUPA_ID
    LUPA_ID is a national ten-character identifier that is an arbitrary serial identifier.  All OR/WA RMP's are numbered between LUPA1801 and LUPA2000.  These identifiers distinguish a unique occurrence of a BLM Land Use Plan.  These numbers are assigned by the State Planning Lead and only apply to RMPs.  For RMP's, LUPA_ID's can be associated with either completed plans (PLANID) or plans in progress (DRAFT_PLANID). Depending on software settings this value may appear as the ten-character code value or the ten-character code value and the subtype description of the LUP name and the date of the Record of Decision (ROD). 

    ValueDefinition
    LUPA001801
    LUPA001801 - Andrews MFP 1982
    LUPA001802
    LUPA001802 - High Desert MFP 1982
    LUPA001803
    LUPA001803 - John Day RMP 1985
    LUPA001804
    LUPA001804 - Two Rivers RMP 1986
    LUPA001805
    LUPA001805 - Baker RMP 1989
    LUPA001806
    LUPA001806 - Brothers/LaPine RMP 1989
    LUPA001807
    LUPA001807 - Spokane RMP 1992
    LUPA001808
    LUPA001808 - Three Rivers RMP 1992
    LUPA001809
    LUPA001809 - Coos Bay RMP 1995
    LUPA001810
    LUPA001810 - Eugene RMP 1995
    LUPA001811
    LUPA001811 - Klamath Falls RMP 1995
    LUPA001812
    LUPA001812 - Medford RMP 1995
    LUPA001813
    LUPA001813 - Roseburg RMP 1995
    LUPA001814
    LUPA001814 - Salem RMP 1995
    LUPA001815
    LUPA001815 - Upper Klamath Basin-Wood River Ranch RMP 1995
    LUPA001816
    LUPA001816 - Lakeview RA RMP 2003
    LUPA001817
    LUPA001817 - Southeastern Oregon RMP 2003
    LUPA001818
    LUPA001818 - Steens Mountain CMPA/Andrews Management Unit RMP 2005
    LUPA001819
    LUPA001819 - Upper Deschutes RMP 2005
    LUPA001820
    LUPA001820 - John Day RMP
    LUPA001821
    LUPA001821 - Baker RMP
    LUPA001822
    LUPA001822 - Andrews Management Unit RMP  2008

    LUP_INACTV_DT
    The date the plan was superseded (YYYYMMDD format). (Source: BLM)
                      

    BNDY_INACTV_DT
    The date the plan boundary was modified, while maintaining the same plan guidance (YYYYMMDD format). (Source: BLM)
                      

    Shape_Length
    Length of feature in internal units. (Source: ESRI)
                      

    Positive real numbers that are automatically generated.

    Shape_Area
    Area of feature in internal units squared. (Source: ESRI)
                      

    Positive real numbers that are automatically generated.

    LUP_NAME
    The official name of the LUP, whether final, in progress, or historic.  The PLAN_DATE is filled at the same time along with NEPA_ID and LUPA_ID.  The LUP names are a subset of the larger PLANID domain.  Final plans should have the year of the ROD at the end of the name.  The RMPA should consist of the original RMP name plus the word "Amendment." (Source: BLM)
                      

    ValueDefinition
    Andrews Management Unit RMP 2005
    Andrews Management Unit RMP 2005
    Baker RMP 1989
    Baker RMP 1989
    Brothers/LaPine RMP 1989
    Brothers/LaPine RMP 1989
    Cascade-Siskiyou National Monument RMP - 2008
    Cascade-Siskiyou National Monument RMP - 2008
    Coos Bay District RMP 1995
    Coos Bay District RMP 1995
    Coos Bay RMP - 2008
    Coos Bay RMP - 2008
    Eugene District RMP - 2008
    Eugene District RMP - 2008
    Eugene District RMP 1995
    Eugene District RMP 1995
    John Day Resource Area RMP 1985
    John Day Resource Area RMP 1985
    Klamath Falls Resource Area RMP - 2008
    Klamath Falls Resource Area RMP - 2008
    Klamath Falls Resource Area RMP 1995
    Klamath Falls Resource Area RMP 1995
    Lakeview Resource Area RMP 2003
    Lakeview Resource Area RMP 2003
    Lower Deschutes River Management Plan 1993
    Lower Deschutes River Management Plan 1993
    Medford District RMP - 2008
    Medford District RMP - 2008
    Medford District RMP 1995
    Medford District RMP 1995
    NW Forest Plan 1994
    NW Forest Plan 1994
    Roseburg District RMP - 2008
    Roseburg District RMP - 2008
    Roseburg District RMP 1995
    Roseburg District RMP 1995
    Salem District RMP - 2008
    Salem District RMP - 2008
    Salem District RMP 1995
    Salem District RMP 1995
    Southeastern Oregon RMP 2002
    Southeastern Oregon RMP 2002
    Spokane District RMP 1992
    Spokane District RMP 1992
    Steens Mountain Cooperative Management and Protection Area RMP 2005
    Steens Mountain Cooperative Management and Protection Area RMP 2005
    Three Rivers Resource Area RMP 1992
    Three Rivers Resource Area RMP 1992
    Two Rivers Resource Area RMP 1986
    Two Rivers Resource Area RMP 1986
    Upper Deschutes Resource Area RMP 2005
    Upper Deschutes Resource Area RMP 2005
    Upper Klamath Basin-Wood River Ranch RMP
    Upper Klamath Basin-Wood River Ranch RMP 

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)

    • Bureau of Land Management

  2. Who also contributed to the data set?

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

    Leslie Frewing
    Bureau of Land Management
    Program analyst
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6088 (voice)
    lfreing@blm.gov
Back to Top

Why was the data set created?

Data is intended for support of various Land Use Planning (LUP) activities including Resource Management Plans (RMPs), Resource Management Plan Amendments (RMPA), and activity plans.

Back to Top

How was the data set created?

  1. Where did the data come from?

  2. What changes have been made?

    Date: 20121212 (change 1 of 1)
    An empty polygon feature class in the new standard format was created. Historic plan polygon features were selected from the previous standard, PLANDBDY_POLY feature class. As part of the conversion to the new standard, historic boundaries were created for the whole Western Oregon Plan Review (WOPR) area, along with individual plan boundaries for each district WOPR boundary. The Northwest Forest Plan boundary was also changed from being categorized as an activity plan in the previous data to being an historic plan boundary and included in this feature class. The new polygon features went through a manual edit review and a review using the LUP_HIST_TOPO topology layer. The topology review included the relationship of features to the new associated LUP_HIST_ARC feature class.

    Person responsible for change:
    Arthur Miller
    Bureau of Land Management
    GIS Analyst
    P.O.Box 2965
    Portland, OR 97208
    US

    (503) 808-6113 (voice)
    a1miller@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?

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

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

    Data is complete as of publication date.

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

    Geometry: Polygons may not cover the landscape or all BLM lands continuously until a complete set of current LUP polygons have been archived. There are potentially many historic LUPs covering the same area, so there will be overlapping polygons. An individual plan area may consist of multiple unattached polygons. Such plan boundary polygon pieces should be stored as individual records with common attribute values, not as multi-part polygons. Arcs are simple, non-overlapping lines that are split between endpoints as needed.

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 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.

Distributor 1 of 1

  1. Who distributes the data set?

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

    503-808-6340 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov
    Contact Instructions:
    contact instructions

  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?

    • Cost to order the data: Contact distributor.


    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

  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?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20121212

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR 97208
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