<?xml version="1.0" encoding="UTF-8"?><metadata xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gml="http://www.opengis.net/gml" xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:xlink="http://www.w3.org/1999/xlink">
<idinfo>
<citation>
<citeinfo>
<title>National Landscape Conservation System (NLCS) National Monuments (NM), National Conservation Areas (NCA), &amp; Similar Designations Data</title>
<origin>U.S. Department of Interior, Bureau of Land Management (BLM)</origin>
<pubdate>20161205</pubdate>
<pubinfo>
<publish>Bureau of Land Management</publish>
</pubinfo>
<onlink>https://gis.blm.gov/AZDownload/Products/Published/BLM_AZ_NLCS_NM_NCA.zip</onlink>
<geoform>vector digital data</geoform>
</citeinfo>
</citation>
<descript>
<abstract>This polygon featureclass depicts the boundaries of the Bureau of Land Management's (BLM's) National monuments (NMs), and National conservation areas (NCAs) in Arizona as part of the National Landscape Conservation System (NLCS) data standards. This featureclass also depicts similar land designations such as Cooperative Management and Protection Areas, Forest Reserves, and Outstanding Natural areas. The NLCS dataset is in progress as of April 30, 2019. Only the Gila Box Riparian NCA has completed the process of legal description, map creation, certification, and submittal to Congress. The remaining NMs and NCAs are awaiting the draft of legal descriptions. As legal descriptions are finalized and certified, the NLCS dataset may require updating to ensure that the spatial footprints of the NM and NCA boundary data match their respective legal descriptions. Once the boundaries are confirmed, no further changes to the NM/NCA boundary data should be made. Boundary changes can only be made through an amendment to the legal description and direct notification to Congress. With the exception of the Grand Canyon Parashant National Monument, proposed designation boundaries are included in the NLCS dataset. Please refer to process steps detailed in the Lineage section of this metadata for the efforts made by the Arizona BLM in 2019.</abstract>
<purpose>The National Land Conservation System (NLCS) dataset shows the boundaries of the National Monuments (NMs), National Conservation Areas (NCAs), and similar designations. Similar designations include Cooperative Management and Protection Areas, Forest Reserves, and Outstanding Natural Areas. Descriptions of each polygon type are detailed in the NLCS Implementation Guidelines (version 1.1, pg 21). The Antiquities Act of 1906 grants the President authority to designate national monuments in order to protect “objects of historic or scientific interest.” NCAs and similarly designated lands are designated by Congress to conserve, protect, enhance, and manage public lands for the benefit and enjoyment of present and future generations. In June 2000, the Bureau of Land Management (BLM) responded to growing concern over the loss of open space by creating the NLCS. The NLCS brings into a single system some of the BLM's premier designations. By putting these lands into an organized system, the BLM hopes to increase public awareness of the scientific, cultural, educational, ecological, and other values of these NM/NCA boundaries.
The Public Law (P.L.) 101-628 established Gila Box Riparian NCA; P.L. 106-538 established the Las Cienegas NCA (also Sonoita Valley Acquisition Planning District), and P.L. 100-696 established San Pedro Riparian NCA. Each of these laws required the BLM to file boundary legal descriptions and maps to Congress for each NCA. As of April 30, 2019, only the Gila Box Riparian National Conservation Area has completed legal description, map depiction, certification, and submission to Congress. All other NM/NCA have gone through review by Arizona field offices. Draft maps have been completed and are awaiting legal descriptions to be drafted with the exception of the Grand Canyon Parashant NM. All proposed boundaries are included in this dataset with the exception of the Grand Canyon Parashant NM boundary. When legal descriptions are finalized and certified, minor updates may be necessary to ensure that the geospatial depiction of the NM/NCA boundary data matches the legal descriptions, after which no further changes to the geospatial NM/NCA boundary data should be made.
The standards, format and language for the legal descriptions and boundary maps were developed during regular meetings of the NLCS Coordinator, geospatial specialists and the Cadastral Surveyors regarding Arizona NLCS data. Guidance was provided from Congressional required maps and legal boundary descriptions for the NLCS Designation Manual 6120 (March, 2010). Established through Presidential Proclamation, there is no requirement for BLM to file boundary legal descriptions or maps with Congress for the National Monument. However, the NLCS Coordinator and Cadastral Survey Chief decided that it was prudent to extend the boundary process to NMs.</purpose>
<supplinf>A published revision of the Department Manual 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).</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>20190430</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>In work</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc>-114.793</westbc>
<eastbc>-108.8823</eastbc>
<northbc>37.0118</northbc>
<southbc>31.2509</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>boundaries</themekey>
<themekey>environment</themekey>
<themekey>structure</themekey>
<themekey>location</themekey>
</theme>
<theme>
<themekt>BLM-THEME</themekt>
<themekey>Endangered</themekey>
<themekey>Facility</themekey>
<themekey>Geology</themekey>
<themekey>Geospatial</themekey>
<themekey>Management</themekey>
<themekey>Paleontology</themekey>
<themekey>Recreation</themekey>
<themekey>Vegetation</themekey>
<themekey>Wildlife</themekey>
<themekey>Withdrawal</themekey>
</theme>
<place>
<placekt>BLM-STATE</placekt>
<placekey>Arizona</placekey>
</place>
<theme>
<themekt>BLM-AZData</themekt>
<themekey>BLM</themekey>
<themekey>NLCS</themekey>
<themekey>NM</themekey>
<themekey>NCA</themekey>
<themekey>National Monuments</themekey>
<themekey>National Conservation Area</themekey>
<themekey>public lands</themekey>
<themekey>congressional</themekey>
<themekey>jurisdiction</themekey>
<themekey>withdrawal</themekey>
</theme>
<place>
<placekt>Reference-State</placekt>
<placekey>Western States</placekey>
<placekey>United States</placekey>
</place>
</keywords>
<accconst>None, these data are considered public domain.</accconst>
<useconst>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.</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</ptcontac>
<datacred>BLM-AZ</datacred>
<secinfo>
<secsys>Not classified.</secsys>
<secclass>Unclassified</secclass>
<sechandl>Not classified.</sechandl>
</secinfo>
<native>Esri ArcGIS 10.3.1.4959</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>The NLCS NM/NCA polygon footprints are derived from the NM/NCA arcs. For each NM/NCA a proposed boundary line (arc) was prepared by a geospatial specialist. The legislative or proclamation map was the primary determinate for boundary placement. For comparative purposes these maps were digitized and georeferenced. This was particularly important as the small scale and thickness hand drawn line on the legislative map, meant that there was some latitude for interpreting the intent of boundary placement. How the boundary had been depicted and managed since the NM/NCA had been established was carefully considered. NM/NCA Management Plans were consulted for boundary descriptions and to establish which trails, range, and wildlife improvements were contained within Wilderness Areas. Master Title Plats were checked for any mineral claims or right-of-ways which might affect the boundary. These were researched for current authorization and the serial casefile noted in the NM/NCA boundary arc attribute table.
Please contact the GIS Manager for additional information on provenance, history, accuracy and quality of Arizona's state datasets.</attraccr>
</attracc>
<logic>Foundational to the this data is the expectation that it topologically align where possible and appropriate with the official published version of Bureau of Land Management (BLM) Public Land Survey System (PLSS) Cadastral National Spatial Data Infrastructure (CAD NSDI) GIS Data. The 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.3. 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.</logic>
<complete>This dataset is considered in progress for the information presented. Inconsistencies may still be present in the data. As of April 30, 2019, only the Gila Box Riparian National Conservation Area has completed legal description, map depiction, certification, and submission to Congress. All other NM/NCA have gone through review by Arizona field offices. Draft maps have been completed and are awaiting legal descriptions to be drafted with the exception of the Grand Canyon Parashant National Monument.
Maintenance to be performed as needed under the guidance of subject matter experts and/or NLCS leads to ensure legal descriptions and Congressional status are maintained.</complete>
<posacc>
<horizpa>
<horizpar>This data's spatial accuracy can be found from the reliability and/or the error in X, Y coordinates contained in the PLSS Points feature class. This represents the best estimate of spatial accuracy on a point-by-point basis. In addition, proposed boundaries were reviewed by the NLCS Coordinator, Field Office Managers, Recreation Specialists, Archaeologists, and Cadastral Surveyors as appropriate.</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Department of Interior, Bureau of Land Management (BLM)</origin>
<pubdate>20141205</pubdate>
<title>H-1283-2 Data Administration and Management Handbook</title>
<edition>Release 1-1762</edition>
<onlink>http://web.blm.gov/internal/wo-500/directives/dir-hdbk/h1283-2.pdf</onlink>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20141205</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>Bureau of Land Management Data</srccitea>
<srccontr>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.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>U.S. Department of Interior, Bureau of Land Management (BLM)</origin>
<pubdate>20100305</pubdate>
<title>Bureau of Land Management (BLM) Manual 6120 - Congressionally Required Maps and Legal Boundary Descriptions for National Landscape Conservation System Designations</title>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
<srccontr>Direction is provided to implement Bureau of Land Management (BLM) Manual 6120 - Congressionally Required Maps and Legal Boundary Descriptions for National Landscape Conservation System Designations.</srccontr>
</srcinfo>
<procstep>
<procdesc>Using the implementation guidelines, GIS-skilled staff at BLMAZ State office working with the State office Program Manager, cross-walked and cleaned up data to comply with the standardized national dataset. It was produced into a seamless state dataset. Alterations of the congressionally-established boundaries are updated after being established in LR2000 and MTPs.
Alterations of the congressionally-established boundaries are updated after being established in LR2000 and MTPs.</procdesc>
<srcused>withheld</srcused>
<procdate>20141205</procdate>
<proccont>
<cntinfo>
<cntperp>
<cntper>GIS Manager</cntper>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
</cntperp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>One North Central Avenue, Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>USA</country>
</cntaddr>
<cntvoice>(602) 417- 9200</cntvoice>
<cnttdd>(602) 417- 9200</cnttdd>
<cntfax>(602) 417- 9588</cntfax>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM - 4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>A proposed boundary line was prepared for each NM/NCA by a GIS specialist. The legislative or proclamation map was the primary determinate for boundary placement. These boundary lines were used to derive the polygon footprint for the featureclass "nlcs_nm_nca_poly".
Small scale and thickness of hand-drawn lines on legislative maps left some latitude for interpreting the intent of boundary placement. Therefore, proclamation maps were digitized and georeferenced for comparative purposes.
The legacy management and depiction of each boundary was carefully considered. NM and NCA Management Plans were consulted for boundary descriptions and to identify trails, range improvements, and wildlife improvements contained within Wilderness Areas.</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Master Title Plats (MTPs) were reviewed for existing mineral claims and/or rights-of-ways that might affect boundary placement. MTP depictions were researched for current authorization and the serial casefile was noted in the nm_nca_arc attribute table.</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Google Earth was used to digitize the features that would eventually form the wilderness boundary. Boundary lines were tied to features on the ground whenever possible. Google image resolution allowed clear feature identification, e.g. the bases of powerline posts were identified and used to create the appropriate rights-of-way. Surveyors performed groundtruthing efforts and set monuments to establish coordinates. Coordinates derived from Google's keyhole markup language (KML) files proved accurate to surveying results. Constantly improving resolution, rapid data reload, and the ability to view in different angles and directions was advantageous. Any initial concerns over Google Earth’s lack of metadata and potential for inaccuracy were unfounded.</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>To ensure appropriate placement, the proposed boundaries were reviewed on multiple occasions by the NLCS Coordinator, field fffice managers, Wilderness and recreation specialists, realty specialists where appropriate, archaeologists; and cadastral surveyors.</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Angle point data were constructed for each boundary with instruction from surveyors. These angle points are described in each boundary's legal description. This process was only initiated after boundaries were approved by appropriate reviewers. NM and NCA boundary polygons are based on the boundary arcs which are segmented and attributed to define feature-level metadata.</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>In Arizona, each NCA/NM boundary arc is segmented and attributed to describe features which form the boundary. This data color coded and annotated was used on the Coded Copy Maps. Coded Copy Maps are a visual representation of each wilderness boundary legal description). To achieve the necessary level of description four 'AZ only' attribute fields were added to nlcs_nm-nca_arc National Data Standard attribute table. These four fields are described as follows 1. "Wilderness Name": Name assists in search of area
2. Annotation: Standard phrases describing boundary features. (e.g. "On section line" "Follows easterly edge of wash" "30ft setback from road center" etc_
3. Detail: Varied comments for additional information. (e.g. feature name, serialized case file number and row, and decision comments)
4. Source: References to documents, digitization source, and digitization date</procdesc>
<procdate>201904</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<esriterm Name="nlcs_nm_nca_poly">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">TRUE</esritopo>
<efeacnt Sync="TRUE">8</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
<XYRank Sync="TRUE">1</XYRank>
<ZRank Sync="TRUE">1</ZRank>
<topoWeight Sync="TRUE">1.000000</topoWeight>
<validateEvents Sync="TRUE">FALSE</validateEvents>
<partTopoRules>
<topoRuleID Sync="TRUE">2</topoRuleID>
</partTopoRules>
<partTopoRules>
<topoRuleID Sync="TRUE">4</topoRuleID>
</partTopoRules>
<partTopoRules>
<topoRuleID Sync="TRUE">5</topoRuleID>
</partTopoRules>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.0</semiaxis>
<denflat>298.257222101</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altres>0.000100</altres>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed Name="nlcs_nm_nca_poly">
<enttyp>
<enttypl>nlcs_nm_nca_poly</enttypl>
<enttypd>The polygon features for the NLCS National Monuments, National Conservation Areas and similar designations</enttypd>
<enttypds>National Landscape Conservation System (NLCS) Implementation Guidelines</enttypds>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">8</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>NLCS_ID</attrlabl>
<attrdef>The designed primary key that will uniquely identify a single occurrence of the entity.</attrdef>
<attrdefs>National Landscape Conservation System (NLCS) Implementation Guidelines</attrdefs>
<attalias>NLCS Unique Identifier</attalias>
<attrtype>String</attrtype>
<attwidth>10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NLCS_NAME</attrlabl>
<attrdef>The name of a nationally significant designated area with scientific, cultural, educational, ecological and other values.</attrdef>
<attrdefs>National Landscape Conservation System (NLCS) Implementation Guidelines</attrdefs>
<attalias>NLCS Name</attalias>
<attrtype>String</attrtype>
<attwidth>100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>CASEFILE_NO</attrlabl>
<attrdef>The number that refers to the serialized case file number of the group of official documents that record the facts, or actions taken, on a specific application, such as an oil and gas lease, exchange, airport lease, easement acquisition, etc.</attrdef>
<attrdefs>National Landscape Conservation System (NLCS) Implementation Guidelines</attrdefs>
<attalias>Case File Number</attalias>
<attrtype>String</attrtype>
<attwidth>17</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NLCS_TYPE</attrlabl>
<attrdef>The name that indicates the type of the BLM's nationally significant designated areas.</attrdef>
<attrdefs>National Landscape Conservation System (NLCS) Implementation Guidelines</attrdefs>
<attalias>Designation</attalias>
<attrtype>String</attrtype>
<attwidth>50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ADMIN_ST</attrlabl>
<attrdef>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</attrdef>
<attrdefs>National Landscape Conservation System (NLCS) Implementation Guidelines</attrdefs>
<attalias>Administrative State Code</attalias>
<attrtype>String</attrtype>
<attwidth>2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>created_user</attrlabl>
<attrdef>The name of the field that will store the names of users who created features or records. If this field already exists, it must be a String field. </attrdef>
<attrdefs>ESRI</attrdefs>
<attalias>created_user</attalias>
<attrtype>String</attrtype>
<attwidth>255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>created_date</attrlabl>
<attrdef>The date (UTC) in which the feature within the feature class of a geodatabase was created.</attrdef>
<attrdefs>ESRI</attrdefs>
<attalias>created_date</attalias>
<attrtype>Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>last_edited_user</attrlabl>
<attrdef>The name of the user who most recently updated the feature within the feature class of a geodatabase.</attrdef>
<attrdefs>ESRI</attrdefs>
<attalias>last_edited_user</attalias>
<attrtype>String</attrtype>
<attwidth>255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>last_edited_date</attrlabl>
<attrdef>The date (UTC) in which the feature within the feature class of a geodatabase was most recently edited.</attrdef>
<attrdefs>ESRI</attrdefs>
<attalias>last_edited_date</attalias>
<attrtype>Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Original_GlobalID</attrlabl>
<attrdef>Original global ID value generated when record was established.</attrdef>
<attrdefs>Arizona State Office. Bureau of Land Management</attrdefs>
<attalias>Original_GlobalID</attalias>
<attrtype>String</attrtype>
<attwidth>50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>GlobalID</attrlabl>
<attrdef>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.</attrdef>
<attrdefs>ESRI</attrdefs>
<attalias>GlobalID</attalias>
<attrtype>UUID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STArea()</attrlabl>
<attalias Sync="TRUE">Shape.STArea()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Software generated area of a polygon. </attrdef>
<attrdefs>ESRI</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STLength()</attrlabl>
<attalias Sync="TRUE">Shape.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Software generated length of a line string or multiline string.</attrdef>
<attrdefs>ESRI</attrdefs>
</attr>
</detailed>
<overview>
<eaover>Please see the National Landscape Conservation System (NLCS) Implementation Guidelines for information regarding the National data standards for this feature-dataset.</eaover>
</overview>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>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.</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>ESRI Layer Package (LPK)</formname>
<formvern>10</formvern>
</digtinfo>
</digform>
<ordering>Contact GIS Manager for product information and ordering instructions.</ordering>
</stdorder>
<techpreq>Geospatial software.</techpreq>
<availabl>
<timeinfo>
<sngdate>
<caldate>20161205</caldate>
</sngdate>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd>20161205</metd>
<metrd>20200901</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Arizona State Office, Bureau of Land Management</cntorg>
<cntper>GIS Manager</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>One North Central Ave. Suite 800</address>
<city>Phoenix</city>
<state>AZ</state>
<postal>85004</postal>
<country>United States</country>
</cntaddr>
<cntemail>ASOWEB_AZ@blm.gov</cntemail>
<hours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</hours>
</cntinfo>
</metc>
<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metac>None.</metac>
<metuc>None, these data are considered public domain.</metuc>
</metainfo>
<Esri>
<DataProperties>
<itemProps>
<itemName>nlcs_nm_nca_poly</itemName>
<nativeExtBox>
<westBL>226054.592600</westBL>
<eastBL>658288.043100</eastBL>
<southBL>3466942.794600</southBL>
<northBL>4095491.592600</northBL>
<exTypeCode>1</exTypeCode>
</nativeExtBox>
<imsContentType export="False">002</imsContentType>
</itemProps>
<coordRef>
<type>Projected</type>
<geogcsn>GCS_North_American_1983</geogcsn>
<csUnits>Linear Unit: Meter (1.000000)</csUnits>
<projcsn>NAD_1983_UTM_Zone_12N</projcsn>
<peXml>&lt;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/10.7'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_UTM_Zone_12N&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Transverse_Mercator&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,500000.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-111.0],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.9996],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,26912]]&lt;/WKT&gt;&lt;XOrigin&gt;-5120900&lt;/XOrigin&gt;&lt;YOrigin&gt;-9998100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;26912&lt;/WKID&gt;&lt;LatestWKID&gt;26912&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20221121</SyncDate>
<SyncTime>14553200</SyncTime>
<ModDate>20221121</ModDate>
<ModTime>14553200</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<CreaDate>20240119</CreaDate>
<CreaTime>18152500</CreaTime>
<SyncOnce>TRUE</SyncOnce>
</Esri>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
<cntPhone>
<voiceNum>(602) 417-9200 </voiceNum>
<faxNum>(602) 417-9556</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20221121</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
<cntPhone>
<voiceNum>(602) 417-9200 </voiceNum>
<faxNum>(602) 417-9556</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://gbp-blm-egis.hub.arcgis.com/pages/arizona </linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<themeKeys>
<thesaName>
<resTitle>BLM-AZData</resTitle>
</thesaName>
<keyword>BLM</keyword>
<keyword>boundary</keyword>
<keyword>congressional</keyword>
<keyword>jurisdiction</keyword>
<keyword>National Conservation Area</keyword>
<keyword>National Monuments</keyword>
<keyword>NCA</keyword>
<keyword>NLCS</keyword>
<keyword>NM</keyword>
<keyword>public lands</keyword>
</themeKeys>
<placeKeys>
<thesaName>
<resTitle>BLM-STATE</resTitle>
</thesaName>
<keyword>Arizona</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>BLM-THEME</resTitle>
</thesaName>
<keyword>Endangered</keyword>
<keyword>Facility</keyword>
<keyword>Geology</keyword>
<keyword>Geospatial</keyword>
<keyword>Management</keyword>
<keyword>Paleontology</keyword>
<keyword>Recreation</keyword>
<keyword>Vegetation</keyword>
<keyword>Wildlife</keyword>
<keyword>Withdrawal</keyword>
</themeKeys>
<placeKeys>
<thesaName>
<resTitle>Reference-State</resTitle>
</thesaName>
<keyword>AZ</keyword>
<keyword>United States</keyword>
<keyword>Western States</keyword>
</placeKeys>
<idCitation>
<resTitle>National Landscape Conservation System (NLCS) National Monuments (NM), National Conservation Areas (NCA), &amp; Similar Designations Polygon</resTitle>
<date>
<pubDate>20220225</pubDate>
</date>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<citRespParty>
<rpIndName>U.S. Department of the Interior, Bureau of Land Management (BLM)</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
<cntPhone>
<voiceNum>(602) 417-9200 </voiceNum>
<faxNum>(602) 417-9556</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="006"/>
</role>
<displayName>Name: GIS Manager
Organization: Arizona State Office, Bureau of Land Management
Position: GIS Manager
Role: Point of Contact</displayName>
</citRespParty>
<citRespParty>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
<cntPhone>
<voiceNum>(602) 417-9200 </voiceNum>
<faxNum>(602) 417-9556</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
<displayName>Name: GIS Manager
Organization: Arizona State Office, Bureau of Land Management
Position: GIS Manager
Role: Point of Contact</displayName>
</citRespParty>
</idCitation>
<idAbs> This feature class also depicts similar land designations such as Cooperative Management and Protection Areas, Forest Reserves, and Outstanding Natural areas. The NLCS dataset is in progress as of April 30, 2019. Only the Gila Box Riparian NCA has completed the process of legal description, map creation, certification, and submittal to Congress. The remaining NMs and NCAs are awaiting the draft of legal descriptions. As legal descriptions are finalized and certified, the NLCS dataset may require updating to ensure that the spatial footprints of the NM and NCA boundary data match their respective legal descriptions. Once the boundaries are confirmed, no further changes to the NM/NCA boundary data should be made. Boundary changes can only be made through an amendment to the legal description and direct notification to Congress. With the exception of the Grand Canyon Parashant National Monument, proposed designation boundaries are included in the NLCS dataset. Please refer to process steps detailed in the Lineage section of this metadata for the efforts made by the Arizona BLM in 2019.
The National Land Conservation System (NLCS) dataset shows the boundaries of the National Monuments (NMs), National Conservation Areas (NCAs), and similar designations. Similar designations include Cooperative Management and Protection Areas, Forest Reserves, and Outstanding Natural Areas. Descriptions of each polygon type are detailed in the NLCS Implementation Guidelines (version 1.1, pg 21). The Antiquities Act of 1906 grants the President authority to designate national monuments in order to protect “objects of historic or scientific interest.” NCAs and similarly designated lands are designated by Congress to conserve, protect, enhance, and manage public lands for the benefit and enjoyment of present and future generations. In June 2000, the Bureau of Land Management (BLM) responded to growing concern over the loss of open space by creating the NLCS. The NLCS brings into a single system some of the BLM's premier designations. By putting these lands into an organized system, the BLM hopes to increase public awareness of the scientific, cultural, educational, ecological, and other values of these NM/NCA boundaries.
The Public Law (P.L.) 101-628 established Gila Box Riparian NCA; P.L. 106-538 established the Las Cienegas NCA (also Sonoita Valley Acquisition Planning District), and P.L. 100-696 established San Pedro Riparian NCA. Each of these laws required the BLM to file boundary legal descriptions and maps to Congress for each NCA. As of April 30, 2019, only the Gila Box Riparian National Conservation Area has completed legal description, map depiction, certification, and submission to Congress. All other NM/NCA have gone through review by Arizona field offices. Draft maps have been completed and are awaiting legal descriptions to be drafted with the exception of the Grand Canyon Parashant NM. All proposed boundaries are included in this dataset with the exception of the Grand Canyon Parashant NM boundary. When legal descriptions are finalized and certified, minor updates may be necessary to ensure that the geospatial depiction of the NM/NCA boundary data matches the legal descriptions, after which no further changes to the geospatial NM/NCA boundary data should be made.
The standards, format and language for the legal descriptions and boundary maps were developed during regular meetings of the NLCS Coordinator, geospatial specialists and the Cadastral Surveyors regarding Arizona NLCS data. Guidance was provided from Congressional required maps and legal boundary descriptions for the NLCS Designation Manual 6120 (March, 2010). Established through Presidential Proclamation, there is no requirement for BLM to file boundary legal descriptions or maps with Congress for the National Monument. However, the NLCS Coordinator and Cadastral Survey Chief decided that it was prudent to extend the boundary process to NMs.</idAbs>
<idPurp>This polygon feature class depicts the boundaries of the Bureau of Land Management's (BLM's) National monuments (NMs), and National conservation areas (NCAs) in Arizona as part of the National Landscape Conservation System (NLCS) data standards. </idPurp>
<idCredit>Bureau of Land Management, Arizona</idCredit>
<idStatus>
<ProgCd value="004"/>
</idStatus>
<idPoC>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
<cntPhone>
<voiceNum>(602) 417-9200 </voiceNum>
<faxNum>(602) 417-9556</faxNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<searchKeys>
<keyword>Arizona</keyword>
<keyword>AZ</keyword>
<keyword>BLM</keyword>
<keyword>boundaries</keyword>
<keyword>boundary</keyword>
<keyword>congressional</keyword>
<keyword>Endangered</keyword>
<keyword>environment</keyword>
<keyword>Facility</keyword>
<keyword>Geology</keyword>
<keyword>geoscientificInformation</keyword>
<keyword>Geospatial</keyword>
<keyword>jurisdiction</keyword>
<keyword>location</keyword>
<keyword>Management</keyword>
<keyword>National Conservation Area</keyword>
<keyword>National Monuments</keyword>
<keyword>NCA</keyword>
<keyword>NLCS</keyword>
<keyword>NM</keyword>
<keyword>Paleontology</keyword>
<keyword>public lands</keyword>
<keyword>Recreation</keyword>
<keyword>structure</keyword>
<keyword>United States</keyword>
<keyword>Vegetation</keyword>
<keyword>Western States</keyword>
<keyword>Wildlife</keyword>
<keyword>Withdrawal</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>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.</useLimit>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>None, these data are considered public domain.</othConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Not classified.</classSys>
<handDesc>Not classified.</handDesc>
</SecConsts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<envirDesc>Esri ArcGIS 10.3.1.4959</envirDesc>
<suppInfo>A published revision of the Department Manual 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).</suppInfo>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-114.077071</westBL>
<eastBL Sync="TRUE">-109.221264</eastBL>
<northBL Sync="TRUE">37.005582</northBL>
<southBL Sync="TRUE">31.304652</southBL>
</GeoBndBox>
</geoEle>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>20220225</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<tpCat>
<TopicCatCd value="003"/>
</tpCat>
<tpCat>
<TopicCatCd value="007"/>
</tpCat>
<tpCat>
<TopicCatCd value="008"/>
</tpCat>
<tpCat>
<TopicCatCd value="013"/>
</tpCat>
<tpCat>
<TopicCatCd value="017"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<maintNote>Last metadata review date: 20200901</maintNote>
</mdMaint>
<mdConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</mdConst>
<mdConst>
<LegConsts>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>None, these data are considered public domain.</othConsts>
</LegConsts>
</mdConst>
<dqInfo>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>This data's spatial accuracy can be found from the reliability and/or the error in X, Y coordinates contained in the PLSS Points feature class. This represents the best estimate of spatial accuracy on a point-by-point basis. In addition, proposed boundaries were reviewed by the NLCS Coordinator, Field Office Managers, Recreation Specialists, Archaeologists, and Cadastral Surveyors as appropriate.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>The NLCS NM/NCA polygon footprints are derived from the NM/NCA arcs. For each NM/NCA a proposed boundary line (arc) was prepared by a geospatial specialist. The legislative or proclamation map was the primary determinate for boundary placement. For comparative purposes these maps were digitized and georeferenced. This was particularly important as the small scale and thickness hand drawn line on the legislative map, meant that there was some latitude for interpreting the intent of boundary placement. How the boundary had been depicted and managed since the NM/NCA had been established was carefully considered. NM/NCA Management Plans were consulted for boundary descriptions and to establish which trails, range, and wildlife improvements were contained within Wilderness Areas. Master Title Plats were checked for any mineral claims or right-of-ways which might affect the boundary. These were researched for current authorization and the serial casefile noted in the NM/NCA boundary arc attribute table.
Please contact the GIS Manager for additional information on provenance, history, accuracy and quality of Arizona's state datasets.</measDesc>
</report>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Foundational to the this data is the expectation that it topologically align where possible and appropriate with the official published version of Bureau of Land Management (BLM) Public Land Survey System (PLSS) Cadastral National Spatial Data Infrastructure (CAD NSDI) GIS Data. The 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.3. 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.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>This dataset is considered in progress for the information presented. Inconsistencies may still be present in the data. As of April 30, 2019, only the Gila Box Riparian National Conservation Area has completed legal description, map depiction, certification, and submission to Congress. All other NM/NCA have gone through review by Arizona field offices. Draft maps have been completed and are awaiting legal descriptions to be drafted with the exception of the Grand Canyon Parashant National Monument.
Maintenance to be performed as needed under the guidance of subject matter experts and/or NLCS leads to ensure legal descriptions and Congressional status are maintained.</measDesc>
</report>
<dataLineage>
<dataSource>
<srcDesc>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.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>H-1283-2 Data Administration and Management Handbook</resTitle>
<resAltTitle>Bureau of Land Management Data</resAltTitle>
<date>
<pubDate>2014-12-05</pubDate>
</date>
<resEd>Release 1-1762</resEd>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Land Management (BLM)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citOnlineRes>
<linkage>http://web.blm.gov/internal/wo-500/directives/dir-hdbk/h1283-2.pdf</linkage>
</citOnlineRes>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2014-12-05</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Direction is provided to implement Bureau of Land Management (BLM) Manual 6120 - Congressionally Required Maps and Legal Boundary Descriptions for National Landscape Conservation System Designations.</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Bureau of Land Management (BLM) Manual 6120 - Congressionally Required Maps and Legal Boundary Descriptions for National Landscape Conservation System Designations</resTitle>
<date>
<pubDate>2010-03-05</pubDate>
</date>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Land Management (BLM)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</srcCitatn>
</dataSource>
<prcStep>
<stepDesc>Using the implementation guidelines, GIS-skilled staff at BLMAZ State office working with the State office Program Manager, cross-walked and cleaned up data to comply with the standardized national dataset. It was produced into a seamless state dataset. Alterations of the congressionally-established boundaries are updated after being established in LR2000 and MTPs.
Alterations of the congressionally-established boundaries are updated after being established in LR2000 and MTPs.</stepDesc>
<stepDateTm>2014-12-05</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(602) 417- 9200</voiceNum>
<voiceNum tddtty="True">(602) 417- 9200</voiceNum>
<faxNum>(602) 417- 9588</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>One North Central Avenue, Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM - 4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Bureau of Land Management Data</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>A proposed boundary line was prepared for each NM/NCA by a GIS specialist. The legislative or proclamation map was the primary determinate for boundary placement. These boundary lines were used to derive the polygon footprint for the feature class "nlcs_nm_nca_poly".
Small scale and thickness of hand-drawn lines on legislative maps left some latitude for interpreting the intent of boundary placement. Therefore, proclamation maps were digitized and georeferenced for comparative purposes.
The legacy management and depiction of each boundary was carefully considered. NM and NCA Management Plans were consulted for boundary descriptions and to identify trails, range improvements, and wildlife improvements contained within Wilderness Areas.</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Master Title Plats (MTPs) were reviewed for existing mineral claims and/or rights-of-ways that might affect boundary placement. MTP depictions were researched for current authorization and the serial casefile was noted in the nm_nca_arc attribute table.</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Google Earth was used to digitize the features that would eventually form the wilderness boundary. Boundary lines were tied to features on the ground whenever possible. Google image resolution allowed clear feature identification, e.g. the bases of powerline posts were identified and used to create the appropriate rights-of-way. Surveyors performed groundtruthing efforts and set monuments to establish coordinates. Coordinates derived from Google's keyhole markup language (KML) files proved accurate to surveying results. Constantly improving resolution, rapid data reload, and the ability to view in different angles and directions was advantageous. Any initial concerns over Google Earth’s lack of metadata and potential for inaccuracy were unfounded.</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>To ensure appropriate placement, the proposed boundaries were reviewed on multiple occasions by the NLCS Coordinator, field fffice managers, Wilderness and recreation specialists, realty specialists where appropriate, archaeologists; and cadastral surveyors.</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Angle point data were constructed for each boundary with instruction from surveyors. These angle points are described in each boundary's legal description. This process was only initiated after boundaries were approved by appropriate reviewers. NM and NCA boundary polygons are based on the boundary arcs which are segmented and attributed to define feature-level metadata.</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>In Arizona, each NCA/NM boundary arc is segmented and attributed to describe features which form the boundary. This data color coded and annotated was used on the Coded Copy Maps. Coded Copy Maps are a visual representation of each wilderness boundary legal description). To achieve the necessary level of description four 'AZ only' attribute fields were added to nlcs_nm-nca_arc National Data Standard attribute table. These four fields are described as follows 1. "Wilderness Name": Name assists in search of area
2. Annotation: Standard phrases describing boundary features. (e.g. "On section line" "Follows easterly edge of wash" "30ft setback from road center" etc_
3. Detail: Varied comments for additional information. (e.g. feature name, serialized case file number and row, and decision comments)
4. Source: References to documents, digitization source, and digitization date</stepDesc>
<stepDateTm>2019-04</stepDateTm>
<stepProc>
<rpIndName>GIS Manager</rpIndName>
<rpOrgName>Arizona State Office, Bureau of Land Management</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>One North Central Ave. Suite 800</delPoint>
<city>Phoenix</city>
<adminArea>AZ</adminArea>
<postCode>85004</postCode>
<country>US</country>
<eMailAdd>ASOWEB_AZ@blm.gov</eMailAdd>
</cntAddress>
<cntHours>Monday-Friday, 8 AM-4 PM, Mountain Standard Time</cntHours>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="nlcs_nm_nca_poly">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">8</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="004"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="26912"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.13(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<Binary>
<Thumbnail>
<Data EsriPropertyType="PictureX">/9j/4AAQSkZJRgABAQEAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACFAMgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iii
gAooooAKKKKACiiqUxnu53t4ZXgijIEkq43McZ2rkHHBGT+XqGlcC7RVLTp3f7RbSyebJbSeWZMf
fGAwJxxuwRn35wARV2hqzsAVDcXMVsE80t+8bYoVCxJwT0APYGpqq3cEzy280IjZoWY7JGKg5UjO
QDgj6HgmiKTeoDo72GSQR/vFY9PMiZAfYFgAT7VYqjDayzXQu71It6jEMajd5Xqdx6sfUAccc9Te
pySWwBRRRUgFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAVkx6lbWmpajBdypb4ZJVaV
giuhQDIJPOCpB/CtamvFHKpWRFcFSpDDOQeo+lVFpbgZt5amNmltdT+wm4YAghWR3OACA38WBgAH
BPJBqvpMFxJqk1413PJCgkt2WS4373DgBtgUIhAU/d67ueQa5keD307xZYWUUU1x4bnWR5LMuzW8
UikMm5DkADCBRnkgnAxmu/hhjt4UhhQJGihVVRwAO1dFXlhFKLvfyJQ+iiiuUoKKKKACiiigAooo
oAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiig
AooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiq0t/bQ30Fk7kXE4JjUIxBAGTkgYHTv
TSb2As0UUUgCiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKz2sp3
1oXbPGIFVdoXO5iA4we2PnY8deOmOdCimpNbAFFFFIAooooAKKKKACiiigAooooAKKKKACiiigAo
oooAKKKKACiiigAooooAKKKKAIBeW5ujbeaBMP4TxngHj14I6dM1PWJaxyXdrqkchhkgE8ghEQzI
jAnO7Jxuzgjp2+tXbDUY7mGFZZYlunBJh+64+qEkg46jnFaShbYVy9RRRWYwooooAKKKxtPn119S
mt7u0t1tIZGAuvM+adTypVR0wCFbOOQccVUY3TfYDZoooqQCiiigAooooAKKKKACiiigAooooAKK
KKACiiigAooooAq3FhFPJ5ys8NxjAmiOGx6Hsw9iD1pIbEJP9onkM1xk4Y8KgPZV6Dp9ferdFVzO
1gOf0/X/ANw5vZTJczXLxwW8cRU5XgxgnAJBVjnP8q2rW5ivbSG6gcPFKgdGHcGqt1pVrLBKsNpb
q8rrI52Bd5DBjkgZ5x1p2k21zZ6fHbXLRsYgEj2En5AAACTjJ98CtJ8jV46CVy9RRRWIwooooAKK
KKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigDF8Ta7/YGm/aBCXZ22K7
A+Wh9XI6d8dATgZGc1LPrSJHpFxGEa2v5FTduDEB0LKRtyDzgZBI5z05rTdQ6MhJAYEZU4I+hrG8
QWRHhaaK3d/NtUSSF2LM+6MhhzycnbjPJ571tDkdota3/P8AyEzbopASVBIwccj0paxGFFFFABRR
RQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFF
ABRRRQB//9k=</Data>
</Thumbnail>
</Binary>
</metadata>
