. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR LUP In Progress Boundary Polygon
FGDC Metadata
Show Definitions
Description | Spatial | Data Structure | Data Quality | Data Source | Data Distribution | Metadata
Description
Citation
Information used to reference the data.
Title: BLM OR LUP In Progress Boundary Polygon
Originators: Bureau of Land Management
Publication date: 20130220
Data type: vector digital data
Description
A characterization of the data, including its intended use and limitations.
Abstract:
LUP_PRGS_POLY: Land Use Progress Boundary Polygon (LUP_PRGS_POLY) describes the planning or project area for the Land Use in Progress (LUP_PRGS) dataset. The LUP_PRGS dataset contains LUPs that are in progress. There should not be more than one LUP in progress in a particular area. When an RMP or RMPA changes from in progress to active, the polygons and arcs are added to LUP_CRNT and removed from LUP_PRGS. Once an LUP becomes active, it must integrate with other active LUPs so that there will continue to be no gaps or overlaps in active LUPs. For a more detailed description of the LUP_PRGS 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
Purpose:
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.
Supplemental information:
The LUP_PRGS dataset contains LUPs that are in progress. There should not be more than one LUP in progress in a particular area. If, upon completion, an in progress LUP will spatially alter the boundaries of a neighboring active LUP, a special, in-progress version (showing the altered boundaries) of the affected neighboring LUP should be created and given a status (stage) of PENDCHNG (pending change). When an RMP or RMPA changes from in progress to active, the polygons and arcs are added to LUP_CRNT and removed from LUP_PRGS. At this time, if there is an affected neighboring LUP with PENDCHNG status, it also should be used to replace its associated previously active LUP boundary and removed from LUP_PRGS. Once an LUP becomes active, it must integrate with other active LUPs so that there will continue to be no gaps or overlaps in active LUPs.
Point Of Contact
Contact information for the individual or organization that is knowledgeable about the data.
Organization: Bureau of Land Management
Person: Leslie Frewing
Position: Program analyst
Phone: (503) 808-6088
Email: lfreing@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Data Type
How the data are represented, formatted and maintained by the data producing organization.
Data type: vector digital data
Native dataset environment: Microsoft Windows Server 2008 R2 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.0.3035
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 20130220
Currentness reference:
publication date
Status
The state of and maintenance information for the data.
Data status: Complete
Update frequency: As needed
Key Words
Words or phrases that summarize certain aspects of the data.
Theme:
Keywords: LUP, Resource Management Plans, Land Use Plan Amendments, RMPA, RMP, Progress, Resource Management Plan Amendments, Land Use Plans, Planning
Keyword thesaurus: None
Theme:
Keywords: boundaries
Keyword thesaurus: ISO 19115
Theme:
Keywords: Special Management, Land Use Plans
Keyword thesaurus: BLM-Theme
Place:
Keywords: Washington, Oregon
Keyword thesaurus: BLM-State
Data Access Constraints
Restrictions and legal prerequisites for accessing or using the data after access is granted.
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.
Cross Reference
Information about other, related data sets that are likely to be of interest.
Title: LUP_PRGS_ARC
Originators: Bureau of Lan Management
Publication date: 20121212
Spatial Reference Information
Horizontal Coordinate System
Reference system from which linear or angular quantities are measured and assigned to the position that a point occupies.
Coordinate System Details
Geographic coordinate system
Latitude resolution: 2e-008
Longitude resolution: 2e-008
Geographic coordinate units: Decimal Degrees
Geodetic model
Horizontal datum name: D North American 1983
Ellipsoid name: GRS 1980
Semi-major axis: 6378137.0
Denominator of flattening ratio: 298.257222101
Spatial Domain
The geographic areal domain of the data that describes the western, eastern, northern, and southern geographic limits of data coverage.
Bounding Coordinates
In Unprojected coordinates (geographic)
Boundary Coordinate
West -124.703801 (latitude)
East -116.463064 (latitude)
North 49.000600 (longitude)
South 41.992957 (longitude)
Data Structure and Attribute Information
Overview
Summary of the information content of the data, including other references to complete descriptions of entity types, attributes, and attribute values for the data.
Direct spatial reference method: Vector
Attributes of OSODBA.LUP_PRGS_POLY
Detailed descriptions of entity type, attributes, and attribute values for the data.
Attributes
OBJECTID
Definition:
Internal feature number.
Attribute values: Sequential unique whole numbers that are automatically generated.
Attribute definition source:
ESRI
Shape
Definition:
Feature geometry.
Attribute values: Coordinates defining the features.
Attribute definition source:
ESRI
LUPA_ID
Definition:
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).  For plans in progress the date appears as 20XX.
Attribute domain values
Value Definition
LUPA001801
LUPA001801 - Andrews MFP 1982
Definition Source:
BLM
LUPA001802
LUPA001802 - High Desert MFP 1982
Definition Source:
BLM
LUPA001803
LUPA001803 - John Day RMP 1985
Definition Source:
BLM
LUPA001804
LUPA001804 - Two Rivers RMP 1986
Definition Source:
BLM
LUPA001805
LUPA001805 - Baker RMP 1989
Definition Source:
BLM
LUPA001806
LUPA001806 - Brothers/LaPine RMP 1989
Definition Source:
BLM
LUPA001807
LUPA001807 - Spokane RMP 1992
Definition Source:
BLM
LUPA001808
LUPA001808 - Three Rivers RMP 1992
Definition Source:
BLM
LUPA001809
LUPA001809 - Coos Bay RMP 1995
Definition Source:
BLM
LUPA001810
LUPA001810 - Eugene RMP 1995
Definition Source:
BLM
LUPA001811
LUPA001811 - Klamath Falls RMP 1995
Definition Source:
BLM
LUPA001812
LUPA001812 - Medford RMP 1995
Definition Source:
BLM
LUPA001813
LUPA001813 - Roseburg RMP 1995
Definition Source:
BLM
LUPA001814
LUPA001814 - Salem RMP 1995
Definition Source:
BLM
LUPA001815
LUPA001815 - Upper Klamath Basin-Wood River Ranch RMP 1995
Definition Source:
BLM
LUPA001816
LUPA001816 - Lakeview RA RMP 2003
Definition Source:
BLM
LUPA001817
LUPA001817 - Southeastern Oregon RMP 2003
Definition Source:
BLM
LUPA001818
LUPA001818 - Steens Mountain CMPA/Andrews Management Unit RMP 2005
Definition Source:
BLM
LUPA001819
LUPA001819 - Upper Deschutes RMP 2005
Definition Source:
BLM
LUPA001820
LUPA001820 - John Day RMP
Definition Source:
BLM
LUPA001821
LUPA001821 - Baker RMP
Definition Source:
BLM
LUPA001822
LUPA001822 - Andrews Management Unit RMP  2008
Definition Source:
BLM
PLAN_DATE
Definition:
The date the plan was implemented (YYYYMMDD format).
Attribute definition source:
BLM
NEPA_ID
Definition:
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
Attribute definition source:
BLM
DRAFT_PLANID
Definition:
The name of the Project Plan Area for the plan associated with an activity when  in draft stages.  The RMPA should consist of the original RMP name plus the  word "Amendment."  Once finalized, the final name is added to the PLANID  domain and placed in PLANID, the decision date in PLAN_DATE, the  NEPA_ID filled in and LUPA_ID filled in (for RMP).
Attribute definition source:
BLM
PLAN_STAGE
Definition:
The status (or stage) of the plan that authorizes (or will authorize) the activity.  A plan in Active stage must have PLANID and PLAN_DATE filled in and NEPA_ID and LUPA_ID filled in if applicable.
Attribute domain values
Value Definition
PRE-DRAFT
Plans that are in the Scoping or Analysis of the Management Situation (or equivalent) stage
Definition Source:
BLM
DRAFT
Plans that are in the Draft stage
Definition Source:
BLM
SUPP_DRAFT
Supplemental Draft EIS
Definition Source:
BLM
FINAL
Plans that are in the Final stage
Definition Source:
BLM
SUPP_FINAL
Supplemental Final EIS
Definition Source:
BLM
ACTIVE
Plans for which a Record of Decision or Decision Record has been signed
Definition Source:
BLM
PENDCHNG
Active plans with pending boundary changes due to neighboring in progress plans
Definition Source:
BLM
Attribute definition source:
BLM
PLAN_SUBUNIT
Definition:
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. 
Attribute definition source:
BLM
VERSION_NAME
Definition:
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
Attribute definition source:
BLM
GLOBALID
LUP_NAME
Definition:
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."
Attribute domain values
Value Definition
Andrews Management Unit RMP 2005
Andrews Management Unit RMP 2005
Definition Source:
BLM
Baker RMP 1989
Baker RMP 1989
Definition Source:
BLM
Brothers/LaPine RMP 1989
Brothers/LaPine RMP 1989
Definition Source:
BLM
Cascade-Siskiyou National Monument RMP - 2008
Cascade-Siskiyou National Monument RMP - 2008
Definition Source:
BLM
Coos Bay District RMP 1995
Coos Bay District RMP 1995
Definition Source:
BLM
Coos Bay RMP - 2008
Coos Bay RMP - 2008
Definition Source:
BLM
Eugene District RMP - 2008
Eugene District RMP - 2008
Definition Source:
BLM
Eugene District RMP 1995
Eugene District RMP 1995
Definition Source:
BLM
John Day Resource Area RMP 1985
John Day Resource Area RMP 1985
Definition Source:
BLM
Klamath Falls Resource Area RMP - 2008
Klamath Falls Resource Area RMP - 2008
Definition Source:
BLM
Klamath Falls Resource Area RMP 1995
Klamath Falls Resource Area RMP 1995
Definition Source:
BLM
Lakeview Resource Area RMP 2003
Lakeview Resource Area RMP 2003
Definition Source:
BLM
Lower Deschutes River Management Plan 1993
Lower Deschutes River Management Plan 1993
Definition Source:
BLM
Medford District RMP - 2008
Medford District RMP - 2008
Definition Source:
BLM
Medford District RMP 1995
Medford District RMP 1995
Definition Source:
BLM
NW Forest Plan 1994
NW Forest Plan 1994
Definition Source:
BLM
Roseburg District RMP - 2008
Roseburg District RMP - 2008
Definition Source:
BLM
Roseburg District RMP 1995
Roseburg District RMP 1995
Definition Source:
BLM
Salem District RMP - 2008
Salem District RMP - 2008
Definition Source:
BLM
Salem District RMP 1995
Salem District RMP 1995
Definition Source:
BLM
Southeastern Oregon RMP 2002
Southeastern Oregon RMP 2002
Definition Source:
BLM
Spokane District RMP 1992
Spokane District RMP 1992
Definition Source:
BLM
Steens Mountain Cooperative Management and Protection Area RMP 2005
Steens Mountain Cooperative Management and Protection Area RMP 2005
Definition Source:
BLM
Three Rivers Resource Area RMP 1992
Three Rivers Resource Area RMP 1992
Definition Source:
BLM
Two Rivers Resource Area RMP 1986
Two Rivers Resource Area RMP 1986
Definition Source:
BLM
Upper Deschutes Resource Area RMP 2005
Upper Deschutes Resource Area RMP 2005
Definition Source:
BLM
Upper Klamath Basin-Wood River Ranch RMP
Upper Klamath Basin-Wood River Ranch RMP 
Definition Source:
BLM
Attribute definition source:
BLM
SHAPE.AREA
SHAPE.LEN
SDTS Feature Description
Description of point and vector spatial objects in the data using the Spatial Data Transfer Standards (SDTS) terminology.
Spatial data transfer standard (SDTS) terms
Feature class
Type: GT-polygon composed of chains
Count: 21
Data Quality and Accuracy Information
General
Information about the fidelity of relationships, data quality and accuracy tests, omissions, selection criteria, generalization, and definitions used to derive the data.
Logical consistency report:
Geometry: Polygons do not cover the landscape nor do they cover all BLM lands continuously. There are potentially more than one in-progress LUP or amendment covering the same area, so there may 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.
Completeness report:
Data is complete as of publication date.
Data Source and Process Information
Process Steps
Information about events, parameters, tolerances and techniques applied to construct or derive the data.
Process step information
Process Step 1
Process description:
An empty polygon feature class in the new standard format was created. In progress plan polygon features were selected from the previous standard, PLANDBDY_POLY feature class. These features went through a manual edit review and a review using the LUP_PRGS_TOPO topology layer. The topology review included the relationship of features to the new associated LUP_PRGS_ARC feature class.
Organization: Bureau of Land Management
Person: Arthur Miller
Position: GIS Analyst
Phone: (503) 808-6113
Email: a1miller@blm.gov
Address type: mailing
Address:
P.O.Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20121212
Process Step 2
Process description:
Added features for RMPs for Western Oregon. These are based on the January 2013 line work from RAB/DOB, and have a newer and different representation of watershed based linework such as the boundary formed by the crest of the cascades. These new polygons overlap some existing polygons for east of the cascades plans due to the new RAB/DOB representations. Along with 6 new district or resource area plan boundaries for western Oregon, a seperate overall plan boundary for the entirety of the RMPs for Western Oregon has been included. The overal plan boundary has a unique LUPA_ID, but is not intended to ever become a "current" plan boundary since the records of decision for the plan will be at the district and resource area unit level.
Organization: Bureau of Land Management
Person: Arthur Miller
Position: GIS Analyst
Phone: (503) 808-6113
Email: a1miller@blm.gov
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Process date: 20130128
Data Distribution Information
General
Description of the data known by the party from whom the data may be obtained, liability of party distributing data, and technical capabilities required to use the data.
Distribution liability:
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.
Distribution Point of Contact
Contact information for the individual or organization distributing the data.
Organization: Bureau of Land Management
Person: Eric Hiebenthal
Position: GIS Data Management Specialist
Phone: 503-808-6340
Fax: 503-808-6419
Email: ehiebent@blm.gov
Instructions:
contact instructions
Address type: mailing
Address:
P.O Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Standard Order Process
Common ways in which data may be obtained.
Fees: Contact distributor.
Ordering instructions:
Data are only available through the Oregon/Washington State office of the Bureau of Land Management.
Metadata Reference
Metadata Date
Dates associated with creating, updating and reviewing the metadata.
Last updated: 20130220
Metadata Point of Contact
Contact information for the individual or organization responsible for the metadata information.
Organization: Bureau of Land Management, Oregon State Office
Person: Roger Mills
Position: GIS Specialist
Phone: (503) 808-6340
Fax: (503) 808-6419
Telecommunications Device or Teletypewriter (TDD/TTY) phone: tdd/tty phone
Email: r2mills@blm.gov
Hours of service: 8:00-4:00
Instructions:
None
Address type: mailing
Address:
P.O. Box 2965
City: Portland
State or Province: OR
Postal code: 97208
County: US
Metadata Standards
Description of the metadata standard used to document the data and reference to any additional extended profiles to the standard used by the metadata producer.
Standard name: FGDC Content Standard for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention: local time
FGDC Plus Metadata Stylesheet
Stylesheet: FGDC Plus Stylesheet
File name: FGDC Plus.xsl
Version: 2.0
Description: This metadata is displayed using the FGDC Plus Stylesheet, which is an XSL template that can be used with ArcGIS software to display metadata. It displays metadata elements defined in the Content Standard for Digital Geospatial Metadata (CSDGM) - aka FGDC Standard, the ESRI Profile of CSDGM, the Biological Data Profile of CSDGM, and the Shoreline Data Profile of CSDGM. CSDGM is the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies are ordered to use this standard to document geospatial data created as of January, 1995. The standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the federal level with State and local governments adopting the metadata standard as well. The Biological Data Profile broadens the application of the CSDGM so that it is more easily applied to biological data that are not explicitly geographic (laboratory results, field notes, specimen collections, research reports) but can be associated with a geographic location. Includes taxonomical vocabulary. The Shoreline Data Profile addresses variability in the definition and mapping of shorelines by providing a standardized set of terms and data elements required to support metadata for shoreline and coastal data sets. The FGDC Plus Stylesheet includes the Dublin Core Metadata Element Set. It supports W3C DOM compatible browsers such as IE7, IE6, Netscape 7, and Mozilla Firefox. It is in the public domain and may be freely used, modified, and redistributed. It is provided "AS-IS" without warranty or technical support.
Instructions: On the top of the page, click on the title of the dataset to toggle opening and closing of all metadata content sections or click section links listed horizontally below the title to open individual sections. Click on a section name (e.g. Description) to open and close section content. Within a section, click on a item name (Status, Key Words, etc.) to open and close individual content items. By default, the Citation information within the Description section is always open for display.
Download: FGDC Plus Stylesheet is available from the ArcScripts downloads at www.esri.com.