5000 150000000 2022-04-07 11:30:42.33 20260309 13490800 editor:esri.dijit.metadata.editor 1.0 FGDC CSDGM Metadata false 1649352642835r668823650150119 NOC Data Management Lead BLM National Operations Center, OC530 NOC Data Management Lead kkirkpatrick@blm.gov Bldg 85, Denver Federal Center Denver CO 80225 US 2026-03-09 11:30:42.33 Last metadata review date: 20220314 BLM-STATE Alaska Arizona California Colorado Eastern States Idaho Montana Nevada New Mexico Oregon Utah Wyoming BLM-THEME Geospatial Management NGDA Portfolio Themes Governmental Units and Administrative and Statistical Boundaries Theme National Geospatial Data Asset NGDA NGDAID186 NONE Administrative Units BLM Bureau of Land Management Jurisdiction Public Lands NONE United States Western States BLM Natl ADMU Field Office Generalized Polygons 2026-03-09 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. U.S. Department of the Interior, Bureau of Land Management (BLM) Bureau of Land Management Bureau of Land Management Many of the BLM National Datasets cannot be taken offline due to the number of vertices in the dataset. In addition, displaying the data using a Feature Service crashes ArcGIS Server due to complex geometries (ie Godzilla polygons). As a result, it became imperative to generalize the Feature Classes so that they can be used in a Feature Service as well as being taken offline. Using configuration settings, the user may choose between using a Smoothing algorithm or Simplification algorithm to perform generalization. Documentation on the Smoothing algorithm can be found here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/cartography/smooth-polygon.htm Documentation on the Simplification algorithm can be found here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/cartography/simplify-polygon.htm Note: At the time of this writing, only polygon smoothing/simplification is tested. However, Linear datasets are also supported (FEATURE_TYPE) *Each of the features were generalized except for the labels (anno) and the point feature class in the admu blm webpub dataset. To keep the naming convention the same, we added the _gen after each feature class so this service and the data layers won’t get confused with the other admu services. This service and the underlying data will be kept “in-sync” with national replication. This feature class is the Field Office level data from the feature level Dataset for the BLM Administrative Unit Boundaries Data Standard. The feature dataset includes both BLM administrative land areas and office locations. Land areas are depicted with polygons for the smallest administrative unit (field offices). Larger administrative units, such as district offices, and administrative states may be derived from these polygons. Office locations at each level are depicted with points.. This dataset is a subset of the official national dataset, containing features and attributes intended for public release and has been optimized for online map service performance. The Schema Workbook represents the official national dataset from which this dataset was derived. This dataset has been generalized in an effort to meet program performance requests and/or requirements within a feature service. The generalized geometry may not reflect the original data perfectly and should be taken into account when running certain analysis types. Changes to the current generalized process are ongoing and this service should not be considered final. This dataset captures and establishes the geographic areas in which the organizational units of the BLM have distinct jurisdictional responsibility for land and resource management activities occurring on the public lands, the maintained rights of the United States (i.e. mineral estate) and actions relating to the Trust responsibilities of the U.S. Government as stipulated in Law or Treaty. Particularly, this data pertains to the following BLM groups and their purposes: BLM Field Office Personnel; most programs and national applications within the BLM; other agencies and the public. 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. BLM Admin State Esri ArcGIS 10.1.1.3143 Administrative Units Alaska Arizona BLM boundaries Bureau of Land Management California Colorado Eastern States Geospatial Governmental Units and Administrative and Statistical Boundaries Theme Idaho Jurisdiction location Management Montana National Geospatial Data Asset Nevada New Mexico NGDA NGDAID186 Oregon planningCadastre Public Lands United States Utah Western States Wyoming 1 -124.860828 -66.885070 24.396305 49.384356 2026-03-09 publication date -124.860828 -66.885070 24.396305 49.384356 National Data Steward Bureau of Land Management, WO830 National Data Steward vmyers@blm.gov 1220 South West 3rd Avenue P.O. Box 2965 Portland OR 97204-2818 US (503) 808-6240 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. 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. 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 Other Constraints Other Constraints Other Constraints Other Constraints Other Constraints Other Constraints Other Constraints Other Constraints -124.860828 -66.885070 49.384356 24.396305 Using the Schema Workbook, 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 BLM Headquarters, where it is compiled to produce seamless national datasets. Unknown Spatial Data Coordinator BLM Headquarters Spatial Data Coordinator scrowe@blm.gov Bldg. 85, Denver Federal Center Denver CO 80225 US (303)236-3508 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 2014-12-05 publication date This document describes the physical design for the national data standard for the geospatial dataset. It is intended as a guideline for implementation. States may extend and expand upon this guideline in order to meet their specific needs, provided that when the data is pushed up to the national level, it will meet the minimum requirements as set forth in the Data Standard BLM Administrative Units Schema Workbook 2011-06-06 2011-06-06 publication date Changes that are made to the Administrative Units data internally are reviewed for correctness before being applied externally. Correctness would include location and point attributes. 2026-03-09 Spatial Data Coordinator BLM Headquarters Spatial Data Coordinator scrowe@blm.gov Bldg. 85, Denver Federal Center Denver CO 80225 US This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States, please call 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. This national dataset is an aggregation from multiple datasets provided by the BLM Administrative States. Please call 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 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. https://gis.blm.gov/arcgis/rest/services/admin_boundaries/BLM_Natl_AdminUnit/MapServer https://gis.blm.gov/arcgis/rest/services/admin_boundaries/BLM_Natl_AdminUnit/MapServer BLM Administrative Units http://www.geoplatform.gov/spec/esri-map-rest This feature data set covers both BLM administrative land areas and office locations. Land areas are depicted with polygons for the smallest administrative unit (field offices). Other levels of administrative units, other, district and state, were derived from these polygons. Overviews were created to improve drawing speed and should not be used for analysis. NOC Data Management Lead BLM National Operations Center, OC530 NOC Data Management Lead kkirkpatrick@blm.gov Bldg 85, Denver Federal Center Denver CO 80225 US 123 26 8 0 181 BLM Administrative Unit Office Points BLM Administrative Unit Office These point features depict the physical locations for active BLM Administrative Unit Offices (at the field office level and above). One physical location may administer more than one administrative unit, and have multiple offices co-located in that location. Therefore, point features may be coincident. BLM Administrative Units (Boundaries) Schema Workbook ADM_UNIT_CD Administrative Unit Code: The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. ADMU_NAME Administrative Unit Name: The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. BLM_ORG_TYPE BLM Organization Type: A name that indicates the type of organization that is being described. Design Considerations: The organization type (field office, district office, administrative state, or other) corresponding to the polygon. ADMIN_ST Administrative State Code: An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2 Label Label Label_Full_Name Label Full Name City_Label City Label BLM Administrative Unit State Boundary This feature class represents the polygon features for active BLM Administrative Unit Boundaries at the State level. BLM Administrative Units (Boundaries) Schema Workbook ADMIN_ST Administrative State Code: An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2 BLM Administrative Unit District Boundary This feature class represents the polygon features for active BLM Administrative Unit Boundaries at the District level BLM Administrative Units (Boundaries) Schema Workbook PARENT_CD Parent Admin Code: The identifier for the administrative unit that has responsibility for other units. Design Considerations: The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. 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. ADMIN_ST Administrative State Code: An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2 BLM Administrative Unit Field Boundary This feature class represents the polygon features for active BLM Administrative Unit Boundaries at the Field level. BLM Administrative Units (Boundaries) Schema Workbook ADM_UNIT_CD Administrative Unit Code: The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. ADMU_NAME Administrative Unit Name: The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. BLM_ORG_TYPE BLM Organization Type: A name that indicates the type of organization that is being described. Design Considerations: The organization type (field office, district office, administrative state, or other) corresponding to the polygon. APPRV_DT Approval Date: The date on which the BLM Washington Office or Assistant Secretary, Land and Minerals Management approved or concurred with the change to the organization unit number, name and/or administrative unit boundaries. EFF_DT Effective Date: The date on which an area of BLM land becomes the responsibility of a BLM administrative unit. ADMU_ST_URL State Office URL : The URL of the State Office website. The standard format for a BLM state website is http://www.blm.gov/xx/st/en.html where “xx” is the 2-character state abbreviation. PARENT_CD Parent Admin Code : The identifier for the administrative unit that has responsibility for other units. The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. 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. PARENT_NAME Parent Name: The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. ADMIN_ST Administrative State Code : An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2 BLM Administrative Unit Other Boundary This feature class represents the polygon features for active BLM Administrative Unit Boundaries at the Other level BLM Administrative Units (Boundaries) Schema Workbook ADM_UNIT_CD Administrative Unit Code: The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. ADMU_NAME Administrative Unit Name: The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. BLM_ORG_TYPE BLM Organization Type: A name that indicates the type of organization that is being described. Design Considerations: The organization type (field office, district office, administrative state, or other) corresponding to the polygon. APPRV_DT Approval Date: The date on which the BLM Washington Office or Assistant Secretary, Land and Minerals Management approved or concurred with the change to the organization unit number, name and/or administrative unit boundaries. EFF_DT Effective Date: The date on which an area of BLM land becomes the responsibility of a BLM administrative unit. ADMU_ST_URL State Office URL : The URL of the State Office website. The standard format for a BLM state website is http://www.blm.gov/xx/st/en.html where “xx” is the 2-character state abbreviation. PARENT_CD Parent Admin Code : The identifier for the administrative unit that has responsibility for other units. Design Considerations: The code that indicates the formal grouping of positions into designated units and the assignment of functions and responsibilities to those units based on the DOI FPPS structure. 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. PARENT_NAME Parent Name : The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. ADMIN_ST Administrative State Code : An alphabetic abbreviation that represents each of the 50 states of the United States, the District of Columbia, the outlying areas of the United States, and associated areas. FIPS PUB 5-2 See the BLM Administrative Units Data Dictionary contained in Zip Folder