Bureau of Land Management
BLM OR Activity Plan Boundary Polygon
vector digital data
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
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.
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).
Land Use Plan Amendments
Land Use Plans
Land Use Plans
PUBLIC DATA: None, these data are considered public domain.
*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.
Bureau of Land Management
P.O. Box 2965
Microsoft Windows Server 2008 R2 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.1.3143
Bureau of Lan Management
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.
Data is complete as of publication date.
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.
Bureau of Land Management
GT-polygon composed of chains
D North American 1983
Internal feature number.
Sequential unique whole numbers that are automatically generated.
Coordinates defining the features.
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).
Too lengthy to list. Contact State Data Administrator for a copy.
The date the plan was implemented (YYYYMMDD format). This field is filled in when the plan is final.
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.
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).
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.
Plans that are in the Scoping or Analysis of the Management Situation (or equivalent) stage
Plans that are in the Draft stage
Supplemental Draft EIS
Plans that are in the Final stage
Supplemental Final EIS
Plans for which a Record of Decision or Decision Record has been signed
Active plans with pending boundary changes due to neighboring in progress plans
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.
Bureau of Land Management
GIS Data Management Specialist
P.O Box 2965
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.
Data are only available through the Oregon/Washington State office of the Bureau of Land Management.
Bureau of Land Management, Oregon State Office
P.O. Box 2965
FGDC Content Standard for Digital Geospatial Metadata