20260414 13455200 FALSE 20260414 13404900 20260414 13404900 NM_BLM_Admin_Unit_Boundaries 114573.999500 1600196.266900 2879824.275400 4473005.499700 1 002 Projected GCS_North_American_1983 Linear Unit: Meter (1.000000) NAD_1983_UTM_Zone_13N <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' 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>PROJCS[&quot;NAD_1983_UTM_Zone_13N&quot;,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]],PROJECTION[&quot;Transverse_Mercator&quot;],PARAMETER[&quot;False_Easting&quot;,500000.0],PARAMETER[&quot;False_Northing&quot;,0.0],PARAMETER[&quot;Central_Meridian&quot;,-105.0],PARAMETER[&quot;Scale_Factor&quot;,0.9996],PARAMETER[&quot;Latitude_Of_Origin&quot;,0.0],UNIT[&quot;Meter&quot;,1.0],AUTHORITY[&quot;EPSG&quot;,26913]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26913</WKID><LatestWKID>26913</LatestWKID></ProjectedCoordinateSystem> 1.0 FGDC CSDGM Metadata 625000 5000 dataset GIS Manager Bureau of Land Management - New Mexico State Office GIS Team Lead 505-954-2000 301 Dinosaur Trail Santa Fe NM 87508 US blm_nm_comments@blm.gov Monday thru Friday 8:00 am - 4:00 pm Mountain Time 20260414 ArcGIS Metadata 1.0 GIS Manager Bureau of Land Management - New Mexico State Office GIS Team Lead 505-954-2000 301 Dinosaur Trail Santa Fe NM 807508 US blm_nm_comments@blm.gov Monday thru Friday 8:00 am - 4:00 pm Mountain Time Administrative Unit Boundary Polygons https://blmspace.blm.doi.net/oc/intra/drs/SitePages/BLM%20National%20Administrative%20Unit%20Boundaries%20(ADMU).aspx File Geodatabase Feature Class BLM-STATE New Mexico BLM-THEME Geospatial Management ISO 19115 Topic Categories Administrative NGDA Portfolio Themes BLM Administrative Boundaries National Geospatial Data Asset NONE United States Western States NONE Administrative Units BLM Bureau of Land Management Jurisdiction Public Lands 1 -109.535694 -92.187539 40.407664 25.624729 Unknown 20211210 Bureau of Land Management U.S. Department of the Interior, Bureau of Land Management (BLM) BLM Administrative Unit Boundary Polygons 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. 20211210 This polygon feature class represents the spatial extent of active BLM Administrative Unit Boundaries at the State, District, and Field Office levels. This polygon feature class shows the physical boundary of BLM Administrative Units. A Bureau of Land Management (BLM) Administrative Unit is a geographic area in which an organizational unit of the BLM has 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. In some cases, the administrative unit may manage areas outside of the boundary for other programs’ purposes. BLM Admin State GIS Manager Bureau of Land Management - New Mexico State Office GIS/Data Team Lead 505-954-2000 301 Dinosaur Trail Santa Fe NM 87508 US blm_nm_comments@blm.gov Monday thru Friday: 8:00 am - 4:00 pm Mountain Time Administrative Administrative Units BLM BLM Administrative Boundaries boundaries Bureau of Land Management Geospatial Jurisdiction location Management National Geospatial Data Asset New Mexico planningCadastre Public Lands United States Western States 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. These are 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. 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 for 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 information may be updated without notification. Esri ArcGIS 10.1.1.3143 publication date Unknown 20211210 -124.860827 -66.885071 24.396306 49.384356 Unknown 20211210 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. Last metadata review date: 20150309 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. None, these data are considered public domain. 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 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. The attribute total percent accuracy for this dataset is 64.45%. 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. 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 20211210 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 2014-12-05 0 EPSG 6.11(3.0.1) admu_ofc_poly BLM Administrative Unit Boundary Polygons BLM Administrative Units (Boundaries) Implementation Guidelines Feature Class 0 OBJECTID Internal feature number. Esri Sequential unique whole numbers that are automatically generated. OBJECTID OID 4 0 0 ADM_UNIT_CD 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. BLM Administrative Units (Boundaries) Implementation Guidelines DOM_ADM_UNIT_CD BLM Administrative Units (Boundaries) Implementation Guidelines Administrative Unit Code String 8 0 0 ADMU_NAME The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. BLM Administrative Units (Boundaries) Implementation Guidelines Administrative Unit Name String 40 0 0 BLM_ORG_TYPE A name that indicates the type of organization that is being described. BLM Administrative Units (Boundaries) Implementation Guidelines DOM_BLM_ORG_TYPE BLM Administrative Units (Boundaries) Implementation Guidelines BLM Organization Type String 20 0 0 APPRV_DT 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. BLM Administrative Units (Boundaries) Implementation Guidelines Approval Date Date 8 0 0 EFF_DT The date on which an area of the BLM land becomes the responsibility of a BLM administrative unit. BLM Administrative Units (Boundaries) Implementation Guidelines Effective Date Date 8 0 0 ADMU_ST_URL Not on the logical model. The URL of the State Office website. BLM Administrative Units (Boundaries) Implementation Guidelines State Office URL String 150 0 0 PARENT_CD The identifier for the administrative unit that has responsibility for other units. BLM Administrative Units (Boundaries) Implementation Guidelines DOM_ADM_UNIT_CD BLM Administrative Units (Boundaries) Implementation Guidelines Parent Admin Code String 8 0 0 PARENT_NAME The official name by which the organization is known. An organization may include businesses, agencies, or corporations, but not individual persons. BLM Administrative Units (Boundaries) Implementation Guidelines Parent Name String 40 0 0 ADMIN_ST An alphabetic abbreviation that represents each of hte 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 Units (Boundaries) Implementation Guidelines DOM_ADMIN_ST BLM Administrative Units (Boundaries) Implementation Guidelines Administrative State Code String 2 0 0 GlobalID 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. This attribute is included for purposes of replication only. It is not used as a unique identifier for relationships between feature classes/tables. Esri GlobalID GlobalID 38 0 0 SHAPE Feature geometry. Esri Coordinates defining the features. Shape Geometry 0 0 0 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. See the BLM Administrative Units (Boundaries) Implementation Guidelines. Simple FALSE 0 TRUE FALSE