<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20220201</CreaDate>
<CreaTime>15163200</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">Parcel_2021_dslv_pin10</itemName>
<nativeExtBox>
<westBL Sync="TRUE">1003175.748000</westBL>
<eastBL Sync="TRUE">1205633.622000</eastBL>
<southBL Sync="TRUE">1749884.652250</southBL>
<northBL Sync="TRUE">1998851.705000</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<imsContentType Sync="TRUE">002</imsContentType>
</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_Illinois_East_FIPS_1201_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/3.3.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_Illinois_East_FIPS_1201_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;,984250.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-88.33333333333333],PARAMETER[&amp;quot;Scale_Factor&amp;quot;,0.999975],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,36.66666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,3435]]&lt;/WKT&gt;&lt;XOrigin&gt;-17463800&lt;/XOrigin&gt;&lt;YOrigin&gt;-46132600&lt;/YOrigin&gt;&lt;XYScale&gt;4000&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.002&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;102671&lt;/WKID&gt;&lt;LatestWKID&gt;3435&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20250409</SyncDate>
<SyncTime>11055200</SyncTime>
<ModDate>20250411</ModDate>
<ModTime>8501500</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISProfile>ItemDescription</ArcGISProfile>
</Esri>
<eainfo>
<detailed Name="Parcel_2021_dslv_pin10">
<enttyp>
<enttypl Sync="TRUE">Parcel_2021_dslv_pin10</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">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">PIN10</attrlabl>
<attalias Sync="TRUE">PIN10</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</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">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">SHAPE_Length</attrlabl>
<attalias Sync="TRUE">SHAPE_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE_Area</attrlabl>
<attalias Sync="TRUE">SHAPE_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<rpIndName>Linda Schwab</rpIndName>
<rpOrgName>Northeastern Illinois Planning Commission</rpOrgName>
<rpPosName>Metadata Specialist/GIS Analyst</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>312/454-0400</voiceNum>
<faxNum>312/454-0411</faxNum>
</cntPhone>
<cntAddress>
<delPoint>222 S. Riverside Plaza, Suite 1800</delPoint>
<city>Chicago</city>
<adminArea>Illinois</adminArea>
<postCode>60606</postCode>
<country>US</country>
<eMailAdd>lschwab@nipc.org</eMailAdd>
</cntAddress>
<cntHours>09:00 - 17:00, Central Time Zone, Monday-Friday, except holidays</cntHours>
<cntInstr>Please contact during normal business hours</cntInstr>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20250411</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Tanya Anthofer</rpIndName>
<rpOrgName>Office of the Cook County Clerk</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>312-603-6229</voiceNum>
<faxNum>312-603-6717</faxNum>
</cntPhone>
<cntAddress>
<delPoint>Cook County Clerk Room 434 Map Dept 118 N. Clark St</delPoint>
<city>Chicago</city>
<adminArea>Illinois</adminArea>
<postCode>60602</postCode>
<country>US</country>
<eMailAdd>TANTHOF@cookcountygov.com</eMailAdd>
</cntAddress>
<cntHours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<planAvDtTm>2002-02-01T00:00:00</planAvDtTm>
<ordInstr>Call the individual listed as the Contact_Person in the Distribution_Information section of this metadata record to find out how to obtain this data set, the available formats, the available transfer media, compatibility, etc. This person will also be able to provide information about the fees associated with obtaining the data set.</ordInstr>
</distorOrdPrc>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="TRUE">Parcel_2021_dslv_pin10</resTitle>
<date>
<pubDate>2002-02-01T00:00:00</pubDate>
</date>
<resEd>2001</resEd>
<citRespParty>
<rpOrgName>Cook County Board of Commissioners</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Chicago, Illinois</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Cook County Board of Commissioners</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;This data set contains parcel polygon, tax block polygon, and leasehold polygon features classes, as well as several object classes (tables), for Cook County, Illinois, including a PIN table, a Ref_PIN table, a condo table, and a condo miscellaneous table. The cadastral data for Cook County have previously not been digital nor automated. This project is the initial automation for this information. This database was designed to represent a continuous, non-overlapping spatial database accounting for all land area in Cook County.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>In the cadastral database model, atomic polygons were aggregated to the level of parcel polygons by a unique PIN. This was accomplished by using a master PIN object class (table) that is linked by the key REF_PIN to the parcel feature class. REF_PIN is unique for each parcel polygon shown on the tax map. The PIN table is needed because a single parcel polygon can represent more than one parcel as in the case of condominiums and elevation specific parcels. The attribute POLYTYPE is a flag that specifies that this condition exists and indicates the need to query additional tables. In addition to parcels that have only one PIN per polygon, the PIN table accommodates PINs for condominiums, leaseholds, and elevation-specific parcels. The PIN table contains records for each unique 14-digit PIN (the basic 10-digit PIN plus a 4-digit unit number for condominiums and leaseholds). The base 10-digit PIN is included in the table as well as the four components, PINA, PINSA, PINB, and PINP, which comprise the 10-digit PIN. The Cadastral data set is a depiction of taxable properties in Cook County with selected associated features for enhancement. The purpose of creating this cadastral geodatabase was to update previous data sets and integrate the data with other data sets based on a common geography (digital orthophotoimagery), and serve as a standard cadastral database for virtually all cadastral applications in the County. The creation of this digital cadastral database will allow Cook County to supplant hard-copy tax maps, which are used to illustrate parcel boundaries, with a comprehensive GIS database referenced to an accurate planimetric base map and digital orthoimagery. The County will thus be able to perform maintenance of its land records in the GIS database and automate queries and map output. The Cook County Assessor will not use this database for assessment purposes (such as area of the property). However, the tax map serves the Cook County Clerk to graphically depict legal descriptions of all parcels in Cook County as the tax map represents them. The primary sources of data for the Cook County cadastral GIS database are the approximately 8,800 tax map "pages" maintained by the Cook County Clerk's Office. All information appearing on existing tax maps as of tax years 2000 or 2001 was incorporated into the cadastral database. The maps are maintained by the Clerk's Office on Mylar and have been published annually. The County's system of tax maps is based on the Illinois Public Land Survey System (PLSS). In the PLSS, each township is divided into 36 sections, and each section into four quarter-sections. A quarter-section is further divided into two tax map sheets, often called "pages". Each tax map (1/4 mile by 1/2 mile) represents the east or west half of one quarter-section, and typically there are eight tax maps per section. There can be additional pages, known as "flysheets" or "flyleaves", which provide additional information as to subdivisions, condominium/unit, and floor-plans/elevations. It is not intended that the digital cadastral feature data set should match perfectly with the digital orthoimagery, but rather that it match relatively well so that the digital orthoimagery would provide a visual backdrop to the cadastral information and replicate the tax maps. The tax maps themselves are graphical representations of legal descriptions but cannot be used in place of legal descriptions. As such, this digital cadastral database should not be used in place of legal descriptions, where warranted.</idPurp>
<idCredit>Cook County GIS</idCredit>
<idStatus>
<ProgCd value="007"/>
</idStatus>
<idPoC>
<rpIndName>Tanya Anthofer</rpIndName>
<rpOrgName>Office of the Cook County Clerk</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>312-603-6229</voiceNum>
<faxNum>312-603-6717</faxNum>
</cntPhone>
<cntAddress>
<delPoint>Cook County Clerk Room 434 Map Dept 118 N. Clark St</delPoint>
<city>Chicago</city>
<adminArea>Illinois</adminArea>
<postCode>60602</postCode>
<country>US</country>
<eMailAdd>TANTHOF@cookcountygov.com</eMailAdd>
</cntAddress>
<cntHours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<placeKeys>
<keyword>Thorton</keyword>
<keyword>Bremen</keyword>
<keyword>River Forest</keyword>
<keyword>Bloom</keyword>
<keyword>New Trier</keyword>
<keyword>Jefferson</keyword>
<keyword>North</keyword>
<keyword>Chicago</keyword>
<keyword>Worth</keyword>
<keyword>Barrington</keyword>
<keyword>northeastern Illinois</keyword>
<keyword>Maine</keyword>
<keyword>South</keyword>
<keyword>Cicero</keyword>
<keyword>Elk Grove</keyword>
<keyword>Hyde Park</keyword>
<keyword>Leyden</keyword>
<keyword>Calumet</keyword>
<keyword>Stickney</keyword>
<keyword>Lyons</keyword>
<keyword>Hanover</keyword>
<keyword>Wheeling</keyword>
<keyword>Oak Park</keyword>
<keyword>Palos</keyword>
<keyword>Orland</keyword>
<keyword>Palatine</keyword>
<keyword>Norwood Park</keyword>
<keyword>Rich</keyword>
<keyword>Illinois</keyword>
<keyword>Evanston</keyword>
<keyword>Northfield</keyword>
<keyword>Riverside</keyword>
<keyword>West</keyword>
<keyword>Lemont</keyword>
<keyword>Niles</keyword>
<keyword>Cook County</keyword>
<keyword>Lake View</keyword>
<keyword>Rogers Park</keyword>
<keyword>Lake</keyword>
<keyword>Proviso</keyword>
<keyword>Berwyn</keyword>
<keyword>Schaumburg</keyword>
</placeKeys>
<themeKeys>
<keyword>property</keyword>
<keyword>cadastral</keyword>
<keyword>condominium</keyword>
<keyword>parcel</keyword>
<keyword>lease</keyword>
<keyword>PIN</keyword>
<keyword>tax map</keyword>
<keyword>tax block</keyword>
</themeKeys>
<searchKeys>
<keyword>Thorton</keyword>
<keyword>Bremen</keyword>
<keyword>River Forest</keyword>
<keyword>Bloom</keyword>
<keyword>New Trier</keyword>
<keyword>Jefferson</keyword>
<keyword>North</keyword>
<keyword>Chicago</keyword>
<keyword>property</keyword>
<keyword>Worth</keyword>
<keyword>Barrington</keyword>
<keyword>cadastral</keyword>
<keyword>condominium</keyword>
<keyword>northeastern Illinois</keyword>
<keyword>Maine</keyword>
<keyword>South</keyword>
<keyword>Cicero</keyword>
<keyword>Elk Grove</keyword>
<keyword>parcel</keyword>
<keyword>Hyde Park</keyword>
<keyword>Leyden</keyword>
<keyword>Calumet</keyword>
<keyword>lease</keyword>
<keyword>PIN</keyword>
<keyword>Stickney</keyword>
<keyword>Lyons</keyword>
<keyword>Hanover</keyword>
<keyword>Wheeling</keyword>
<keyword>Oak Park</keyword>
<keyword>tax map</keyword>
<keyword>Palos</keyword>
<keyword>Orland</keyword>
<keyword>tax block</keyword>
<keyword>Palatine</keyword>
<keyword>Norwood Park</keyword>
<keyword>Rich</keyword>
<keyword>Illinois</keyword>
<keyword>Evanston</keyword>
<keyword>Northfield</keyword>
<keyword>Riverside</keyword>
<keyword>West</keyword>
<keyword>Lemont</keyword>
<keyword>Niles</keyword>
<keyword>Cook County</keyword>
<keyword>Lake View</keyword>
<keyword>Rogers Park</keyword>
<keyword>Lake</keyword>
<keyword>Proviso</keyword>
<keyword>Berwyn</keyword>
<keyword>Schaumburg</keyword>
</searchKeys>
<resConst>
<LegConsts>
<useLimit>Cook County is committed to offering its data users accurate, useful and current information. Although every effort has been made to ensure the accuracy of information, errors and conditions originating from physical sources used to develop the database may be reflected in the data supplied. The client must be aware of data conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data and other conditions specific to certain data. No warranty expressed or implied is made by Cook County regarding the accuracy or utility of this information.</useLimit>
<othConsts>There may be attributes for this dataset which are listed in this metadata record but which the recipient will not receive. These portions of the dataset are for internal use by Cook County only and are not subject to distribution.</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Under no circumstances may the data be redistributed or made available over a network without explicit permission from the Cook County Department of Office Technology. It is required that the Cook County Board of Commissioners be cited in any products generated from the data. The following source citation must be included: "Source: Cook County, Illinois 1:1200-Scale Parcel Digital Data Set, Version 1.0, June 2002."&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<envirDesc Sync="FALSE">Esri ArcGIS 13.3.2.52636</envirDesc>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period gmlID="ID0E4RBG">
<tmBegin>2000-01-01T00:00:00</tmBegin>
<tmEnd>2001-01-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox>
<exTypeCode>true</exTypeCode>
<westBL>-88.264274</westBL>
<eastBL>-87.346143</eastBL>
<southBL>41.467005</southBL>
<northBL>42.154371</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<suppInfo>This cadastral feature data set was originally developed as an ArcInfo coverage. Throughout the metadata, there will be information pertaining to the general data, as well as more specific information referring to the data when obtained and used as an ArcInfo coverage, and an ArcGIS geodatabase. In metadata fields where specific information is required, it will be listed in the same order. The original data set was created as an ArcInfo coverage and was later converted to an ArcGIS geodatabase. The current data format, as used by the Cook County government, is a geodatabase. The ArcInfo geodatabase model supports topologically integrated feature classes similar to the ArcInfo coverage model but extends the coverage model to support relationship classes, complex networks, and object-oriented features. Geodatabases contain feature classes (which can be organized into feature datasets) and tables. For more information about the use and format of ArcGIS geodatabases, please consult the Environmental Systems Research Institute (ESRI) web page at http://www.esri.com. This data set is one in a series of five cadastral data sets for Cook County, Illinois. In the cadastral database model, atomic polygons have been aggregated into various layers based on key attributes. Each layer may then be linked to ancillary tables and objects based on its key attribute. For information regarding available distribution formats, please contact the individual listed as the Contact_Person in the Distribution_Information section of this metadata document.</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-88.264274</westBL>
<eastBL Sync="TRUE">-87.516926</eastBL>
<northBL Sync="TRUE">42.154371</northBL>
<southBL Sync="TRUE">41.468316</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="012"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="012"/>
</maintFreq>
<dateNext>20020630</dateNext>
<maintNote>Last metadata review date: 20020626</maintNote>
</mdMaint>
<mdConst>
<Consts>
<useLimit>This metadata file is intended to accompany the geospatial data set identified and received from Cook County. It is not to be altered or summarized. Cook County does not support secondary distribution. If this geospatial data set was received from anyone besides the Cook County Department of Office Technology or the Cook County Assessor's Office, this metadata file and the geospatial data set it describes may lack integrity.</useLimit>
</Consts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQCompOm">
<measDesc>This feature data set includes all features found on the Cook County Tax Maps as of 1 February 2001. Completeness is judged to be excellent, based on repeated examination and usage.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>Features are stored in double precision, using ESRI ARCGIS 8.x software, as a geodatabase. As cadastral features were digitized from paper tax maps and completed, they were checked against those images adjacent to them to ensure correct edgematching and completeness and correct coding of and lines which crossed onto adjoining images.</measDesc>
</report>
<report type="DQAbsExtPosAcc">
<measDesc>This data set was created in part using digital orthoimagery as a base, which meets National Map Accuracy Standards for 1"=100' data products, and has an absolute horizontal positional accuracy of +/- 2.5 feet (+/- 0.7625 meters). Additionally, this data set was subjected to numerous vendor automatic and manual quality control checks to ensure the positional accuracy of the data set throughout the processing.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>The attributes in this data set are estimated to have very good accuracy, to a contract-specified level of 98% accuracy. This data set and its attributes were subjected to extensive quality control checks, both automated and manual/visual, throughout its development. The QC was performed by the vendor(s) creating the data set, while the final quality inspection and approval of the data set was performed by staff of Cook County.</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>9.0 Final Quality Control of Deliverables: The QC_Tax_Map_Regions was sent from SDS and GIS Data to ESRI Redlands, the primary contractor for this project. ESRI Redlands then sent QC_Tax_Map_Regions to one of two quality control contractors - either Catalyst Consulting, Inc., (Catalyst) or Spatial Data Integrations, Inc., (SDI). ESRI Redlands may have also performed some in-house quality control analysis on QC_Tax_Map_Regions delivered from GIS Data. In any case, the quality control contractors verified the overall quality of the QC_Tax_Map_Regions delivered using ESRI QC View software and ArcView. If the quality was not acceptable, the data set was sent back to the original developing contractor (SDS or GIS Data) for corrections. Any corrected data was then reviewed once again by either Catalyst or SDI or by ESRI Redlands for overall quality until it was acceptable.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>ESRI Redlands</rpOrgName>
<rpPosName>Project Leader</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909-793-2853</voiceNum>
<faxNum>909-307-3025</faxNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>CA</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Vendor_QC_Tax_Map_Regions.</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>QC_Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>10.0 Cook County Quality Control of Deliverables: Following review by Catalyst or SDI, ESRI Redlands delivered the Vendor_QC_Tax_Map_Regions to Cook County. Using ArcView, Cook County performed its own QC of this coverage data. If the quality was not acceptable, the data set was returned to ESRI Redlands who either returned it to the original conversion subcontractor or performed the corrections themselves.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>ESRI Redlands</rpOrgName>
<rpPosName>Project Leader</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909-793-2853</voiceNum>
<faxNum>909-307-3025</faxNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>CA</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepProc>
<rpIndName>Tanya Anthofer</rpIndName>
<rpOrgName>Office of the Cook County Clerk</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>312-603-6229</voiceNum>
<faxNum>312-603-6717</faxNum>
</cntPhone>
<cntAddress>
<delPoint>Cook County Clerk Room 434 Map Dept 118 N. Clark St</delPoint>
<city>Chicago</city>
<adminArea>IL</adminArea>
<postCode>60602</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Vendor_QC_Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Final_Cook_QC_Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>5.0 Edgematching: Each consultant (GIS Data and SDS) performed typical automatic and visual edgematching procedures throughout the processing. These procedures included customized routines to verify geometric and attribute edgematching.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Various_Process_Outputs</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Various_Process_Outputs</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>1.0 Scan Tax Maps: TeamWerks, Inc. (TeamWerks) scanned all available current (as of 2000) Cook County Tax Maps (Current_Tax_Maps), at a resolution of 300 dots per inch (dpi) and delivered them as TIFF images to two contractors working on the tax map processes, Smart Data Strategies, Inc. (SDS) and Catalyst Consulting Group (Catalyst).</stepDesc>
<stepDateTm date="unknown"/>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Current_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Scanned_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>3.0 Line Work Digitization: SDS and ESRI (Thailand) Co. Ltd. (GIS Data) digitized line work from the Georeferenced_Tax_Maps. GIS Data performed line work digitization using Georeferenced_Tax_Maps from Catalyst. Although SDS and GIS Data used different hardware and software systems to perform these functions, both followed the same procedures with similar methods. Technicians used the Georeferenced_Tax_Maps to "heads-up" digitize and construct line work, creating parcels, blocks, subdivisions, and rights-of-way. All boundary information was placed, such as subdivision, block, and page boundaries. The "Best Fit" concept was used in the production by SDS. The parcels were digitized using 1998_Digital_Orthophotos and Georeferenced_Tax_Maps as background sources, as the technician used ground evidence to register the property boundaries. Fence lines, hedgerows, building outlines, ditch lines, lakes, and streams, along with the Georeferenced_Tax_Maps were used to determine parcel lines and other boundaries. SDS technicians aligned small blocks of parcels to the ground evidence base (1998_Digital_Orthophotos) and then performed line work digitization. This process thus provided an accurate approach to parcel conversion and isolated parcels requiring rigorous editing. Automatic quality control checks were placed throughout the production flow in order to identify errors or omissions early in the conversion process. GIS Data performed heads-up digitization of line work directly from the Georeferenced_Tax_Maps. The 1998_Digital_Orthophotos were used for reference to resolve conflicts and make some boundary determinations. Please refer to the document "GIS Database Development Procedures Manual, Final Version, May 2001", by ESRI, for production rules. This document may be obtained from the Cook County Assessor's Office or from the Cook County Department of Office Technology.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>1998_Digital_Orthophotos, Georeferenced_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Georeferenced_Digitized_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>4.0 Adding Annotation: Annotation was added to the Georeferenced_Digitized_Tax_Maps to reflect all of the annotation information on the original Current_Tax_Maps. In urban areas, this typically included parcel number, dimensions, street names, block numbers, and subdivision reference and section numbers, among other features. Cook County approved all fonts and sizes as well as placement criteria, which were developed according to the Current_Tax_Maps.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Georeferenced_Digitized_Tax_Maps, Current_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Annotated_Georeferenced_Digitized_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>6.0 Quality Assurance/Quality Control: Rigid in-process and postprocess QC measures were implemented throughout the processing to ensure the delivery of quality data. Internal QC processes were performed by the edit staff followed by the contractors' QA/QC management teams. Digital files were required to pass each phase of the QA/QC process with complete accuracy prior to their delivery to Cook County. To supplement on-screen edit processes, hard-copy plots were created to assist editing technicians in reviewing the map data. All plots were checked against the original source documents to ensure accuracy and quality. Automated digital checks were also performed. All parcel line work and annotation were validated by quality audits at several points in the processing.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>QC_Annotated_Georeferenced_Digitized_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Various_Process_Outputs</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>7.0 Translation into ArcInfo: GIS Data performed their work in the ArcInfo environment; thus, no translation was required. GIS Data created Region Subclasses from the linework polygons for subdivisions, blocks, parcels, lots, and ROW and the associated Regions tables were populated. For work performed by SDS, the QC_Annotated_Georeferenced_Digitized_Tax_Maps were translated from MicroStation to ArcInfo format. First, SDS used the ArcInfo IGDSARC command to translate the MicroStation file into a Master_Coverage. As objects in the Master_Coverage were coded into distinct ArcInfo objects, they were verified by proprietary macros to be free of dangles and topology errors. Then, those verified objects were removed from the Master_Coverage until all objects were translated. Automated procedures were then utilized to build polygons using the ArcInfo CLEAN command. The resulting polygons were attributed with the original annotation text and the ArcInfo REGIONDISSOLVE command was issued to create regions from the various polygons.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>QC_Annotated_Georeferenced_Digitized_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>2.0 Georeferencing Tax Maps: SDS georeferenced their project area's Scanned_Tax_Maps to the 1998_Digital_Orthophotos base by aligning common road intersections observed on each. Where Scanned_Tax_Maps did not have a sufficient number of road intersections for georeferencing, SDS technicians visually aligned the Scanned_Tax_Maps to the 1998_Digital_Orthophotos using obvious occupation lines. Thus, real-world coordinates were established as control points for the georeferencing process. This georeferencing step was also performed by Catalyst for the geographical area not covered by SDS. Catalyst then sent their output product to GIS Data (ESRI [Thailand] Co. Ltd.) (GIS Data).</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Georeferenced_Tax_Maps</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Scanned_Tax_Maps, 1998_Digital_Orthoimagery</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>8.0 Quality Control of ArcInfo Database: To verify that the data in Tax_Map_Regions was captured correctly and that the ArcInfo database structure conformed to Cook County specifications, ESRI QCView software was used as part of the automated control process, and ArcView was used for visual verification by GIS Data. Coverages and themes were validated to ensure that they contained the appropriate feature classes and subclasses, and individual attribute item definitions were checked. Additionally, project parameters such as map projection, units, and applicable map scales were validated.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</rpOrgName>
<rpPosName>Project Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909/793-2853</voiceNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>California</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
<eMailAdd>professionalservices@esri.com</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>QC_Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<prcStep>
<stepDesc>11.0 Convert to ArcGIS 8.2 Geodatabase: ESRI Redlands developed a coverage-to-geodatabase conversion module and converted the completed cadastral tax map (Final_Cook_QC_Tax_Map_Regions) data from ArcInfo coverage format to ArcGIS geodatabase format. ESRI Redlands then validated the conversion by reviewing the conversion statistics and checking the data within the geodatabase to ensure that no data was lost or corrupted.</stepDesc>
<stepProc>
<rpIndName>Charlie Wells</rpIndName>
<rpOrgName>ESRI Redlands</rpOrgName>
<rpPosName>Project Leader</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>909-793-2853</voiceNum>
<faxNum>909-307-3025</faxNum>
</cntPhone>
<cntAddress>
<delPoint>380 New York Street</delPoint>
<city>Redlands</city>
<adminArea>CA</adminArea>
<postCode>92373-8100</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepProc>
<rpIndName>Tanya Anthofer</rpIndName>
<rpOrgName>Office of the Cook County Clerk</rpOrgName>
<rpPosName>GIS Manager</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>312-603-6229</voiceNum>
<faxNum>312-603-6717</faxNum>
</cntPhone>
<cntAddress>
<delPoint>Cook County Clerk Room 434 Map Dept 118 N. Clark St</delPoint>
<city>Chicago</city>
<adminArea>IL</adminArea>
<postCode>60602</postCode>
<country>US</country>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc>
<srcCitatn>
<resAltTitle>Tax_Map_Geodatabase</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc>
<srcCitatn>
<resAltTitle>Final_Cook_QC_Tax_Map_Regions</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<dataSource>
<srcDesc>Provided background base for verification of geographical accuracy of data set.</srcDesc>
<srcScale>
<rfDenom>1200</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Cook County, Illinois 1998 1:1200-scale Black and White Digital Orthoimagery, February 2002</resTitle>
<resAltTitle>1998_Digital_Orthoimagery</resAltTitle>
<date>
<pubDate>1998-01-01T00:00:00</pubDate>
</date>
<resEd>1.0</resEd>
<citRespParty>
<rpOrgName>Cook County Board of Commissioners</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Cook County Board of Commissioners</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Chicago, Illinois</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant gmlID="ID0E6SAI">
<tmPosition>1998-04-19T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant gmlID="ID0E2TAI">
<tmPosition>1998-04-23T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant gmlID="ID0ENTAI">
<tmPosition>1998-04-18T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant gmlID="ID0ERSAI">
<tmPosition>1998-04-17T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>The mylar tax maps provided the base from which the digital cadastral data layers were created.</srcDesc>
<srcScale>
<rfDenom>1200</rfDenom>
</srcScale>
<srcCitatn>
<resTitle>Cook County Tax Maps</resTitle>
<resAltTitle>Current_Tax_Maps</resAltTitle>
<date>
<pubDate>2001-02-01T00:00:00</pubDate>
</date>
<citRespParty>
<rpOrgName>Cook County Clerk and Cook County Board of Commissioners</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Cook County Board of Commissioners</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Chicago, Illinois</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<otherCitDet>8,800 plus map sheets</otherCitDet>
</srcCitatn>
<srcExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period gmlID="ID0EVPAI">
<tmBegin>2000-01-01T00:00:00</tmBegin>
<tmEnd>2001-01-01T00:00:00</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
</dataSource>
</dataLineage>
</dqInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Parcel_2021_dslv_pin10">
<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="3435"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.9.3(9.3.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Parcel_2021_dslv_pin10">
<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>
</metadata>
