. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Activity Plan 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 Activity Plan Boundary Polygon
Originators: Bureau of Land Management
Publication date: 20130523
Data type: vector digital data
Description
A characterization of the data, including its intended use and limitations.
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).
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.1.3143
Time Period of Data
Time period(s) for which the data corresponds to the currentness reference.
Date: 20130523
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, Activity Plans, Land Use 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:
*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.
Cross Reference
Information about other, related data sets that are likely to be of interest.
Title: AVY_PLAN_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 -122.248696 (latitude)
East -118.199575 (latitude)
North 44.119436 (longitude)
South 41.993092 (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.AVY_PLAN_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
PLANID
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 values: Too lengthy to list. Contact State Data Administrator for a copy.
Attribute definition source:
BLM
PLAN_DATE
Definition:
The date the plan was implemented (YYYYMMDD format). This field is filled in when the plan is final.
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 Statement. This field is filled in when the plan is final.
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).
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
GLOBALID
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
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: 79
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:
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.
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. 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.
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
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: 20130320
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.