20250624 09145600 1.0 FALSE LWC_MNGMNT_POLY 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.3.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> 20250811 10574300 20250811 10574300 150000000 5000 dataset external 5a5e623f2f1754e1ac1730244bffa682caeb0e82 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 True Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GS0301 - Geographic Information System Specialist Role: Unknown 20250624 ArcGIS Metadata 1.0 Eric Hiebenthal Bureau of Land Management State Data Steward 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. Arc GIS Feature Class Winzip Winzip Arc GIS; Winzip https://gbp-blm-egis.hub.arcgis.com/pages/oregon File Geodatabase Feature Class BLM-STATE Oregon Washington BLM-THEME Geospatial Management Wilderness NONE LWC Wilderness Characteristics Bureau of Land Management U.S. Department of the Interior, Bureau of Land Management (BLM) BLM OR LWC Management Polygons U.S. Department of Interior, Bureau of Land Management (BLM) vector digital data This is an aggregate national dataset. Source data were received from all or some of the BLM state offices of Alaska, Arizona, California, Colorado, Eastern States, Idaho, Montana, Nevada, New Mexico, Oregon/Washington, Utah, and Wyoming. 2025-08-11 LWC_MNGMNT_POLY: This polygon feature represents the spatial extent and boundaries of BLM Lands with Wilderness Characteristics with management decisions. This dataset also also provides BLM and the public with information about naturalness, opportunities for solitude and/or primitive recreation, supplemental values and proximity to Wilderness Areas or Wilderness Study Areas. BLM Managed Lands with Wilderness Characteristics is consistent with Section 202 of the Federal Land Policy and Management Act (FLPMA), which requires the Secretary of the Interior to develop, maintain and when appropriate, revise land use plans which provide by tracts or areas for the use of public lands, and the BLM Land Use Planning Handbook, BLM has identified and begun an assessment of BLM-managed lands with wilderness characteristics outside of existing WSAs. BLM Manual 6320 - Considering Lands with Wilderness Characteristics in the BLM Land Use Planning Process, provides the guidance from which BLM considers lands with wilderness characteristic and their possible management status. This polygon feature represents the spatial extent and boundaries of lands that are determined to have wilderness characteristics, and the management status of those lands. The Federal Land Policy and Management Act of 1976 directed the Bureau to inventory and study its roadless areas for wilderness characteristics. To be designated as a Land with Wilderness Characteristics, an area has to have the following features: Size - roadless areas of at least 5,000 acres of public lands or of a manageable size OR proximity to a Wilderness Area of Wilderness Study Area, Naturalness - generally appears to have been affected primarily by the forces of nature; Opportunities - provides outstanding opportunities for solitude or primitive and unconfined types of recreation. In addition, Lands with Wilderness Characteristics often have special qualities such as ecological, geological, educational, historical, scientific and scenic values. Bureau of Land Management (BLM), Oregon State Office biota environment Geospatial LWC Management Oregon Washington Wilderness Wilderness Characteristics 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. Esri ArcGIS 10.1.1.3143 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). Each state office has a Data Steward or Contact Person for this data. Please contact the specific state office for additional information on their state dataset. -124.368205 -77.182370 31.332563 48.987865 20230628 20230628 -124.860828 -66.885070 49.384356 24.396305 external 6cdd5c59a7b8f0b62b5196dfc6861bc1312a2e37 Lauren Pidot Bureau of Land Management, Oregon State Office Program Analyst Planner (503) 808-6297 P.O. Box 2965 Portland OR 97208 US lpidot@blm.gov True Name: Lauren Pidot Organization: Bureau of Land Management, Oregon State Office Position: Program Analyst Planner Role: Unknown Non classified None Last metadata review date: 20250620 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. Non classified None This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The logical consistency of this dataset reflects that of the source datasets. Each source dataset is run through a series of tests to verify that the data complies with the format specified in the Data Standard. ERRORS AND INCONSISTENCIES MAY STILL BE PRESENT IN THE DATA. These tests were conducted using ESRI ArcMap 10.1. The tests consisted of checking coded values for attributes against a domain of accepted values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero. For the geometry, the topology was validated; however overlaps and gaps can still be found. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The logical consistency of this dataset reflects that of the source datasets. Each source dataset is run through a series of tests to verify that the data complies with the format specified in the Data Standard. ERRORS AND INCONSISTENCIES MAY STILL BE PRESENT IN THE DATA. These tests were conducted using ESRI ArcMap 10.1. The tests consisted of checking coded values for attributes against a domain of accepted values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero. For the geometry, the topology was validated; however overlaps and gaps can still be found. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The logical consistency of this dataset reflects that of the source datasets. Each source dataset is run through a series of tests to verify that the data complies with the format specified in the Data Standard. ERRORS AND INCONSISTENCIES MAY STILL BE PRESENT IN THE DATA. These tests were conducted using ESRI ArcMap 10.1. The tests consisted of checking coded values for attributes against a domain of accepted values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero. For the geometry, the topology was validated; however overlaps and gaps can still be found. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The completeness of this dataset reflects that of the source datasets. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The accuracy of attributes in this dataset reflects that of the source datasets. Attribute accuracy was tested by validating attribute coded values against accepted domain values, checking that alpha-numeric values followed a valid format, and checking that numeric values were greater than zero. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please contact the distributor for additional information on provenance, history, accuracy and quality of the data. The positional accuracy across this dataset varies according to the source. Using the implementation guidelines, GIS staff at BLM field and state offices cross-walk and clean up their data to comply with the standardized national dataset. Then, the BLM field and/or state offices submit the data to the National Operations Center (NOC), where it is compiled to produce seamless national datasets. This process of data replication to the National Operations Center is intended to occur on a monthly basis. Spatial Data Coordinator BLM National Operations Center Spatial Data Coordinator (303)236-5445 (303)236-3508 Bldg. 50, Denver Federal Center Denver CO 80225 US scrowe@blm.gov 20230628 This official BLM Data Management handbook contains information about how data is administered, managed, and tracked. This handbook discusses how the BLM operates with regard to data development and design, quality, metadata, and business rules. The information this resource contains also pertains to geospatial data. H-1283-2 Data Administration and Management Handbook 2014-12-05 Release 1-1762 U.S. Department of Interior, Bureau of Land Management (BLM) http://web.blm.gov/internal/wo-500/directives/dir-hdbk/h1283-2.pdf publication date Worked with data steward to identify inventory polygons to load into the management feature class. Source of information was RMP datasets and published RMP's. 20250424 external ab69b8b3d7fb8f098bb20d9b375261be50f153ac Dana Baker-Allum Bureau of Land Management GS0301 - Geospatial Data Designer (503) 808-6320 P.O. Box 2965 Portland OR 97208 US dbakerallum@blm.gov Name: Dana Baker-Allum Organization: Bureau of Land Management Position: Senior GIS Applications Developer Role: Unknown True Name: Dana Baker-Allum Organization: Bureau of Land Management Position: GS0301 - Geospatial Data Designer Role: Unknown 614 EPSG 6.5(3.0.1) See the Lands with Wilderness Characteristics (LWC) Implementation Guidelines. LWC_MNGMNT_POLY Represents LWC Units that have been determined to meet the size, naturalness, outstanding opportunities criteria and have gone through a management determination in an RMP that has been finalized. Feature Class 614 OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. LWC_ID LWC Unique Identifier The identifier for an LWC assigned as part of the inventory process. As per BLM Manual 6310 - Conducting Wilderness Characteristics Inventory on BLM Lands (Public)" dated 1/8/2021 (https://www.blm.gov/sites/default/files/docs/2021-01/BLM-Policy-Manual-6310.pdf)., each area will be assigned a unique identifier using a two-letter state code, office code, and an inventory area number, e.g. NV-030-051. Where possible, numbers assigned should build on the original inventory. LWC_ID remains the same through any inventory/managed status. Also used on the associated roads feature class (LWC_ROAD_ARC) to indicate which unit the road falls within or forms a boundary for. BLM String 12 0 0 Example: OR-015-065 UNIT_NAME Unit Name Descriptive name identifier for each Wilderness Characteristic unit. Mixed case words, preferably with a local geographic reference. Unique for OR/WA. BLM String 100 0 0 SUB_UNIT_NAME Sub Unit Name Descriptive name used to identify sub-units within a unit BLM String 100 0 0 LWC_MNGMNT_STS LWC Management Status Indicates how the area determined to have LWC will be managed. Areas may be managed to protect, managed with restrictions, managed for other multiple uses, or have no RMP decision. BLM String 30 0 0 Manage to Protect Manage to Protect - Protecting wilderness characteristics while providing for compatible multiple uses. BLM Manage with Restrictions Manage with Restrictions - Minimize impacts to wilderness characteristics via management restrictions (e.g., terms and conditions of use or stipulations) while emphasizing other multiple uses. BLM Manage for Other Multiple Uses Manage for Other Multiple Uses - Allowing for other multiple uses in an area while not protecting wilderness characteristics. BLM No RMP Decision No RMP Decision - No management decision has been selected. BLM ROD_DATE Record of Decision Date Date the unit became official through a Record of Decision BLM Date 8 0 0 Example: 1/15/2025 MNGMNT_UNIT_NAME Management Unit Name General name description of the management unit or RMP. This would be the Field Office, Monument or NCA name, or similar management unit. BLM String 100 0 0 Example: Lakeview Resource Management Plan Amendment MNGMNT_DOC_URL Management Document URL A BLM URL to the read-only Resource Management Plan in ePlanning. This field may contain several comma-separated links to several documents. BLM String 500 0 0 Example: https://eplanning.blm.gov/eplanning-ui/project/114300/510 NEPA_ID NEPA Plan Identifier The official NEPA Plan ID for the plan authorizing the management status. BLM String 50 0 0 Example: OI-BLM-ORWA-L050-2018-0030-RMP-EIS DATA_RLSBLTY_YN Data Releasability A Yes/No field Indicating whether or not the record is approved to publish for public use. Records Access Category 1A - Public Data These are externally provided data made available to the public and are considered public domain. These data contain no sensitive information which would be prevented from disclosure by Freedom of Information Act (FOIA), the Privacy Act or other laws. DATA_RLSBLTY_CD attribute will be populated YES for this data. Records Access Category 2 - Non-Public Data, Internal Use These are BLM data that could contain information that should not be disclosed to the public because of the Privacy Act or FOIA. It may be requested by the public through FOIA. The data to be published for public use under Category 1A will be a subset of the complete data that will be available for internal BLM use. Easements and reservations that provide administrative access only will not be published/provided to the public. A field in the dataset/geodatabase attributes will be added as publish Yes/No. Upon field office review and QC of the data they will confirm the Yes for public access features. The data that is defined by publish "No" would fall under Category 2 and the publish "Yes" under Category 1A. The field office is responsible for identifying data that can be displayed to the public. BLM String 3 0 0 NO NO - Negative or Not Present BLM YES YES - Affirmative or Present BLM GIS_ACRES GIS Acres The entire acreage of the polygon regardless of land status. 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 BLM_ORG_CD BLM Organization Code A combination of the BLM administrative state and field office which 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. 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. ADMIN_ST Administrative State Code An administrative unit that identifies the state or geographic area which has administrative jurisdiction over lands, and cases. The land for a case may not be physically located in the associated administrative state. Only those states that are BLM administrative states are in the domain for this entity. For instance, the administrative state of Oregon is responsible for both Oregon and Washington. The default value for this field is "OR." BLM String 2 0 0 CA CA - California BLM ID ID - Idaho BLM NV NV - Nevada BLM OR OR - Oregon BLM COORD_SRC_TYPE Coordinate Source Type The name that identifies the general category for the origin of the location coordinate, representing a compilation of the state adopted source codes. The domain contains those values that would most likely be used in the determination of source codes for the data set. The default value for this field is "OTH - All records to be assigned other because we are tracking feature source in the arc layer." BLM String 5 0 0 MAP MAP BLM IMG IMG BLM GPS GPS BLM GCD GCD BLM NHD NHD BLM SRV SRV BLM TRS TRS BLM LLD LLD BLM GIS GIS BLM UNK UNK BLM OTH OTH - All records to be assigned other because we are tracking feature source in the arc layer. BLM WBD WBD BLM GISO GISO BLM LiDAR LiDAR BLM ADMIN_UNIT_CD Administrative Unit Code The BLM administrative unit/office that is a combination of Administrative State Code and Administrative Office Code that fully identifies the geographic area which has jurisdiction over the lands. This field is auto populated from the BLM_ORG_CD field. BLM String 8 0 0 Administrative Unit Code. This is the national list of administrative units. This domain is inherited from the national Administrative Units data standard. This is a lengthy domain. For the full list go to: https://gis.blm.gov/ORDownload/Domains/DOM_ADM_UNIT_CD.xlsx. GLOBALID GlobalID An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data. GlobalID 38 0 0 Example: {4747B796-44B4-4628-B069-2D496422E59F} 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.