<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20190313</CreaDate>
<CreaTime>08302500</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20180711</SyncDate>
<SyncTime>11525900</SyncTime>
<ModDate>20180711</ModDate>
<ModTime>11525900</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">Zoning</itemName>
<imsContentType>002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">5687189.803000</westBL>
<eastBL Sync="TRUE">6201605.500000</eastBL>
<southBL Sync="TRUE">1808592.500000</southBL>
<northBL Sync="TRUE">2229048.000000</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_California_IV_FIPS_0404_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.2.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_California_IV_FIPS_0404_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;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,6561666.666666666],PARAMETER[&amp;quot;False_Northing&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-119.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,36.0],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,37.25],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,35.33333333333334],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2228]]&lt;/WKT&gt;&lt;XOrigin&gt;-116466200&lt;/XOrigin&gt;&lt;YOrigin&gt;-92735300&lt;/YOrigin&gt;&lt;XYScale&gt;4000&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.002&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.002&lt;/ZTolerance&gt;&lt;MTolerance&gt;1.9999999999999998e-05&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102644&lt;/WKID&gt;&lt;LatestWKID&gt;2228&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>ItemDescription</ArcGISProfile>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<idinfo>
<citation>
<citeinfo>
<onlink Sync="FALSE">withheld</onlink>
<origin>Monterey County Planning and Building Dept. GIS Team </origin>
<pubdate>Unpublished Material</pubdate>
<title Sync="FALSE">Zoning</title>
<ftname Sync="FALSE">Zoning</ftname>
<geoform Sync="TRUE">vector digital data</geoform>
</citeinfo>
</citation>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.1850</native>
<descript>
<langdata Sync="TRUE">en</langdata>
<abstract>The zoning112002.shp layer represents the zoning designations for all unincorporated areas of Monterey County. This digital map is meant to replicate and replace the county's existing hardcopy zoning maps. There are currently 45 areas that have been labeled 'Under Review' in this layer. Zoning for projects in one of these areas will have to be determined using the hardcopy Sectional District Maps.</abstract>
<purpose>This layer was developed to assist in the processing of planning and building permits.</purpose>
<supplinf>Current as of 12/16/2008</supplinf>
</descript>
<timeperd>
<current>ground condition</current>
<timeinfo>
<sngdate>
<caldate>12/16/2008</caldate>
</sngdate>
</timeinfo>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-121.991663</westbc>
<eastbc Sync="TRUE">-120.213947</eastbc>
<northbc Sync="TRUE">36.943886</northbc>
<southbc Sync="TRUE">35.758423</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">5687189.803000</leftbc>
<rightbc Sync="TRUE">6201605.500000</rightbc>
<bottombc Sync="TRUE">1808592.500000</bottombc>
<topbc Sync="TRUE">2229048.000000</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>zoning</themekt>
<themekey>Planning</themekey>
</theme>
<theme>
<themekey>zoning</themekey>
</theme>
<theme>
<themekt>district</themekt>
</theme>
<theme>
<themekt>district</themekt>
</theme>
<theme>
<themekt>allowed use </themekt>
</theme>
<theme>
<themekt>setback </themekt>
</theme>
<theme>
<themekt>coverage</themekt>
</theme>
<theme>
<themekt>density</themekt>
</theme>
<theme>
<themekt>residential</themekt>
</theme>
<theme>
<themekt>commercial</themekt>
</theme>
<theme>
<themekt> farming</themekt>
</theme>
<theme>
<themekt>grazing</themekt>
</theme>
<theme>
<themekt>frog farms </themekt>
</theme>
</keywords>
<accconst>Sign limited warranty</accconst>
<useconst>NOT FOR LEGAL USE. This data is not the official zoning for Monterey County. The official zoning is that which is on the zoning map mylars kept on file in the Planning Department. This layer is an attempt to replicate those maps. Where there are differences between this layer and the official maps; the official maps take precedence.</useconst>
<natvform Sync="FALSE">Feature Class</natvform>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>Jim Dimaqggio</cntper>
<cntorg>RMA</cntorg>
</cntperp>
<cntvoice>831 755 5154</cntvoice>
<cntemail>dimaggioj@co.monterey.ca.us</cntemail>
</cntinfo>
</ptcontac>
</idinfo>
<distInfo>
<distributor>
<distorTran>
<onLineSrc>
<linkage Sync="FALSE">withheld</linkage>
<orDesc Sync="TRUE">002</orDesc>
</onLineSrc>
<transSize Sync="TRUE">12.653</transSize>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">Enterprise Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataqual>
<lineage>
<procstep>
<procdesc>The zoning112002.shp creation procedure is as follows: Using the current parcel layer, parcels with identical zoning were selected and merged together using the 'Combine Features' function. The appropriate zoning attributes were added to the shapefile table. This data included: the 'planning area' represented by a numbered code, the 'zoning string' representing the zoning as it appears on the existing hardcopy maps, the 'zoning category', the density, any combined regulations, height limitations and notes. The above method was sufficient as long as zoning boundaries followed parcel outlines. Irregular-shaped zoning districts, common in 'Farmlands' districts, required special editing techniques. In these instances a transparency is made from the existing Sectional District Map (SDM) of the area in question. The scale of the ArcView display is then matched to the scale of the transparency. The transparency is placed over the monitor and aligned so that the parcel lines on the transparency match those parcel lines in ArcView. The polygon or polygons can then be edited to match the zoning district boundary as it appears on the SDM. Each polygon or 'zoning district' is then labeled according to its 'zone string'. Any one polygon should be contiguous to itself, or in other words no part should be disconnected from the rest of the polygon. Any 'Notes' on the SDM's are accounted for on the digital map by adding the appropriate information to the attribute table for each applicable polygon. In instances where mapping errors have been discovered on the SDM, the correct zoning is determined and that is what appears on the digital map. A running list of these errors is kept and noted on a separate set of the SDM's. A set of rules were developed for application in situations where the SDM and the digital zoning map appeared different. When applicated, instances are noted on a separate set of SDM's with the associated Rule #. The rules are: 1. What if the existing zoning boundary does not line up with digital parcel lines, even though it does line up with manually drawn parcel lines on the SDM? RULE #1A - When the same parcel lines are shown on both the digital map and SDM with simply minor differences in dimensions, shift zoning boundary line on the digital map to follow the same parcel lines depicted on the SDM. RULE #1B - When the same parcel lines are shown on both the digital map and SDM but with notable differences in shape and size, use other reference points on the digital map to closely replicate the location of the zoning boundary as depicted on the SDM. 2. What if existing zoning boundary does not line up with digital parcel lines and, unlike #1 above, there are no corresponding parcel lines on the SDM's? RULE #2 - Use other reference points on the digital map to closely replicate the location of the zoning boundary as depicted on the SDM. 3. What if existing zoning boundary follows a natural landform feature (e.g., topographic contour, watershed basin, river, prime soils) or rancho boundaries, rather than parcel lines? RULE #3 - Use other reference points on the digital map to closely replicate the location of the zoning boundary as depicted on the SDM. 4. What if a parcel straddles the Monterey County line, extending into a neighboring county? RULE #4 - Use the Monterey County line as zoning boundary on digital map. Use U.S. Census boundary mapping as the basis for the Monterey County line even if it varies from parcel lines. 5. What if existing zoning boundary lies along a roadway? RULE #5A - Where a zoning boundary lies along a public road, the zoning boundary should follow the right-of-way boundaries, thereby excluding such roadways from any zoning designation. RULE #5B - Where a zoning boundary lies along a private road, the zoning boundary should follow the centerline of the roadway. An exception is that those private roads in large subdivisions delineated on the digital base map shall be treated the same as public roads (see Rule 5A). 6. What if the existing zoning boundary lies along a railroad right-of-way? RULE #6 - Draw the zoning boundary along the railroad centerline or right-of-way boundary, whichever best replicates the location as depicted on the SDM. 7. What if the location of the Coastal Zone boundary differs slightly between the separate sets of SDM's for Titles 20 and 21? RULE #7 - Use existing digitized Coastal Zone boundary, which was based on the original mapping of Title 20 zoning. Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Person: Jim DiMaggio Contact_Organization: Monterey County Planning and Building Dept. GIS Team Contact_Position: GIS Technician Contact_Voice_Telephone: 831-755-5065x3065 Contact_Electronic_Mail_Address: dimaggioj@co.monterey.ca.us </procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20060417</date>
<time Sync="TRUE">13385700</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20061218</date>
<time Sync="TRUE">08310600</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20070510</date>
<time Sync="TRUE">10182200</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20081012</procdate>
<proctime Sync="TRUE">22261800</proctime>
</procstep>
<srcinfo>
<srctime>
<timeinfo>
<sngdate>
<caldate>12/30/2008</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
</srcinfo>
</lineage>
</dataqual>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 12.2.0.12813</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Zoning</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">5687189.803</westBL>
<eastBL Sync="TRUE">6201605.5</eastBL>
<northBL Sync="TRUE">2229048</northBL>
<southBL Sync="TRUE">1808592.5</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-121.991663</westBL>
<eastBL Sync="TRUE">-120.213947</eastBL>
<northBL Sync="TRUE">36.943886</northBL>
<southBL Sync="TRUE">35.758423</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-121.991663</westBL>
<eastBL Sync="TRUE">-120.213947</eastBL>
<northBL Sync="TRUE">36.943886</northBL>
<southBL Sync="TRUE">35.758423</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idPurp>This layer was developed to assist in the processing of planning and building permits. Please refer to Zoning Ordinances for explanation of zoning categories and regulations: Title 20 for Coastal and Title 21 for Inland.</idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The zoning112002.shp layer represents the zoning designations for all unincorporated areas of Monterey County. This digital map is meant to replicate and replace the county's existing hardcopy zoning maps. There are currently 45 areas that have been labeled 'Under Review' in this layer. Zoning for projects in one of these areas will have to be determined using the hardcopy Sectional District Maps.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>Planning</keyword>
<keyword>zoning</keyword>
</searchKeys>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;NOT FOR LEGAL USE. This data is not the official zoning for Monterey County. The official zoning is that which is on the zoning map mylars kept on file in the Planning Department. This layer is an attempt to replicate those maps. Where there are differences between this layer and the official maps; the official maps take precedence.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Note: Zoning District boundaries often follow parcel lines, when this is the case, the zoning layer was "snapped' to the parcel boundary. After the creation of this data, the Assessor's Office made changes or corrections to the parcel layer; as a result, the zoning and parcel layers may no longer be in sync. The result is that a zoning district boundary may display as being slightly off from a parcel line.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
</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>
<cntorgp>
<cntper>REQUIRED: The person responsible for the metadata information.</cntper>
<cntorg>REQUIRED: The organization responsible for the metadata information.</cntorg>
</cntorgp>
<cntaddr>
<addrtype>REQUIRED: The mailing and/or physical address for the organization or individual.</addrtype>
<city>REQUIRED: The city of the address.</city>
<state>REQUIRED: The state or province of the address.</state>
<postal>REQUIRED: The ZIP or other postal code of the address.</postal>
</cntaddr>
<cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice>
</cntinfo>
</metc>
<metd Sync="TRUE">20081230</metd>
</metainfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd Sync="TRUE" value="005"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<distinfo>
<resdesc Sync="TRUE">Downloadable Data</resdesc>
<stdorder>
<digform>
<digtinfo>
<transize Sync="TRUE">12.653</transize>
<dssize Sync="TRUE">12.653</dssize>
</digtinfo>
</digform>
</stdorder>
</distinfo>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="Zoning">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">1</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_StatePlane_California_IV_FIPS_0404_Feet</projcsn>
</cordsysn>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<plandu Sync="TRUE">survey feet</plandu>
<coordrep>
<absres Sync="TRUE">0.000250</absres>
<ordres Sync="TRUE">0.000250</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">1.000000</altres>
</altsys>
</vertdef>
</spref>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2228">NAD_1983_StatePlane_California_IV_FIPS_0404_Feet</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Zoning">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">1</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<eainfo>
<detailed Name="Zoning">
<enttyp>
<enttypl Sync="FALSE">Zoning</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">1</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">AREA_PLAN</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">5</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">AREA_PLAN</attrlabl>
<attalias Sync="TRUE">ZONE_CATEG</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">ZONE_CATEG</attrlabl>
<attalias Sync="TRUE">ZONE_DENSI</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">ZONE_DENSI</attrlabl>
<attalias Sync="TRUE">COMB_REG_A</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">16</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">COMB_REG_A</attrlabl>
<attalias Sync="TRUE">COMB_REG_B</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">16</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">COMB_REG_B</attrlabl>
<attalias Sync="TRUE">COMB_REG_C</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">16</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">COMB_REG_C</attrlabl>
<attalias Sync="TRUE">COMB_REG_D</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">16</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">COMB_REG_D</attrlabl>
<attalias Sync="TRUE">HEIGHT</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">HEIGHT</attrlabl>
<attalias Sync="TRUE">NOTES</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">250</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">NOTES</attrlabl>
<attalias Sync="TRUE">RECNO</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">11</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">RECNO</attrlabl>
<attalias Sync="TRUE">ZONESTRING</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</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">ZONESTRING</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">OBJECTID</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">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">AT_ACRES</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">16</atprecis>
<attscale Sync="TRUE">3</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">AT_ACRES</attrlabl>
<attalias Sync="TRUE">SHAPE.AREA</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.AREA</attrlabl>
<attalias Sync="TRUE">SHAPE.LEN</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.LEN</attrlabl>
<attalias Sync="TRUE">PERIMETER</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">16</atprecis>
<attscale Sync="TRUE">3</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PERIMETER</attrlabl>
<attalias Sync="TRUE">SHAPE.AREA</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">20180711</mdDateSt>
</metadata>
