eng utf8 dataset dataset BLM AZ Cadastral U.S. Department of the Interior, Bureau of Land Management (BLM) Cadastral Chief (602) 417-9200 (602) 417-9556

One North Central Ave, Suite 800 Phoenix AZ 85004 US BLM_AZ_Cadastral_Services@blm.gov

Monday - Friday, 9 AM to 4 PM, Mountain Standard Time pointOfContact 2022-08-16 ISO 19139 Geographic Information - Metadata - Implementation Specification 2007 geometryOnly composite 1319453 26912 EPSG 6.11(3.0.1) 2022-08-16 publication BLM AZ Cadastral U.S. Department of the Interior, Bureau of Land Management (BLM) Cadastral Chief (602) 417-9200 (602) 417-9556

One North Central Ave, Suite 800 Phoenix AZ 85004 US BLM_AZ_Cadastral_Services@blm.gov

Monday - Friday, 9 AM to 4 PM, Mountain Standard Time originator BLM AZ Cadastral Bureau of Land Management Cadastral Chief (602) 417-9200 (602) 417-9556

One North Central Ave, Suite 800 Phoenix AZ 85004 US BLM_AZ_Cadastral_Services@blm.gov

Monday - Friday, 9 AM to 4 PM, Mountain Standard Time publisher mapDigital This is considered source data for the BLM administrative state of Arizona which is used to create the aggregate national dataset. The second and third divisions are combined into this feature class as an intentional de-normalization of the PLSS hierarchical data. The polygons in this feature class represent the smallest division to the sixteenth that has been defined for the first division. For example In some cases sections have only been divided to the quarter. Divisions below the sixteenth are in the Special Survey or Parcel Feature Class. This feature class is part of the Cadastral National Spatial Data Infrastructure (NSDI) CADNSDI publication data set for rectangular and non-­‐rectangular Public Land Survey System (PLSS) data set. This data set represents the GIS Version of the Public Land Survey System including both rectangular and non-rectangular surveys. The primary source for the data is cadastral survey records housed by the BLM supplemented with local records and geographic control coordinates from states, counties as well as other federal agencies such as the USGS and USFS. The data has been converted from source documents to digital form and transferred into a GIS format that is compliant with FGDC Cadastral Data Content Standards and Guidelines for publication. This data is optimized for data publication and sharing rather than for specific "production" or operation and maintenance. This data set includes the following: PLSS Fully Intersected (all of the PLSS feature at the atomic or smallest polygon level), PLSS Townships, First Divisions and Second Divisions (the hierarchical break down of the PLSS Rectangular surveys) PLSS Special surveys (non-rectangular components of the PLSS) Meandered Water, Corners and Conflicted Areas (known areas of gaps or overlaps between Townships or state boundaries). The Entity-­‐ Attribute section of this metadata describes these components in greater detail. The CADNSDI or the Cadastral Publication Data Standard is the cadastral data component of the NSDI. This is the publication guideline for cadastral data that is intended to provide a common format and structure and content for cadastral information that can be made available across jurisdictional boundaries, providing a consistent and uniform cadastral data to meet business need that includes connections to the source information from the data stewards. The data stewards determine which data are published and should be contacted for any questions on data content or for additional information. The cadastral publication data is data provided by cadastral data producers in a standard form on a regular basis. Cadastral publication data has two primary components, land parcel data and cadastral reference data. It is important to recognize that the publication data are not the same as the operation and maintenance or production data. The production data is structured to optimize maintenance processes, is integrated with internal agency operations and contains much more detail than the publication data. The publication data is a subset of the more complete production data and is reformatted to meet a national standard so data can be integrated across jurisdictional boundaries and be presented in a consistent and standard form nationally. The purpose of this feature class is to inform PLSS CADNSDI users on the second division of the PLSS is quarter, quarter-quarter, sixteenth or government lot division of the PLSS. FGDC Cadastral Subcommittee, BLM AZSO Cadastral and GIS staff, GCDB, IHS Premier Data Services (Contractor). onGoing BLM AZ Cadastral U.S. Department of the Interior, Bureau of Land Management (BLM) Cadastral Chief (602) 417-9200 (602) 417-9556

One North Central Ave, Suite 800 Phoenix AZ 85004 US BLM_AZ_Cadastral_Services@blm.gov

