<?xml version="1.0" encoding="UTF-8"?><metadata>
<Esri>
<CreaDate>20221129</CreaDate>
<CreaTime>08461700</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20200314</SyncDate>
<SyncTime>21293500</SyncTime>
<ModDate>20200314</ModDate>
<ModTime>21293500</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Corners</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">2234049.422233</westBL>
<eastBL Sync="TRUE">2470916.524942</eastBL>
<southBL Sync="TRUE">301455.091769</southBL>
<northBL Sync="TRUE">747610.451097</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983_HARN</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601_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/10.5'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_HARN_StatePlane_Washington_North_FIPS_4601_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983_HARN&amp;quot;,DATUM[&amp;quot;D_North_American_1983_HARN&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;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-120.8333333333333],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,47.5],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,48.73333333333333],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,47.0],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2926]]&lt;/WKT&gt;&lt;XOrigin&gt;-117104300&lt;/XOrigin&gt;&lt;YOrigin&gt;-99539600&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121928&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&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;2926&lt;/WKID&gt;&lt;LatestWKID&gt;2926&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
</Esri>
<dataqual>
<lineage>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20040921</date>
<time Sync="TRUE">10332700</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20040921</date>
<time Sync="TRUE">14194000</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20041007</date>
<time Sync="TRUE">10041400</time>
</procstep>
</lineage>
<posacc>
<horizpa>
<horizpar>The data is meant to comply with the National Map Accuracy Standard for 1:24,000 scale, which is that 90% of all GIS positions will be with 40 feet of the true position. See the accuracy attributes for the POINT feature data set to get specific 95% accuracy estimations.
</horizpar>
</horizpa>
</posacc>
</dataqual>
<idinfo>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.3500</native>
<descript>
<langdata Sync="TRUE">en</langdata>
<abstract>A position with a known coordinate. A Point may be a Corner, a Geodetic Control Point, or a Significant Coordinated Location. If geodetic quality coordinates are known or established for a Corner Point, the Point is still a Corner Point. A Geodetic Control Point is established for no other purpose than geodetic control.
</abstract>
<purpose>To meet the agency's business needs for land surveying, land title, and land management GIS data.
</purpose>
<supplinf>This cadastre point set was originally downloaded from the DNR site, http://www3.wadnr.gov/dnrapp6/dataweb/dmmatrix.html. A set of cadastre points completed by a John Shackelford of Williamson Consulting(2001) and Century Survey(2004) were incorporated into the layer and related points removed. Stevens County believes these points to be the best and most accurate information available to base its legal grid. With the exception of the attribute values created by Stevens County outlined in this document, the metadata available at the DNR website should be consulted for most of the attribute data.</supplinf>
</descript>
<citation>
<citeinfo>
<origin>Washington State Department of Natural Resources and Stevens County Information Services.</origin>
<pubdate>09/22/2004</pubdate>
<title Sync="TRUE">Corners</title>
<ftname Sync="TRUE">Corners</ftname>
<geoform Sync="TRUE">vector digital data</geoform>
<onlink Sync="FALSE">withheld</onlink>
</citeinfo>
</citation>
<timeperd>
<current>publication date</current>
<timeinfo>
<sngdate>
<caldate>unknown</caldate>
</sngdate>
</timeinfo>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-118.433639</westbc>
<eastbc Sync="TRUE">-117.379774</eastbc>
<northbc Sync="TRUE">49.007296</northbc>
<southbc Sync="TRUE">47.779661</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">395139.524681</leftbc>
<rightbc Sync="TRUE">471554.514681</rightbc>
<bottombc Sync="TRUE">5292759.611712</bottombc>
<topbc Sync="TRUE">5428339.731712</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>point, corner, gps, monument, control, geodetic</themekey>
</theme>
</keywords>
<accconst>Public data edited by Stevens County Staff, no constraints exist.</accconst>
<useconst>This data set has been edited and adjusted to fit the needs of Stevens County. Use by private individuals or other agencies may not produce the desired results due to the changes incorporated.</useconst>
<natvform Sync="TRUE">File Geodatabase Feature Class</natvform>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Bruce L. Garcia</cntper>
<cntorg>Stevens County Information Services</cntorg>
</cntperp>
<cntpos>GIS Coordinator</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>215 S. Oak St.</address>
<city>Colville</city>
<state>WA</state>
<postal>99114</postal>
</cntaddr>
<cntvoice>509-684-7505</cntvoice>
<cntfax>509-684-8310</cntfax>
<cntemail>bgarcia@co.stevens.wa.us</cntemail>
</cntinfo>
</ptcontac>
<datacred>Washington State Department of Natural Resources and Stevens County Information Services.</datacred>
<secinfo>
<secclass>Unclassified</secclass>
</secinfo>
</idinfo>
<dataIdInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.5.1.7333</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">Corners</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">395139.524681</westBL>
<eastBL Sync="TRUE">471554.514681</eastBL>
<northBL Sync="TRUE">5428339.731712</northBL>
<southBL Sync="TRUE">5292759.611712</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-118.433639</westBL>
<eastBL Sync="TRUE">-117.379774</eastBL>
<northBL Sync="TRUE">49.007296</northBL>
<southBL Sync="TRUE">47.779661</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-118.417474</westBL>
<eastBL Sync="TRUE">-117.373014</eastBL>
<northBL Sync="TRUE">49.023231</northBL>
<southBL Sync="TRUE">47.776439</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</dataIdInfo>
<metainfo>
<langmeta Sync="TRUE">en</langmeta>
<metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv>
<mettc Sync="TRUE">local time</mettc>
<metc>
<cntinfo>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<city>Colville</city>
<state>WA</state>
<postal>99114</postal>
<address>215 S. Oak St.</address>
</cntaddr>
<cntvoice>509-684-7505</cntvoice>
<cntperp>
<cntper>Bruce L. Garcia</cntper>
<cntorg>Stevens County Information Services</cntorg>
</cntperp>
<cntpos>GIS Coordinator</cntpos>
<cntfax>509-684-8310</cntfax>
</cntinfo>
</metc>
<metd Sync="TRUE">20110301</metd>
<metac>None</metac>
<metuc>None</metuc>
<metsi>
<metsc>Unclassified</metsc>
</metsi>
</metainfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
<mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distinfo>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Stevens County Information Services</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>215 S. Oak St.</address>
<city>Colville</city>
<state>WA</state>
<postal>99114</postal>
</cntaddr>
<cntvoice>509-684-7505</cntvoice>
<cntfax>509-684-8310</cntfax>
</cntinfo>
</distrib>
<distliab>None</distliab>
</distinfo>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
<protocol Sync="TRUE">Local Area Network</protocol>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="Corners">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="1"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">10519</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_UTM_Zone_11N</projcsn>
</cordsysn>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<plandu Sync="TRUE">meters</plandu>
<coordrep>
<absres Sync="TRUE">0.000156</absres>
<ordres Sync="TRUE">0.000156</ordres>
</coordrep>
</planci>
</planar>
<geodetic>
<horizdn Sync="TRUE">North American Datum of 1983</horizdn>
<ellips Sync="TRUE">Geodetic Reference System 80</ellips>
<semiaxis Sync="TRUE">6378137.000000</semiaxis>
<denflat Sync="TRUE">298.257222</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres Sync="TRUE">0.000156</altres>
</altsys>
</vertdef>
</spref>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2926">NAD_1983_UTM_Zone_11N</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.9.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Corners">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="004"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">10519</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<eainfo>
<detailed Name="Corners">
<enttyp>
<enttypl Sync="TRUE">Corners</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">10519</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">0</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">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</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">PNTID</attrlabl>
<attalias Sync="TRUE">PNTID</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>100-1000</edomv>
<edomvd>Calculated Points from John Shackelford(WC) that were part of the WRIA 59 Pilot GIS Project.</edomvd>
</edom>
<edom>
<edomv>2000-4000</edomv>
<edomvd>Calculated Points from John Shackelford(WC) that were part of the regular WRIA 59 GIS Project.</edomvd>
</edom>
<edom>
<edomv>5000-6000</edomv>
<edomvd>Calculated Points from John Shackelford(WC) that were part of the SFLO GIS Project. This is an offshoot of the WRIA 59 GIS Project that was funded by the Washington State Small Forest Landowners Office.</edomvd>
</edom>
<edom>
<edomv>7000-7999</edomv>
<edomvd>Proportion Points from John Shackelford(WC) that were part of the WRIA 59 and SFLO GIS Projects.</edomvd>
</edom>
<edom>
<edomv>8000-8999</edomv>
<edomvd>GPS Points from John Shackelford(WC) that were part of the WRIA 59 and SFLO GIS Project.</edomvd>
</edom>
<edom>
<edomv>10000-10100</edomv>
<edomvd>GPS Points from Century Survey for the Colville River GIS Project</edomvd>
</edom>
<edom>
<edomv>89000 plus</edomv>
<edomvd>Original Cadastre Points from the Washington State Department of Natural Resources.</edomvd>
</edom>
</attrdomv>
<attrdef>Indicates the source of the corner information.</attrdef>
<attrdefs>STCO, DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTTY</attrlabl>
<attalias Sync="TRUE">PNTTY</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Corner Point. The primary definition of Corner is a legal location. It marks an extremity of a boundary of a subdivision of land. It may mark the extremity of Parcel or a Parcel Legal Area. In addition, a Corner may be a location to which the boundaries of a subdivision of land are referenced. A Corner may have multiple Corner Points, which serve as measures of markers for the legal location of the Corner. For example, a section corner may be disputed as to location and have two or more Corner Points, each of which may or may not be monumented. Examples of Corners that are not on the extremities of a boundary of a subdivision of land are Corners with the Corner Classification code of Location Monument or with the Corner Qualifier code of Witness Point.</edomvd>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Geodetic Control Point. A control station is a precisely coordinated point correlated with other coordinated points. A Geodetic Control Point is a horizontal and/or vertical control station that has been established and adjusted by geodetic methods and in which the shape and size of the earth (geoid) have been considered in position computations. Horizontal geodetic coordinates are latitude and longitude with respect to a reference spheroid. Vertical geodetic elevations are relative to a datum extended over a large area and used to furnish accurate vertical control for surveying and mapping operations. A Geodetic Control Point provides a relationship between the corners of legal areas and a global coordinate system.</edomvd>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Significant Coordinated Location. A Significant Coordinated Location is a point that is important for cadastral investigations but is not a Corner Point or a Geodetic Control Point. An example would be a point on a vegetation line, or a point on a fence line. This is a place to store the locations of features and objects which have cadastral significance.</edomvd>
</edom>
</attrdomv>
<attrdef>Indicates the type of point.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTLBL</attrlabl>
<attalias Sync="TRUE">PNTLBL</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Corner Label</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTNM</attrlabl>
<attalias Sync="TRUE">PNTNM</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Corner Label Name</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONSTAT</attrlabl>
<attalias Sync="TRUE">MONSTAT</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Monumented</edomvd>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Not Monumented</edomvd>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Monumentation Unknown</edomvd>
</edom>
</attrdomv>
<attrdef>Indicates infromation about whether the point is monumented.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORID</attrlabl>
<attalias Sync="TRUE">CORID</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Same as the PNTID</attrdef>
<attrdefs>STCO, DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORDSPFLG</attrlabl>
<attalias Sync="TRUE">CORDSPFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Indicates a dispute over whether a point is a corner.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORPRTRFLG</attrlabl>
<attalias Sync="TRUE">CORPRTRFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Indicates whether a point is a protracted corner. A protracted corner was never surveyed by the GLO or BLM and only exists on a Protraction Diagram. A Protraction Diagram is prepared for the purpose of describing unsurveyed land areas. The diagram is approved for the Director by the Chief, Division of Cadastral Survey, and filed in the respective state offices of the BLM after public notice in the Federal Register.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORCLASS</attrlabl>
<attalias Sync="TRUE">CORCLASS</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>36</edomv>
<edomvd>Township Corner. A corner at the extremity of a PLSS township boundary. Normally a PLSS township has four township corners. This does not include section, quarter-section or section subdivision corners which are on a PLSS township boundary.</edomvd>
</edom>
<edom>
<edomv>33</edomv>
<edomvd>Section Corner. A corner at the extremity of a PLSS section boundary.</edomvd>
</edom>
<edom>
<edomv>37</edomv>
<edomvd>1/4 Section Corner. Quarter-Section Corner. A corner at the extremity of a boundary of a PLSS quarter-section, not including the section corner or center quarter section corner. Written as 1/4 not one fourth.</edomvd>
</edom>
<edom>
<edomv>38</edomv>
<edomvd>1/16 Section Corner. Also termed "quarter-quarter section corner." A corner at an extremity of a boundary of a quarter-quarter section or 1/16th of a section; midpoint between or 20 chains from the controlling corners on the section or township boundaries.</edomvd>
</edom>
<edom>
<edomv>39</edomv>
<edomvd>1/64 Section Corner. A corner at an extremity of a boundary of a 1/64 subdivision of a section. A 1/64 subdivision is the result of the quartering of a quarter-quarter section.</edomvd>
</edom>
<edom>
<edomv>99</edomv>
<edomvd>Not Classified</edomvd>
</edom>
</attrdomv>
<attrdef>The Corner Classification describes the use of the specific Corner. A corner may have multiple classifications. For example, a section corner may also function as a subdivision corner and a lot corner. The highest use of the corner should be denoted by the corner class. A hierarchy of corner classifications should be developed. Only Codes used by STCO are included.</attrdef>
<attrdefs>STCO, DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORAMNDFLG</attrlabl>
<attalias Sync="TRUE">CORAMNDFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Indicates an amended corner, one which no longer functions as a corner and has been replaced by another corner monument. There are two primary applications of amended monuments stated in the BLM Manual of Instruction. In general a monument whose position no longer marks the true position for the corner. The monument is marked A.M. "If it is known that a mineral survey, homestead entry, small holding claim, right of way, reservoir, or other survey has been connected with a corner of an exterior subject to rectification, the fact is stated in the special instruction. In such a case the marks A.M. (signifying amended monument) are added to the original corner monument and the old corner is connected by course and distance to the new." (BLM 1973, paragraph 3-36.) "A recovered closing corner not actually located on the line that was closed upon will determine the direction of the closing line, but not its legal terminus. The correct position is at the true point of intersection of the two lines. The new monument in those cases where it is required will always be placed at the true point of intersection. An off-line monument in those cases where a new monument is required will be marked A.M. (for amended monument) and will be connected by course and distance." (BLM 1973, paragraphs 5-41 and 8- 16(6).)</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORQUAL</attrlabl>
<attalias Sync="TRUE">CORQUAL</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The corner class qualifier refines the corner classification.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORACPTFLG</attrlabl>
<attalias Sync="TRUE">CORACPTFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>This flag indicates if the Corner Point is accepted as the location of the Corner.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORACPTDT</attrlabl>
<attalias Sync="TRUE">CORACPTDT</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date on which the point was accepted as the corner.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">CORVERFLG</attrlabl>
<attalias Sync="TRUE">CORVERFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Indicates that the possibly machine generated class, qualifier, and monumentation status codes have been verified as correct.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">POINTSRC</attrlabl>
<attalias Sync="TRUE">POINTSRC</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>8000</edomv>
<edomvd>County Surveyor/Engineer</edomvd>
</edom>
<edom>
<edomv>8999</edomv>
<edomvd>County Utility</edomvd>
</edom>
<edom>
<edomv>9999</edomv>
<edomvd>Private Surveyor</edomvd>
</edom>
</attrdomv>
<attrdef>The agency or private source of the monumented point. Only codes used by STCO are included.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTALIASNM</attrlabl>
<attalias Sync="TRUE">PNTALIASNM</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Text which represent an alternate form of the name used to identify the control point. These alias entries arise due to non-standard naming conventions used by various agencies and individuals.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTDESC</attrlabl>
<attalias Sync="TRUE">PNTDESC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">240</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Text describing the point.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTESTDT</attrlabl>
<attalias Sync="TRUE">PNTESTDT</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date the point was established.</attrdef>
</attr>
<attr>
<attrlabl Sync="TRUE">PNTPROJNM</attrlabl>
<attalias Sync="TRUE">PNTPROJNM</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date the point was established.</attrdef>
<attrdefs>STCO</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">GEOPNTID</attrlabl>
<attalias Sync="TRUE">GEOPNTID</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">16</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>An alphanumeric designator given by an agency to identify the Geodetic Control Point. For the National Geodetic Survey the Point ID Number is a six-character Permanent Identifier (PID, formerly known as ACRN) which now serves as the primary means for matching recovery description data against the data base for marks known to NGS. Other agencies may have their own unique PID system. The DNR at present, February of 1998, uses a four digit integer for the PID. It is anticipated that in the future the DNR will run out of the present series of PID's and be required to add new digits or letters.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">X</attrlabl>
<attalias Sync="TRUE">X</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The measured east-west coordinate. If it is a plane coordinate, then this is the plane coordinate describing the east-west position of the point. A Plane Rectangular Cartesian east-west coordinate, an easting, is the distance from the north-south axis of the coordinate system in a direction parallel to the east-west axis. Distances east of the axis are positive and distances west of the axis are negative. If it is a longitude, then this is the coordinate describing the east-west position of the point. A geographic east-west coordinate is a longitude, defined as the angle between the plane of the geodetic meridian passing through the Point and the plane of the Meridian of Greenwich. Positive Longitudes will be understood to be the angle measured west from Greenwich.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Y</attrlabl>
<attalias Sync="TRUE">Y</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The measured north-south coordinate. If it is a plane coordinate, then this is the plane coordinate describing the north-south position of the point. A Plane Rectangular Cartesian north-south coordinate, a northing, is the distance from the east-west axis of the coordinate system in a direction parallel to the north-south axis. Distances north of the axis are positive and distances south of the axis are negative. If it is a latitude, then this is the coordinate describing the north-south position of the point. A geographic north-south coordinate is a latitude, defined as the angle which the normal at the Point, projected to the ellipsoid, makes with the plane of the geodetic equator. Positive Latitudes will be understood to be the angle measured north from the equator.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HZCOORDSYS</attrlabl>
<attalias Sync="TRUE">HZCOORDSYS</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>6</edomv>
<edomvd>NAD 1927 StatePlane Washington South FIPS 4602</edomvd>
</edom>
<edom>
<edomv>9</edomv>
<edomvd>NAD 1983 StatePlane Washington North FIPS 4601</edomvd>
</edom>
<edom>
<edomv>10</edomv>
<edomvd>NAD 1983 StatePlane Washington South FIPS 4602</edomvd>
</edom>
<edom>
<edomv>14</edomv>
<edomvd>NAD 1983 UTM Zone 11N</edomvd>
</edom>
</attrdomv>
<attrdef>Indicates the datum and/or the plane coordinates system and/or the ellipsoid for the measured horizontal coordinates. A geodetic datum is a set of constants specifying the coordinate system used for geodetic control, i.e., for calculating coordinates of points on the earth. At least eight constants are needed to form a complete datum: three to specify the location of the origin of the coordinate system, three to specify the orientation of the coordinate system, and two to specify the dimensions of the reference ellipsoid. Before geocentric geodetic datums became possible, it was customary to define a geodetic datum by five quantities: the latitude and longitude of an initial point, the azimuth of a line from this point, and the (two) parameters of the reference ellipsoid. This meaning does not conform to modern usage. A plane coordinate system is a system defining positions by pairs of coordinates which are the perpendicular distances of a point from a pair of axes which intersect at right angles, reckoned in the plane defined by those axes. The position of a point on the earth can be defined by plane rectangular coordinates on a tangent plane (a local system of plane coordinates), or on a so-called conic or cylindrical map projection, such as are used in the state plane coordinate systems. An ellipsoid is a closed surface whose planar sections are either ellipses or circles. For a horizontal datum a reference ellipsoid is an ellipsoid of specified dimensions and associated with the geodetic reference system or datum and to which coordinates in the reference system are said to be with respect. A spheroid is any surface differing but little from a sphere. Many reference ellipsoids of older vintage have been called spheroids. Only the coded used by STCO are included.</attrdef>
<attrdefs>STCO, DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HZMEASMT</attrlabl>
<attalias Sync="TRUE">HZMEASMT</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>901</edomv>
<edomvd>Computed/Calculated. The Calculation method describes coordination methods using some sort of mathematical process for deriving the coordinate. A BLM protraction diagram in which latitudes and longitudes are calculated for corners without a field survey would fit this type.</edomvd>
</edom>
<edom>
<edomv>905</edomv>
<edomvd>Geodetic GPS Survey. The Geodetic GPS Survey method describes the use of the Global Positioning System to make coordinate measurements of high accuracy, typically better than 10 centimeters uncertainty, using the GPS signal carrier phase. The Global Positioning System is the US Department of Defense system of navigational satellites, their ground control stations and GPS receivers.</edomvd>
</edom>
<edom>
<edomv>910</edomv>
<edomvd>Resource Grade GPS. The Resource GPS Survey method describes the use of the Global Positioning System to make coordinate measurements of relatively accuracy, typically greater than 10 centimeters uncertainty, using the GPS signal code phase. The Global Positioning System is the US Department of Defense system of navigational satellites, their ground control stations and GPS receivers.</edomvd>
</edom>
<edom>
<edomv>915</edomv>
<edomvd>Proportioned. The Calculation method describes coordination methods using some sort of mathematical process for deriving the coordinate.</edomvd>
</edom>
<edom>
<edomv>999</edomv>
<edomvd>Unknown</edomvd>
</edom>
</attrdomv>
<attrdef>Indicates the methodology used to determine or measure the point coordinates. These are STCO codes.</attrdef>
<attrdefs>STCO</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HZMEASAC</attrlabl>
<attalias Sync="TRUE">HZMEASAC</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Indicates the estimation of the 95% accuracy of the point coordinate measurement. See DNR Documentation.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">HZACPTFLG</attrlabl>
<attalias Sync="TRUE">HZACPTFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Z</attrlabl>
<attalias Sync="TRUE">Z</attalias>
<attrtype Sync="TRUE">Single</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VTDATUM</attrlabl>
<attalias Sync="TRUE">VTDATUM</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VTUM</attrlabl>
<attalias Sync="TRUE">VTUM</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VTMEASMT</attrlabl>
<attalias Sync="TRUE">VTMEASMT</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VTMEASAC</attrlabl>
<attalias Sync="TRUE">VTMEASAC</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VTACPTFLG</attrlabl>
<attalias Sync="TRUE">VTACPTFLG</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MONTY</attrlabl>
<attalias Sync="TRUE">MONTY</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The Monument Type describes the material, composition, and other characteristics of the physical corner marker, if present. While monuments may be capable of being characterized in several ways, it is expected that the user will chose the most appropriate code for the monument. For example, an aluminum post with and aluminum cap should be coded as and Aluminum Cap, but an aluminum pipe in the ground should be coded as and Aluminum Marker.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONSETDT</attrlabl>
<attalias Sync="TRUE">MONSETDT</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date the monument was set.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONSETTY</attrlabl>
<attalias Sync="TRUE">MONSETTY</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>This code describes the physical environment in which the monument lies.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONTXT</attrlabl>
<attalias Sync="TRUE">MONTXT</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The stamping field should contain the exact stamping as it appears on the survey monument. The entry must not exceed 50 characters. If there is no stamping, make no entry here; however, if the marker is a type that is normally stamped, enter a short note about its being unstamped in the accompanying descriptive text.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONDESC</attrlabl>
<attalias Sync="TRUE">MONDESC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">240</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Every effort must be made to provide enough information for easy recovery of the point. A well written description should describe the monument including any information about the specific setting or exact location of the mark if the coded values are not sufficient to describe it completely.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONACCSRY</attrlabl>
<attalias Sync="TRUE">MONACCSRY</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">240</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Every effort must be made to provide enough information for easy recovery of the point. A well written description should contain the following accessory information: (1) distance and direction to, inscription, and designation of any monumented reference marks; (2) distance and direction from one or more reference objects in the immediate locale should be noted. Examples of these reference objects are the centerlines of roads, fire plugs, telephone poles, chiseled marks in pavement, and survey marks which are not included in the NGS data base. (3) distance and direction to any witness post that was set or if any witness post was set; (4) if applicable, a vertical reference to some nearby object (or the ground) stating the relationship to the object should be recorded. Distance above, below, or about flush with the object should be noted; and When distance estimates or measurements are given in metric units, English equivalencies must follow in parentheses.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONACCESS</attrlabl>
<attalias Sync="TRUE">MONACCESS</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">240</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Every effort must be made to provide enough information for easy recovery of the point. A well written description should contain the following access information: (1) one or more references to some well known, readily available, location in terms of distances and directions. Intersections of prominent highways, landmarks, and public buildings in nearby towns are examples of such locations. In some cases, this location will require some description; (2) detailed directions concerning how one would proceed to the mark site from one or more of these prominent locations; When distance estimates or measurements are given in metric units, English equivalencies must follow in parentheses. Property ownership and contact point telephone numbers are desirable when private property must be crossed or occupied.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONRECDT</attrlabl>
<attalias Sync="TRUE">MONRECDT</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The date of the Monument Recovery.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONRECCOND</attrlabl>
<attalias Sync="TRUE">MONRECCOND</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The Monument Recovery Condition Code captures the condition of the monument at the time of recovery.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">MONRECDESC</attrlabl>
<attalias Sync="TRUE">MONRECDESC</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">240</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>This provides a text field to describe in detail the changes in the monument condition, monument surroundings, and access to the monument.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">EDITDT</attrlabl>
<attalias Sync="TRUE">EDITDT</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Date the dataset was edited.</attrdef>
<attrdefs>STCO, DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">EDITSTAT</attrlabl>
<attalias Sync="TRUE">EDITSTAT</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>0</edomv>
<edomvd>Preliminary</edomvd>
</edom>
<edom>
<edomv>1</edomv>
<edomvd>Final</edomvd>
</edom>
</attrdomv>
<attrdef>Differentiates between preliminary and final edit status.</attrdef>
<attrdefs>DNR</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">EDITNM</attrlabl>
<attalias Sync="TRUE">EDITNM</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Who edited the data. For Stevens County, bgarcia510, is Bruce Garcia and 510 is the Departmental Number. All others are DNR employees.</attrdef>
<attrdefs>STCO</attrdefs>
</attr>
</detailed>
</eainfo>
<mdDateSt Sync="TRUE">20200314</mdDateSt>
</metadata>
