20260219 12054600 1.0 FALSE AVY_PLAN_POLY 002 Geographic GCS_North_American_1983 Angular Unit: Degree (0.017453) <GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433],AUTHORITY[&quot;EPSG&quot;,4269]]</WKT><XOrigin>-400</XOrigin><YOrigin>-400</YOrigin><XYScale>999999999.99999988</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>8.983152841195215e-09</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><LeftLongitude>-180</LeftLongitude><WKID>4269</WKID><LatestWKID>4269</LatestWKID></GeographicCoordinateSystem> 20260414 07254100 20260414 07254100 150000000 5000 dataset Scott Kiefer Bureau of Land Management (BLM), Oregon State Office GS0301 - Geographic Information System Specialist P.O. Box 2965 Portland OR 97208 US skiefer@blm.gov Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GS0301 - Geographic Information System Specialist Role: Unknown 20260213 ArcGIS Metadata 1.0 Eric Hiebenthal Bureau of Land Management GIS Data Management Specialist 503-808-6340 503-808-6419 P.O Box 2965 Portland OR 97208 US ehiebent@blm.gov contact instructions Contact distributor. Data are only available through the Oregon/Washington State office of the Bureau of Land Management. https://gbp-blm-egis.hub.arcgis.com/pages/oregon File Geodatabase Feature Class BLM-STATE Oregon Washington BLM-THEME Geospatial Management NONE Activity Plans NEPA Planning Project Areas U.S. Department of the Interior, Bureau of Land Management (BLM) BLM OR Activity Plan Area Polygons 2026-04-14 Bureau of Land Management Portland, Oregon This data standard describes the Activity Plan Areas dataset. Activity plans are a type of implementation plan that usually describes multiple projects and applies best management practices to meet land use plan objectives. Activity plans are multi-year in timeframe and usually involve multiple actions over time. They can be wide-ranging in size and purpose. They overlap Land Use Planning boundaries, but they do not need to cover all BLM lands. This dataset can include area for activity plans in various stages but should only contain one boundary per activity 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). Maintenance of the dataset should be done as needed as projects are updated and final decisions are made. Note: this theme is not complete and may not include all activities as some districts may choose to only post information in the ePlanning system. This dataset was previously described in the retired Plan Area Boundary data standard. • Dataset (Theme) Name: Activity Plan Area • Dataset (Feature Class): AVY_PLAN_POLY For a more detailed description of the Activity Plan dataset see the Supplemental Information section in this document or follow the link to the Activity Plan Area Spatial Data Standard below. Data Standard Linkage: https://www.blm.gov/about/data/oregon-data-management 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. It shows the over-arching boundary for actual, on-the-ground treatments, tying them together within a larger area. Bureau of Land Management (BLM), Oregon State Office Udom Hong Bureau of Land Management GS0343 - Management and Program Analyst Unknown P.O. Box 2965 Portland OR 97208 US uhong@blm.gov Activity Plans boundaries Geospatial Management NEPA Oregon Planning Project Areas Washington 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. None, these data are considered public domain. These data are provided by Bureau of Land Management (BLM) 'as is' and might 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 sources from which they were derived, and both scale and accuracy may vary across the data set. These data might 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. AVY_PLAN_ARC 2012-12-12T00:00:00 Bureau of Lan Management ESRI Arc Catalog 10.4 -125 -116 41.5 49.5 publication date 2026-04-14 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. *Programmatic 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). A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm) -125 -116 49 42 Non classified None Last metadata review date: 20260210 Non classified None These data are provided by Bureau of Land Management (BLM) 'as is' and might 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 sources from which they were derived, and both scale and accuracy may vary across the data set. These data might 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. None, these data are considered public domain. 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. Unknown Unknown 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. 2012-12-12 Arthur Miller Bureau of Land Management GIS Analyst (503) 808-6113 P.O.Box 2965 Portland OR 97208 US a1miller@blm.gov Attribute ESA_CNSLTN_TYPE_NM was added 2019-03-29 Roger Mills BLM GIS Spec (503) 808-6340 P.O. Box 2965 Portland OR 97208 US r2@blm.govmills 574 EPSG 6.5(3.0.1) AVY_PLAN_POLY Feature Class 574 Activity Plan Area Polygon describes the planning or project area for the Activity Plans dataset. BLM OBJECTID OBJECTID OID 4 0 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. PLANID Plan ID The official name of a land use plan or activity plan. These names are filled in when the plan is final. The PLAN_DATE is filled at the same time along with NEPA_ID and LUPA_ID if applicable. Activity plans generally do not contain a year within the name. PLANID is required if the NEPA_DOC_STTS = Completed or In Progress. BLM String 100 0 0 Plan Name Text. The Plan Name Text refers to the official name for the plan or project. This is a lengthy list of domain values. The domain is available at the following web location: https://www.blm.gov/site-page/oregon-data-management PLAN_DATE Plan Date The date the plan or most recent plan amendment was implemented. This is also known as the Record of Decision (ROD) date. If only partial dates are available, use the following rules for entering values: • Use the first day of the month when only month and year are available. Example: 5/1/2000. • Use the first day of the year when only the year is available. Example: 1/1/2000. PLAN_DATE is required if the NEPA_DOC_STTS = Completed or In Progress. BLM Date 8 0 0 Examples: 10/1/2000, 4/15/1996. NEPA_TYPE NEPA Type The type of NEPA project. This value should match how the project is described in the BLM National ePlanning system. Historic records in the dataset are assigned an Unknown code when ePlanning data is not available. BLM 0 String 10 0 CE CE - Categorical Exclusion BLM DNA DNA - Determination of NEPA Adequacy BLM EA EA - Environmental Assessment BLM EIS EIS - Environmental Impact Statement BLM Other Other - Projects that require public involvement but are not and will never be part of a project subject to NEPA compliance. This may include public comment periods required by other laws such as CERCLA. BLM Unknown Unknown BLM NEPA_ID 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: ORWA = Oregon/Washington). • 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 (CE = Categorical Exclusion, EA = Environmental Assessment, DNA = Determination of NEPA Adequacy, EIS = Environmental Impact Statement). For plans developed prior to 12/2008 a representative number can be established retroactively. BLM String 50 0 0 Examples: DOI-BLM-ORWA-B060-2025-0003-DNA, DOI-BLM-ORWA-C000-2026-0001-CX DRAFT_PLANID Draft Plan ID The name of the Project Plan Area for the plan associated with an activity when in draft stages. Once finalized, the final name is added to the PLANID domain and placed in PLANID, the decision date in PLAN_DATE, and the NEPA_ID filled in. BLM 0 String 100 0 NEPA_DOC_STTS NEPA Document Status 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 filled in if applicable. BLM String 20 0 0 Cancelled Cancelled BLM Completed Completed BLM In Progress In Progress BLM Paused Paused BLM Planned Planned BLM Unknown Unknown BLM PLAN_SUBUNIT Plan Sub Unit 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 disjointed 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_SUBUNITs of "1," "2," and "3" and each having the same DRAFT_PLANID of "Chalk Juniper Cut"). BLM 0 0 String 60 PROJ_IMPL Project Implemented? A Yes/No field to indicate if the activities associated with the NEPA document have been completed on the ground. BLM String 1 0 0 Y Yes BLM N No BLM U Unknown BLM BLM_ORG_CD BLM Org Code A combination of the BLM administrative state and field office that has administrative responsibility for the spatial entity. This includes which office covers the entity for planning purposes and which office is the lead for GIS edits. Another agency or individual may have the physical management responsibility for the on-the-ground entity. This field applies particularly when a spatial entity crosses resource area or district boundaries, and the administrative responsibility is assigned to one or the other rather than splitting the spatial unit. Similarly, OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, and California and vice versa. When appropriate, the office can be identified only to the district or state level rather than to the resource area level. This field is auto calculated on record creation. However, it can be changed to correct the value. BLM String 5 0 0 Administrative Unit Organization Code. Standard BLM organization codes generated from the national list. This is a subset of OR/WA administrative offices and those in other states that border. This is a lengthy domain used by multiple datasets. For the full list of values go to: https://gis.blm.gov/ORDownload/Domains/dom_BLM_ORG_CODE.xls. GIS_ACRES GIS Acres GIS_ACRES is calculated when a polygon is created or modified. The standard spatial reference of Geographic (NAD 1983) cannot be used for calculating acres, so the features are projected as determined by the BLM_ORG_CD of the record. These projections all utilize linear units of meters, so the ESRI Geodatabase-controlled field SHAPE.AREA can be used to convert to acres with the factor based on the U.S. Survey Foot: GIS_ACRES = SHAPE.AREA * 0.0002471044. Note: May not be relevant to Biological treatments. GIS_ACRES is calculated using the NAD 1983 Albers Equal Area project except for the following OR/WA Districts: Prineville: NAD 1983 USFS R6 Albers Coos Bay, Eugene, Lakeview, Medford, Roseburg, Salem: NAD 1983 UTM Zone 10N Burns, Spokane, Vale: NAD 1983 UTM Zone 11N BLM Double 8 0 0 COORD_SRC Coordinate Source The actual source of the GIS coordinates for the polylines. Review lines copied from another theme that already have COORD_SRC. It may need to be changed for use in this dataset. If there are multiple coordinate sources to describe the entire polygon, enter the least accurate of the values into the field. BLM String 7 0 0 CADNSDI CADNSDI - Lines from or snapped to the CADNSDI dataset BLM CFF CFF - Lines duplicated or buffered from Cartographic Feature Files (USFS) BLM DEM DEM - Digital Elevation Model (30m or better accuracy) used for creation of contours BLM DGPS DGPS - Feature obtained from a Global Positioning System device with Real Time Correction (SBAS) BLM DIS DIS - Lines generated to connect discontinuous features BLM DLG DLG - Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs BLM DOQ DOQ - Screen digitized linework over digital orthophotography backdrop (DOQ, NAIP, OSIP, or others) BLM DRG DRG - Screen digitized linework over Digital Raster Graphic backdrop BLM GCD GCD - Lines snapped to Geographic Coordinate Database Points BLM GPS GPS - Lines obtained from a Global Positioning System device BLM IMG IMG - Linework derived from interpretation of satellite or other non-photographic imagery BLM LiDAR LiDAR - LiDAR points, lines, or polygons generated through interpretation or analysis. BLM MAP MAP - Digitized coordinates from hardcopy map or onto a map backdrop BLM MTP MTP - Lines duplicated from Digital Master Title Plat BLM SOURCEL SOURCEL - Coordinates duplicated from a BLM GIS source layer. BLM SOURCEX SOURCEX - Source Layer from non-BLM GIS BLM SRV SRV - Survey methods were used to create the linework (e.g., COGO) BLM TIGER TIGER - Tiger Data BLM TRS TRS - Coordinates only given as a legal description (township, range, section) BLM UNK UNK - Unknown coordinate source BLM WOD WOD - WODDB Photogrammetric BLM GLOBALID GlobalID System generated unique identifier. BLM GUID 38 0 0 Shape Shape Geometry 0 0 0 Feature geometry. ESRI Coordinates defining the features. SHAPE_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. SHAPE_Area Shape_Area Double 8 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. Attribute description may be found in the Abstract. More information may be found in the data standard if available: https://www.blm.gov/about/data/oregon-data-management