Monday - Friday, 9 AM to 4 PM, Mountain Standard Time pointOfContact continual Arizona place AZ United States USA Western States place AZ United States USA Western States place AZ United States USA Western States place AZ United States USA Western States place Geospatial Management theme Geospatial Management theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Cadastral cadnsi Condominium Conflicted Area Data Steward GCDB Geographic Coordinate Database Meandered Water Parcels PLSS PLSS Corners PLSS Divisions PLSS Second Division PLSS Sections PLSS Special Surveys plssseconddivision Public Land Survey System Section Subdivision Survey System Township theme Downloadable Data 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. otherRestrictions None, these data are considered public domain. unclassified Unclassified Unclassified 2019-02-22 publication U.S. Department of the Interior, Bureau of Land Management (BLM) originator Bureau of Land Management, Arizona State Office

Phoenix, AZ

publisher mapDigital This is considered source data for the BLM administrative state of Arizona which is used to create the aggregate national dataset. crossReference vector eng utf8 planningCadastre Esri ArcGIS 10.4.1.5686 publication date true -114.697716 -108.914457 31.277195 37.039411 2022-08-16 Enterprise Geodatabase Feature Class BLM AZ Cadastral Bureau of Land Management Cadastral Chief (602) 417-9200 (602) 417-9556

One North Central Ave, Suite 800 Phoenix AZ 85004 US BLM_AZ_Cadastral_Services@blm.gov

