<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20101208</CreaDate>
<CreaTime>16373000</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<ArcGISFormat>1.0</ArcGISFormat>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">CONS_NCED</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">929390.002700</westBL>
<eastBL Sync="TRUE">2250593.312000</eastBL>
<southBL Sync="TRUE">1585898.352400</southBL>
<northBL Sync="TRUE">3009906.370100</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet</projcsn>
<peXml Sync="TRUE">&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/2.4.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_Rhode_Island_FIPS_3800_Feet&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;,328083.3333333333],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-71.5],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.99999375],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,41.08333333333334],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,3438]]&lt;/WKT&gt;&lt;XOrigin&gt;-18120300&lt;/XOrigin&gt;&lt;YOrigin&gt;-47742100&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121928&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.0032808333333333331&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;102730&lt;/WKID&gt;&lt;LatestWKID&gt;3438&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
</coordRef>
</DataProperties>
<SyncDate>20191002</SyncDate>
<SyncTime>07441700</SyncTime>
<ModDate>20191002</ModDate>
<ModTime>07441700</ModTime>
<ArcGISProfile>ISO19139</ArcGISProfile>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Allison Anderson</rpIndName>
<rpOrgName>Conservation Biology Institute</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>425-286-6749</voiceNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Ty Montgomery</rpIndName>
<rpOrgName>The Other Firm</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>503-336-5359</voiceNum>
</cntPhone>
<cntInstr>For more information about the NCED portal, please contact: 1) NCED Portal - General Inquiries Kassandra Kelly Defenders of Wildlife kkelly@defenders.org 503-697-3222 2) NCED Portal - Technical Inquiries Ty Montgomery The Other Firm ty@theotherfirm.com 503-336-5359</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>none</resFees>
<ordInstr>The main site for viewing, summarizing, and downloading the NCED database is the NCED Portal. The NCED Portal was based on Defenders of Wildlife's Conservation Registry web portal and allows the user to perform data queries, reporting, and data downloads; as well as digitize conservation easements. The NCED database will also be available on other partner web sites: Conservation Registry (DoW) CARL (DU) - http://www.ducks.org/conservation/glaro/carl-gis-layer LandScope America (NatureServe) - http://www.landscope.org/ Conservation Almanac (TPL) - http://www.conservationalmanac.org/ Data Basin Protected Areas Center (CBI) - http://databasin.org/protected-center</ordInstr>
</distorOrdPrc>
<distorTran>
<onLineSrc>
<orDesc>National Conservation Easement Database (NCED)</orDesc>
</onLineSrc>
</distorTran>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>http://www.conservationeasement.us/</linkage>
</onLineSrc>
</distTranOps>
<distTranOps>
<onLineSrc>
<linkage>http://www.conservationeasement.us</linkage>
<orDesc>The NCED's primary publication outlet is the NCED Portal (http://www.conservationeasement.us), a dedicated resource built as an extension of The Conservation Registry (http://www.conservationregistry.org).</orDesc>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="FALSE">CONS_NCED</resTitle>
<date>
<pubDate>20110801</pubDate>
</date>
<citRespParty>
<rpOrgName>National Conservation Easement Database</rpOrgName>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<resEdDate>20110801</resEdDate>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The National Conservation Easement Database (NCED) is a collaborative venture to compile easement records (both spatial and tabular) from land trusts and public agencies throughout the United States in a single, up-to-date, sustainable, GIS compatible, online source. The goal of the NCED is to provide a comprehensive picture of the estimated 20 million acres of privately owned conservation easement lands, recognizing their contribution to America's natural heritage, a vibrant economy, and healthy communities. Conservation easements are legal agreements voluntarily entered into between landowners and conservation entities (agencies or land trusts) for the express purpose of protecting certain societal values such as open space or vital wildlife habitats. In some cases landowners transfer "development rights" for direct payment or for federal and state tax benefits.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>NCED will for the first time show a comprehensive picture of privately owned conservation easement lands in the U.S. The NCED will allow better strategic planning for conservation and development by merging data on land protection with biodiversity and resources, improving ecological and economic plans and investments. State and regional planners and managers will appreciate this dataset as it provides critical contextual information for their work. Institutions responsible for national and international reporting will find this database full of reliable, accurate information for their purposes. The scientific and conservation community will similarly benefit from having this standardized base map to carry out their research and planning objectives.</idPurp>
<idCredit>The NCED project partners would like to thank the U.S. Endowment for Forestry and Communities for their leadership and forethought for putting the NCED team together and for the initial funding that allowed the NCED to be formed. Additional support for the NCED project was provided by the Gaylord and Dorothy Donnelley Foundation and the Knobloch Family Foundation. We would also like to thank Greg Schildwachter for his leadership skills in guiding the project partners through this two-year journey. While the NCED partners were responsible for aggregating conservation easements from across the country, the NCED database would not have been successful without the cooperation of many federal, state, and local agencies, regional and state data repositories, and individual land trusts. We would like to thank the many state and federal agencies and local land trusts that took part in this endeavor. In addition, we would like to provide specific acknowledgement of the following organizations for their provision of state-wide, regional or national data: COMap - Colorado State University; Clemson University, David Holman - Greater Chicago area protected lands; Delaware Valley Regional Planning Commission; Florida Natural Areas Inventory; GreenInfo - California Protected Areas Database; Kansas Natural Heritage Inventory; Kentucky Natural Heritage Program; Maine State Planning Office; Maryland Environmental Trust; Montana Natural Heritage Programs, University of Montana in partnership with the Montana State Library; Nebraska Natural Heritage Program, Nebraska Game and Parks Commission; The Nature Conservancy; Utah Conservation Data Center, State of Utah Natural Resources, Division of Wildlife Resources; Virginia Natural Heritage Program, Department of Conservation and Recreation; Natural Resources Conservation Service; U.S. Fish and Wildlife Service; U.S. Forest Service.</idCredit>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>Allison Anderson</rpIndName>
<rpOrgName>Conservation Biology Institute</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum>425-286-6749</voiceNum>
</cntPhone>
<cntInstr>For more information about the NCED project and database, please contact: Allison Anderson Conservation Biology Institute 425-286-6749 allison@consbio.org Gina LaRocco Defenders of Wildlife 503-697-3222 GLaROCCO@defenders.org Robb Macleod Ducks Unlimited 734-623-2000 rmacleod@ducks.org Shara Howie NatureServe 703-797-4811 shara_howie@natureserve.org Breece Robertson The Trust for Public Land 505-988-5922 breece.robertson@tpl.org</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="007"/>
</maintFreq>
<dateNext>20111201</dateNext>
<maintScp>
<ScopeCd value="005"/>
</maintScp>
</resMaint>
<placeKeys>
<keyword>United States</keyword>
</placeKeys>
<themeKeys>
<keyword>Conservation Planning</keyword>
<keyword>Conservation Easement</keyword>
<keyword>GAP codes</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>ISO 19115 Topic Category</resTitle>
</thesaName>
<keyword>environment</keyword>
<keyword>boundaries</keyword>
</themeKeys>
<searchKeys>
<keyword>United States</keyword>
<keyword>Conservation Planning</keyword>
<keyword>environment</keyword>
<keyword>boundaries</keyword>
<keyword>Conservation Easement</keyword>
<keyword>GAP codes</keyword>
</searchKeys>
<resConst>
<LegConsts>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<othConsts>Access constraints: None.</othConsts>
</LegConsts>
</resConst>
<resConst>
<LegConsts>
<useConsts>
<RestrictCd value="008"/>
</useConsts>
<othConsts>Use constraints: This information is in the public domain unless otherwise noted in the Security attribute or restricted by prior agreement.</othConsts>
</LegConsts>
</resConst>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>NCED</classSys>
<handDesc>To address any data sensitivity concerns, data providers where given the option to either: 1) display all data (spatial and non-spatial), and allow it to be downloadable, 2) display and download only non-spatial data (easement boundaries not available for viewing or downloading). 3) display all data (spatial and non-spatial), but not allow spatial data to be downloadable The NCED team did not request land owner contact information, thus that information is not available for any of the easements aggregated for the NCED.</handDesc>
</SecConsts>
</resConst>
<resConst>
<Consts>
<useLimit>Definition of NCED Project Team: Whereas, the NCED Project Team, represents the organizations involved in the NCED Project, which includes: The Conservation Biology Institute, Defenders of Wildlife, Ducks Unlimited, NatureServe and The Trust for Public Land. 1. The NCED Project Team has received the required consent from the data providers for NCED portal users to access and use non-sensitive conservation easement data (as defined by the data providers). 2. The NCED Project Team shall have no liability for any claim of infringement or rights by third parties based on any use of the NCED dataset in combination with programs, software, hardware, or equipment not designated by the NCED Project Team, without prior written approval by the NCED Project Team, if such infringement could have been avoided had the NCED dataset not been so used. 3. The NCED Project Team shall have no liability or responsibility to the data users, or any other person or entity with respect to any liability, loss, or damage caused or alleged to be caused directly or indirectly by the NCED dataset, including but not limited to any interruption of service, loss of business, anticipatory profits or indirect, special, or consequential damages resulting from the use or operation of the NCED dataset. 4. The NCED Project Team warrants that the data and metadata in the NCED dataset have been accurately compiled, and reviewed to ensure compliance with the NCED Quality Assurance and Control Procedures.</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode country="USA" value="eng"/>
<countryCode value="eng"/>
</dataLang>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>20110606</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-85.457047</westBL>
<eastBL Sync="TRUE">-66.113832</eastBL>
<northBL Sync="TRUE">49.542754</northBL>
<southBL Sync="TRUE">34.650213</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-85.457047</westBL>
<eastBL Sync="TRUE">-66.113832</eastBL>
<northBL Sync="TRUE">49.542754</northBL>
<southBL Sync="TRUE">34.650213</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<suppInfo>The goals for the first phase of the NCED project were to develop a database schema (standard attribute list, domains and spatial reference) for the easement database; develop methods and standards for data collection and aggregation; collect as many of the existing conservation currently in GIS format as possible; aggregate and develop metadata to characterize the conservation easements; and provide a web portal where users can digitize new easements, query and view the NCED data, produce reports, and download data. At the end of phase I (July 31, 2011), the NCED contained 80,756 easements, totaling 17,818,164 acres. The NCED portal will be released to the public in early August 2011. In the second phase of NCED, starting in August 2011, the NCED project team will begin digitizing the non-digital easements that were identified in Phase I, perform additional data improvements, continue with data collection efforts, and market the NCED database to land planners and conservation organizations. Data will be updated on an ongoing basis as funding supports.</suppInfo>
<descKeys>
<thesaName uuidref="723f6998-058e-11dc-8314-0800200c9a66"/>
<keyword Sync="TRUE">002</keyword>
</descKeys>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<tpCat>
<TopicCatCd value="007"/>
</tpCat>
<tpCat>
<TopicCatCd value="003"/>
</tpCat>
<envirDesc Sync="FALSE">Esri ArcGIS 12.4.0.19948</envirDesc>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="007"/>
</maintFreq>
<dateNext>20111201</dateNext>
<maintScp>
<ScopeCd value="005"/>
</maintScp>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Data evaluated according to the "NCED Quality Assurance and Control Procedures" developed by the NCED technical team that document a data aggregation and quality control (QC) process that supports the creation of a standardized, high quality national conservation easement dataset. This work is being done collaboratively by the National Conservation Easement Data (NCED) partners (CBI, TPL, Ducks Unlimited, NatureServe, and Defenders). QC goals: 1) Attribute Table: Ensure that all required attributes (as defined by the NCED team) are complete and accurate. 2) Polygon: Ensure correct projection, and identification or elimination of: - duplicate polygons, - polygons with overlaps, data gaps or other boundary discrepancies, and - sensitive data. The QC / QA is currently underway; the DRAFT dataset likely has some missing attributes, data errors, and overlapping or duplicate polygons. Please check for a FINAL version of the NCED dataset and use that to replace the DRAFT dataset.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>While compiling the NCED database, the partners also kept track of the number of easements that were not currently in digital format or withheld from the NCED database. There were a total of 12,182 easements (2,126,341 acres) not in digital format that were not included in the NCED database. Digitizing these easements will be a part of Phase II of the NCED project. There were a total of 42,884 easements (10,741,920 acres) that were withheld from the NCED database. A majority of these easements (40,210 easements - 10,387,334 acres) were the U.S Fish and Wildlife Service private land easements in the prairie pothole region of the U.S. Note that some of the numbers and acres on non-digitized easements are estimates since the exact numbers were either not provided or the exact numbers could not be easily estimated. This is especially true for the Department of Transportation where many states either did not respond or were only able to provide general estimates of total easements and acres. There were also Land Trust that did not respond to inquiries, so those numbers are also unknown. For additional information about known non-digital easements not currently in NCED and easements withheld from NCED, please see Table 1 in the "NCED Users Guide".</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>In addition to the initial quality control measures that checked for internal consistency and accuracy from individual data providers, the NCED database was reviewed for overlapping polygons. Three basic types of overlaps were identified: duplicate easements, stacked easements, and overlapping easements. Duplicate easements occurred when the same easement boundary was obtained from two different source organizations. These easements were identified, compared, and reconciled so that each easement is only represented in the NCED database a single time. Stacked easements occur when there are two legitimate easements that cover the same or part of the same geography. In these cases, the STACKED attribute in the NCED database is changed to "Yes" to indicate to the user that these are legitimate easements, i.e., there are no known errors in the data. Overlapping easements occur when two or more easements overlap in part of the same geography and are not suppose to overlap, i.e., overlap due to mapping errors in one or both easements. Fixing all of these overlap was beyond the scope of Phase I, so many of these overlap are identified in the CONFLICT attribute as "Conflict - No Adjustment" and will be targeted to be fixed in Phase II. When aggregating multiple data sources it is difficult to stay consistent with easement holder names. Although many of the attributes in the NCED data have domains (i.e., set values were provided in a drop down menu) which standardizes field values. However, it was not within the scope of this effort to standardize the easement holder names field due to the large number of easement holder name variations used by organizations that hold easements, i.e., invariably there will be multiple spellings or abbreviations to organization names. The remaining attributes in the NCED database were also reviewed and adjusted to reduce similar anomalies.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>To start the data collection process, the NCED team developed a list of organizations that could potentially hold conservation easements. A large number of conservation easements throughout the United States are held by local land trust organizations. The Land Trust Alliance represents more than 1,700 land trusts throughout the United States and does a periodic census of the land trusts to record the number and acres of conservation lands. A list of land trusts was obtained from the Land Trust Alliance for the NCED project. In addition, a list of state agencies that could potentially hold easements was generated as well as county agencies that have passed a conservation finance ballot measure (bonds, property tax, sales tax, etc.) for open space and watershed protection efforts. These lists were combined and organized by state. A list of federal agencies and national or regional conservation organizations that could potentially hold easements were generated from the NCED teams past experience. The lists of all organizations and agencies that could potentially hold conservation easements were combined into a database that tracked the status of data collection efforts (hereinafter 'NCED Tracker'). The NCED Team divided the data collection responsibilities into states and regional or national organizations. The data collection efforts were divided up among the NCED project team based on past data collection experience and affiliations. If the organizations that were contacted had easements, but did not want to participate, or had easements that were not digitized, the number and acreage was recorded in the NCED Tracker, as well as notes on whether the organization should be contacted in Phase II of the project. If organizations contacted did not respond to multiple calls over an extended period of time, that was also documented in the NCED Tracker and will be re-contacted in Phase II. When data is received from an organization, it is reviewed in its native format and checked for any obvious errors and missing attributes. The initial quality control consists of viewing the data along with other base information (digital orthophotos, topographic maps, etc) to make sure the polygons are in a logical location and reviewing the attributes to determine if additional information is needed to fulfill the NCED attribute requirements. If any problems are encountered or if additional information is needed, the organization is re-contacted to determine if corrections are needed or collect additional information regarding the easement. Once the data has passed the initial quality control process, it is re-projected into the NCED projection (USA Contiguous Albers Equal Area Conic USGS projection). The next step in the data aggregation process is to create an empty personal geodatabase with the NCED schema. The original data is then loaded into the empty geodatabase and the original attributes are mapped to the correct NCED attributes. Once the data is loaded any additional attributes are added to the database (data entry date, data aggregator, etc.). After the original data was formatted and placed in the personal geodatabase, they are loaded into the partner NCED geodatabase replica. The NCED geodatabase replica is then synchronized with the master NCED geodatabase. The NCED project uses a distributed geodatabase as the workflow between CBI (database administrator) and other NCED partners. Either a check-out geodatabase or two-way replica was created between CBI and NCED project team. Replicas were then synchronized periodically between CBI and the NCED project team.</stepDesc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="CONS_NCED">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode code="102039">United States</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.12(9.3.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<spdoinfo>
<ptvctinf>
<esriterm Name="CONS_NCED">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<eainfo>
<detailed Name="CONS_NCED">
<enttyp>
<enttypl Sync="FALSE">CONS_NCED</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</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 Sync="TRUE">UID</attrlabl>
<attalias Sync="TRUE">Unique ID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Security</attrlabl>
<attalias Sync="TRUE">Security</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SiteName</attrlabl>
<attalias Sync="TRUE">SiteName</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">EsmtHldr</attrlabl>
<attalias Sync="TRUE">Easement Holder</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">EHoldTyp</attrlabl>
<attalias Sync="TRUE">Easement Holder Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">LandType</attrlabl>
<attalias Sync="TRUE">Landowner Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">CoHeld</attrlabl>
<attalias Sync="TRUE">Co-Held</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Purpose</attrlabl>
<attalias Sync="TRUE">Conservation Purpose</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ConsIntent</attrlabl>
<attalias Sync="TRUE">Conservation Intent</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">70</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PubAccess</attrlabl>
<attalias Sync="TRUE">Public Access</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Duration</attrlabl>
<attalias Sync="TRUE">Duration</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Term</attrlabl>
<attalias Sync="TRUE">Term</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AcqDay</attrlabl>
<attalias Sync="TRUE">Acquisition Day</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AcqMonth</attrlabl>
<attalias Sync="TRUE">Acquisition Month</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AcqYear</attrlabl>
<attalias Sync="TRUE">Acquisition Year</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">State</attrlabl>
<attalias Sync="TRUE">State</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">DataAgg</attrlabl>
<attalias Sync="TRUE">Data Aggregator</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">DataEntry</attrlabl>
<attalias Sync="TRUE">Data Entry Date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">DataPvdr</attrlabl>
<attalias Sync="TRUE">Data Provider</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">DataSrc</attrlabl>
<attalias Sync="TRUE">Data Source</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">OrigUID</attrlabl>
<attalias Sync="TRUE">Original UID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">BoundCF</attrlabl>
<attalias Sync="TRUE">Boundary Confidence</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AreaRptd</attrlabl>
<attalias Sync="TRUE">Reported Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AreaGIS</attrlabl>
<attalias Sync="TRUE">GIS Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">AreaDiff</attrlabl>
<attalias Sync="TRUE">Area Difference</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Conflict</attrlabl>
<attalias Sync="TRUE">Conflict</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Stacked</attrlabl>
<attalias Sync="TRUE">Stacked</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Comments</attrlabl>
<attalias Sync="TRUE">Comments</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</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">8</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 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>
</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>
</attr>
</detailed>
</eainfo>
<mdDateSt Sync="TRUE">20191002</mdDateSt>
</metadata>
