. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Activity Plan Boundary Polygon

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Bureau of Land Management
Publication_Date: 20130523
Title:
BLM OR Activity Plan Boundary Polygon
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: http://www.blm.gov/or/gis/data.php
Description:
Abstract:
AVY_PLAN_POLY: Activity Plan Boundary Polygon describes the planning or project area for the Activity Plans dataset. The AVY_PLAN dataset contains activity plan boundaries of wide-ranging size and purpose. They may overlap multiple LUP_CRNT areas, but they do not need to cover all BLM lands, and there may be multiple, overlapping activity plans in any particular area. This dataset can include boundaries for activity plans in various stages from "Pre-Draft" to "Active," but should only contain one boundary per activity plan (one version per plan). For a more detailed description of the Activity Plan 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 AVY_PLAN dataset provides the planning or project boundary for strategic management that may include multiple actions over multiple years in a potentially large area, and may include programmatic plans* covering multiple, active Land Use Plans (LUPs) in the Current Land Use Planning (LUP_CRNT) feature dataset. The data show the over-arching boundaries for actual, on-the-ground treatments, tying them together within a larger area. AVY_PLAN's data may overlap multiple LUP_CRNT areas, but they do not need to cover all BLM lands, and there may be multiple, overlapping activity plans in any particular area. *Programatic Plans refer to specific BLM resource program such as a recreation plan, a noxious weeds plan, or a transportation plan, etc. There are many flavors of programmatic plans. **Note to editors - This dataset can include boundaries for activity plans in various stages from "Pre-Draft" to "Active," but should only contain one boundary per activity plan (one version per plan). The boundary should be entered concurrently with identification of the proposed project area during scoping or upon release of the Environmental Assessment (EA)/Environmental Impact Statement (EIS).
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20130523
Currentness_Reference:
publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -122.248696
East_Bounding_Coordinate: -118.199575
North_Bounding_Coordinate: 44.119436
South_Bounding_Coordinate: 41.993092
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: LUP
Theme_Keyword: Activity Plans
Theme_Keyword: Land Use Plan Amendments
Theme_Keyword: Land Use Plans
Theme_Keyword: Planning
Theme:
Theme_Keyword_Thesaurus: ISO 19115
Theme_Keyword: boundaries
Theme:
Theme_Keyword_Thesaurus: BLM-Theme
Theme_Keyword: Special Management
Theme_Keyword: Land Use Plans
Place:
Place_Keyword_Thesaurus: BLM-State
Place_Keyword: Washington
Place_Keyword: Oregon
Access_Constraints: PUBLIC DATA: None, these data are considered public domain.
Use_Constraints:
*Note to user - The nature of this data may be very fluid. A close reading of the data standard is strongly recommended. Any questions should be directed to the data steward listed under Contacts. *Note to editors - This dataset can include boundaries for activity plans in various stages from "Pre-Draft" to "Active," but should only contain one boundary per activity plan (one version per plan). The boundary should be entered concurrently with identification of the proposed project area during scoping or upon release of the Environmental Assessment (EA)/Environmental Impact Statement (EIS). 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.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Land Management
Contact_Person: Leslie Frewing
Contact_Position: Program analyst
Contact_Address:
Address_Type: mailing
Address:
P.O. Box 2965
City: Portland
State_or_Province: OR
Postal_Code: 97208
Country: US
Contact_Voice_Telephone: (503) 808-6088
Contact_Electronic_Mail_Address: lfreing@blm.gov
Native_Data_Set_Environment:
Microsoft Windows Server 2008 R2 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.1.3143
Cross_Reference:
Citation_Information:
Originator: Bureau of Lan Management
Publication_Date: 20121212
Title:
AVY_PLAN_ARC
Online_Linkage: http://www.blm.gov/or/gis/data.php
Back to Top
Data_Quality_Information:
Logical_Consistency_Report:
Polygons do not cover the landscape nor do they cover all BLM lands continuously. In addition, there may be islands ("donut holes") of non-planning areas surrounded by planning areas. 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. There are potentially many plans covering the same area, so there will be overlapping polygons. Arcs are simple, non-overlapping lines that are split between endpoints as needed.
Completeness_Report:
Data is complete as of publication date.
Lineage:
Process_Step:
Process_Description:
An empty polygon feature class in the new standard format was created. Activity 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 AVY_PLAN_TOPO topology layer. The topology review included the relationship of features to the new associated AVY_PLAN_ARC feature class.
Process_Date: 20121212
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Land Management
Contact_Person: Arthur Miller
Contact_Position: GIS Analyst
Contact_Address:
Address_Type: mailing
Address:
P.O.Box 2965
City: Portland
State_or_Province: OR
Postal_Code: 97208
Country: US
Contact_Voice_Telephone: (503) 808-6113
Contact_Electronic_Mail_Address: a1miller@blm.gov
Back to Top
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains
Point_and_Vector_Object_Count: 79
Back to Top
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
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
Back to Top
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: OSODBA.AVY_PLAN_POLY
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition:
Internal feature number.
Attribute_Definition_Source:
ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition:
Feature geometry.
Attribute_Definition_Source:
ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Coordinates defining the features.
Attribute:
Attribute_Label: PLANID
Attribute_Definition:
The official and unique name of an activity plan.  These names are filled in when the plan is final.  Until the plan is final the DRAFT_PLANID is used.  In the Plan Area Boundary theme group, the full PLANID domain is used only for activity plans (AVY_PLAN).  
Attribute_Definition_Source:
BLM
Attribute_Domain_Values:
Unrepresentable_Domain:
Too lengthy to list. Contact State Data Administrator for a copy.
Attribute:
Attribute_Label: PLAN_DATE
Attribute_Definition:
The date the plan was implemented (YYYYMMDD format). This field is filled in when the plan is final.
Attribute:
Attribute_Label: NEPA_ID
Attribute_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 Statement. This field is filled in when the plan is final.
Attribute_Definition_Source:
BLM
Attribute:
Attribute_Label: DRAFT_PLANID
Attribute_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:
Attribute_Label: PLAN_STAGE
Attribute_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:
Enumerated_Domain:
Enumerated_Domain_Value: PRE-DRAFT
Enumerated_Domain_Value_Definition:
Plans that are in the Scoping or Analysis of the Management Situation (or equivalent) stage
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: DRAFT
Enumerated_Domain_Value_Definition:
Plans that are in the Draft stage
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: SUPP_DRAFT
Enumerated_Domain_Value_Definition:
Supplemental Draft EIS
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: FINAL
Enumerated_Domain_Value_Definition:
Plans that are in the Final stage
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: SUPP_FINAL
Enumerated_Domain_Value_Definition:
Supplemental Final EIS
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: ACTIVE
Enumerated_Domain_Value_Definition:
Plans for which a Record of Decision or Decision Record has been signed
Enumerated_Domain_Value_Definition_Source:
BLM
Enumerated_Domain:
Enumerated_Domain_Value: PENDCHNG
Enumerated_Domain_Value_Definition:
Active plans with pending boundary changes due to neighboring in progress plans
Enumerated_Domain_Value_Definition_Source:
BLM
Attribute:
Attribute_Label: GLOBALID
Attribute:
Attribute_Label: PLAN_SUBUNIT
Attribute_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
Attribute:
Attribute_Label: SHAPE.AREA
Attribute:
Attribute_Label: SHAPE.LEN
Back to Top
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Land Management
Contact_Person: Eric Hiebenthal
Contact_Position: GIS Data Management Specialist
Contact_Address:
Address_Type: mailing
Address:
P.O Box 2965
City: Portland
State_or_Province: OR
Postal_Code: 97208
Country: US
Contact_Voice_Telephone: 503-808-6340
Contact_Facsimile_Telephone: 503-808-6419
Contact_Electronic_Mail_Address: ehiebent@blm.gov
Contact Instructions:
contact instructions
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.
Standard_Order_Process:
Fees: Contact distributor.
Ordering_Instructions:
Data are only available through the Oregon/Washington State office of the Bureau of Land Management.
Back to Top
Metadata_Reference_Information:
Metadata_Date: 20130320
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Land Management, Oregon State Office
Contact_Person: Roger Mills
Contact_Position: GIS Specialist
Contact_Address:
Address_Type: mailing
Address:
P.O. Box 2965
City: Portland
State_or_Province: OR
Postal_Code: 97208
Country: US
Contact_Voice_Telephone: (503) 808-6340
Contact_TDD/TTY_Telephone: tdd/tty phone
Contact_Facsimile_Telephone: (503) 808-6419
Contact_Electronic_Mail_Address: r2mills@blm.gov
Hours_of_Service: 8:00-4:00
Contact Instructions:
None
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Back to Top