Monday - Friday, 9 AM to 4 PM, Mountain Standard Time distributor dataset N/A The BLM GCDB personnel using software tools such as dataprep and native GS tools in ArcGIS checked the data for attribute accuracy by verifying it against land records databases such as legal land description (LLD) and Case Status databases. There may be instances where information in survey records and LLD and Case do not agree or places where records are missing. If there are questions about the attribution of a polygon contact the identified data steward. PLSSPoints feature classes: Accuracy of the individual points contained in the PLSSPoint Feature Class that were determined using GMM software the resulting accuracy is reported with the point in the feature class. An overall statement of reliability may be provided for points that are derived from the least accurate component of the error ellipse. Accuracy of the individual points that were determined using PCCS software a carries positional reliability factor for the average of the misclosures in the data set and the maximum misclosure in the data set. The polygon lines are built from the PLSS Points. The PLSS points should be at the nodes of the lines. The horizontal accuracy of the polygon lines is derived from the accuracy of the points at the nodes. Data conforming to the Publication Guideline should follow for the format and structure of the standard for published data. This means that the topological relationships of the PLSS and parcels should be followed. Level 1 conformance to the guideline means that the data follows and conforms to the structure and an active data steward is identified and engaged in data creation and maintenance. Level 2 conformance all attributes that are necessary for essential query, extraction, labeling and use are present. Level 3 conformance all attributes as applicable are populated. This feature class represents all available geographic coordinate database (GCDB) at the time of publication. Every attempt was made to complete the rectangular Public Land Survey System (PLSS) to at least the First Division (section) level and to capture the outside boundary of non-­rectangular PLSS features. Gaps or holes in the data that are known areas of conflict are presented in the ConflictedAreas feature class. If there are other gaps it is where data has not been automated, was not available from the data steward or was not of sufficient quality to be included. AZ’s current contractor IHS, Premier Data Services, took AZ’s GCDB’s data and made it CadNSDI and parcel fabric. Previous Steps pre-IHS PLSS Intersected: BLM Cadastral Survey using the computational programs of either GMM or PCCS has generated the data where BLM Cadastral is the identified data steward. For both programs the first step is to compile survey input data from the best and most current survey records. Control points are identified, evaluated and entered into a control database. With GMM the survey data, measurements abstracted from survey plats, and control stations extracted from the control database are manually entered with weighting factors into GMM software. Compass rule and least squares adjustments are performed using weighting factors assigned to both control stations and survey line data, based on survey methodologies and vintage of survey. With GMM, section subdivision is performed to achieve land unit detail to at least the forty acre (1/16th) level. Instructions for calculating non-‐regular and minor subdivisions are persistently stored during collection and rerun after every new adjustment in order to achieve the detail necessary to delineate all lines required for depicting federal rights, interests, restrictions, and encumbrances. Coincident lines and lines identified as non-‐boundary lines are removed from the data set used for final land unit constructions. Line intersections are computed and given unique identifiers and land units are constructed. GMM lists all coordinates produced by the compass rule and least squares adjustments and subdivision, with connectivity codes between points and compiles them into a single file for development of Geographic Information Systems (GIS) output. With PCCS the survey data, measurements abstracted from survey plats, and control stations extracted from the control database are manually entered into the PCCS processing software. A succession of compass rule adjustments is performed on the lines to adjust them to the control points, followed by a least squares analysis. The resulting coordinates are accompanied by indications of positional reliability; the average of misclosures in the data set and the maximum misclosure in the data set. PCCS lists all coordinates produced by the compass rule and least squares adjustments with connectivity codes between points and compiles them into a single file for development of Geographic Information Systems (GIS) output. With PCCS, section subdivision is performed to achieve land unit detail to at least the forty-acre (1/16th) level. Separate Process Step: GCDB data conversion software (also called data prep) verifies correctness of GCDB file formats and content based on the polygon coding and the rules associated with those codes. Verified coordinate, line and label files are converted to GIS coverages using the topology check application. All errors in topology are flagged for editing and correction. If topological errors exist, editing of arc and node data, as well as parcel labels, is performed using either GMM or ArcGIS Interface. Final edits are entered into input files and the process is repeated until all errors are corrected and a successful GIS coverage is created. GIS coverages are edge matched with adjoining township data sets to insure a seamless PLSS data set is created. Topologically correct GIS coverages are modified to use FGDC compliant naming conventions and then loaded into the CADNSDI. Separate Process Step: The resulting GCDB data sets are imported into a file geodatabase feature class called LADESC and the points are loaded into the PLSSCorners feature class. A series of extract-‐transfer-‐load (ETL) routines are run to import the data into the PLSS Intersected feature class. Metadata is loaded and edited. Other Feature Classes (except PLSS Points): This feature class is built from the PLSSIntersected feature through a series of SQL selects, dissolves and geoprocessing. The selection uses only the current PLS data so any polygon labeled with a survey note of R (replaced) will not be used in building derived feature classes. Polygons are combined based on the attributes and rules of combination. PLSS Points: For points with a BLM Cadastral as the data steward this feature class is built geographic coordinate database (GCDB) point files. All PLSS Points are at the nodes of line intersections and have a unique identifier as well as any applicable alias that represents the point identifier in adjoining townships or adjoining features. For points with county or state data stewards the PLSS corners are imported from geodatabase files provided by the data steward. Attribute_Accuracy_Report - The BLM GCDB personnel using software tools such as dataprep and native GS tools in ArcGIS checked the data for attribute accuracy by verifying it against land records databases such as legal land description (LLD) and Case Status databases. There may be instances where information in survey records and LLD and Case do not agree or places where records are missing. If there are questions about the attribution of a polygon contact the identified data steward. Horizontal_(Vertical) Positional_Accuracy_Report - For PLSSPoints: Accuracy of the individual points contained in the PLSSPoint Feature Class that were determined using GMM software the resulting accuracy is reported with the point in the feature class. An overall statement of reliability may be provided for points that are derived from the least accurate component of the error ellipse. Accuracy of the individual points that were determined using PCCS software a carries positional reliability factor for the average of the misclosures in the data set and the maximum misclosure in the data set. For Polygon Feature Classes: The polygon lines are built from the PLSS Points. The PLSS points should be at the nodes of the lines. The horizontal accuracy of the polygon lines is derived from the accuracy of the points at the nodes. Account Manager Premier Data Services S&P Global Premier Data Services S&P Global Account Manager (303) 377-0033

15 Inverness Way East Englewood CO 80112 US @ihsmarkit.com

pointOfContact The Arizona Office will need to be contacted for complete data processing details. Development of the data set by the agency / individuals identified in the 'Originator' element in the Identification Info section of the record. 2010-06-01T00:00:00 GIS Manager Arizona State Office, Bureau of Land Management GIS Manager (602) 417-9200 (602) 417-9556

One North Central Ave. Suite 800 Phoenix AZ 85004 US ASOWEB_AZ@blm.gov

Monday - Friday, 8 AM - 4 PM, Mountain Standard Time processor 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. online 2014-12-05 publication Release 1-1762 U.S. Department of Interior, Bureau of Land Management (BLM) originator CadNSDI Reference: https://nationalcad.org/download/PublicationHandbookOct2016.pdf publication date 2017 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. otherRestrictions None, these data are considered public domain. unclassified Unclassified Unclassified unknown Last metadata review date: 20190314