<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Cook County Board of Commissioners</origin>
<pubdate>20020201</pubdate>
<title Sync="TRUE">gis.GIS.Parcel</title>
<edition>2001</edition>
<geoform Sync="TRUE">vector digital data</geoform>
<pubinfo>
<pubplace>Chicago, Illinois</pubplace>
<publish>Cook County Board of Commissioners</publish>
</pubinfo>
<onlink Sync="FALSE">withheld</onlink>
<ftname Sync="TRUE">gis.GIS.Parcel</ftname>
</citeinfo>
</citation>
<descript>
<abstract>
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.
</abstract>
<purpose>
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.
</purpose>
<supplinf>
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.
</supplinf>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>2000</begdate>
<enddate>2001</enddate>
</rngdates>
<sngdate>
<caldate>REQUIRED: The year (and optionally month, or month and day) for which the data set corresponds to the ground.</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>In Work</progress>
<update>Tax maps are published once every calendar year, on February 1</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-88.264274</westbc>
<eastbc Sync="TRUE">-87.516926</eastbc>
<northbc Sync="TRUE">42.154371</northbc>
<southbc Sync="TRUE">41.468316</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">1003175.748000</leftbc>
<rightbc Sync="TRUE">1205633.622000</rightbc>
<bottombc Sync="TRUE">1749884.652000</bottombc>
<topbc Sync="TRUE">1998851.705000</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>parcel</themekey>
<themekey>cadastral</themekey>
<themekey>tax map</themekey>
<themekey>property</themekey>
<themekey>tax block</themekey>
<themekey>lease</themekey>
<themekey>condominium</themekey>
<themekey>PIN</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Cook County</placekey>
<placekey>Chicago</placekey>
<placekey>Illinois</placekey>
<placekey>northeastern Illinois</placekey>
<placekey>Barrington</placekey>
<placekey>Berwyn</placekey>
<placekey>Bloom</placekey>
<placekey>Bremen</placekey>
<placekey>Calumet</placekey>
<placekey>Cicero</placekey>
<placekey>Elk Grove</placekey>
<placekey>Evanston</placekey>
<placekey>Hanover</placekey>
<placekey>Hyde Park</placekey>
<placekey>Jefferson</placekey>
<placekey>Lake</placekey>
<placekey>Lake View</placekey>
<placekey>Lemont</placekey>
<placekey>Leyden</placekey>
<placekey>Lyons</placekey>
<placekey>Maine</placekey>
<placekey>New Trier</placekey>
<placekey>Niles</placekey>
<placekey>North</placekey>
<placekey>Northfield</placekey>
<placekey>Norwood Park</placekey>
<placekey>Oak Park</placekey>
<placekey>Orland</placekey>
<placekey>Palatine</placekey>
<placekey>Palos</placekey>
<placekey>Proviso</placekey>
<placekey>Rich</placekey>
<placekey>River Forest</placekey>
<placekey>Riverside</placekey>
<placekey>Rogers Park</placekey>
<placekey>Schaumburg</placekey>
<placekey>South</placekey>
<placekey>Stickney</placekey>
<placekey>Thorton</placekey>
<placekey>West</placekey>
<placekey>Wheeling</placekey>
<placekey>Worth</placekey>
</place>
</keywords>
<accconst>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.</accconst>
<useconst>
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."
</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Office of the Cook County Clerk</cntorg>
<cntper>Tanya Anthofer</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
Cook County Clerk
Room 434 Map Dept
118 N. Clark St
</address>
<city>Chicago</city>
<state>Illinois</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-6229</cntvoice>
<cntfax>312-603-6717</cntfax>
<cntemail>TANTHOF@cookcountygov.com</cntemail>
<hours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</hours>
</cntinfo>
</ptcontac>
<datacred>David Orr, Cook County Clerk, was instrumental in the process of creating digital cadastral data layers for Cook County, Illinois.</datacred>
<native Sync="FALSE">ESRI ArcCatalog 9.3.1.4000</native>
<natvform Sync="FALSE">Feature Class</natvform>
</idinfo>
<dataqual>
<attracc>
<attraccr>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.</attraccr>
</attracc>
<logic>
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.
</logic>
<complete>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.</complete>
<posacc>
<horizpa>
<horizpar>
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.
</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Cook County Board of Commissioners</origin>
<pubdate>1998</pubdate>
<title>Cook County, Illinois 1998 1:1200-scale Black and White Digital Orthoimagery, February 2002</title>
<edition>1.0</edition>
<geoform>raster digital data</geoform>
<pubinfo>
<pubplace>Chicago, Illinois</pubplace>
<publish>Cook County Board of Commissioners</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>1200</srcscale>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<mdattim>
<sngdate>
<caldate>19980417</caldate>
</sngdate>
<sngdate>
<caldate>19980418</caldate>
</sngdate>
<sngdate>
<caldate>19980419</caldate>
</sngdate>
<sngdate>
<caldate>19980423</caldate>
</sngdate>
</mdattim>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>1998_Digital_Orthoimagery</srccitea>
<srccontr>Provided background base for verification of geographical accuracy of data set.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Cook County Clerk and Cook County Board of Commissioners</origin>
<pubdate>20010201</pubdate>
<title>Cook County Tax Maps</title>
<geoform>multiple map pages</geoform>
<pubinfo>
<pubplace>Chicago, Illinois</pubplace>
<publish>Cook County Board of Commissioners</publish>
</pubinfo>
<othercit>8,800 plus map sheets</othercit>
<onlink>withheld</onlink>
</citeinfo>
</srccite>
<srcscale>1200</srcscale>
<typesrc>stable-base material</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>2000</begdate>
<enddate>2001</enddate>
</rngdates>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>Current_Tax_Maps</srccitea>
<srccontr>The mylar tax maps provided the base from which the digital cadastral data layers were created.</srccontr>
</srcinfo>
<procstep>
<procdesc>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).</procdesc>
<srcused>withheld</srcused>
<procdate>2000-2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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).</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
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.
</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
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.
</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute, Inc. (ESRI), Professional Services</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Manager</cntpos>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>California</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909/793-2853</cntvoice>
<cntemail>professionalservices@esri.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>ESRI Redlands</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Leader</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>CA</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909-793-2853</cntvoice>
<cntfax>909-307-3025</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2000 - 2002</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>ESRI Redlands</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Leader</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>CA</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909-793-2853</cntvoice>
<cntfax>909-307-3025</cntfax>
</cntinfo>
</proccont>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Office of the Cook County Clerk</cntorg>
<cntper>Tanya Anthofer</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
Cook County Clerk
Room 434 Map Dept
118 N. Clark St
</address>
<city>Chicago</city>
<state>IL</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-6229</cntvoice>
<cntfax>312-603-6717</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>withheld</srcused>
<procdate>2002 - Present</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>ESRI Redlands</cntorg>
<cntper>Charlie Wells</cntper>
</cntorgp>
<cntpos>Project Leader</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>380 New York Street</address>
<city>Redlands</city>
<state>CA</state>
<postal>92373-8100</postal>
<country>USA</country>
</cntaddr>
<cntvoice>909-793-2853</cntvoice>
<cntfax>909-307-3025</cntfax>
</cntinfo>
</proccont>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Office of the Cook County Clerk</cntorg>
<cntper>Tanya Anthofer</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
Cook County Clerk
Room 434 Map Dept
118 N. Clark St
</address>
<city>Chicago</city>
<state>IL</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-6229</cntvoice>
<cntfax>312-603-6717</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20040108</date>
<time Sync="TRUE">17494200</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20080124</date>
<time Sync="TRUE">19033500</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20100906</procdate>
<proctime Sync="TRUE">13563000</proctime>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20120821</procdate>
<proctime Sync="TRUE">02340500</proctime>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="CensusBlk2012_uninc">
<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>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">coordinate pair</plance>
<coordrep>
<absres Sync="TRUE">0.000250</absres>
<ordres Sync="TRUE">0.000250</ordres>
</coordrep>
<plandu Sync="TRUE">survey feet</plandu>
</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>
<cordsysn>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet</projcsn>
</cordsysn>
</horizsys>
<vertdef>
<altsys>
<altenc Sync="TRUE">Explicit elevation coordinate included with horizontal coordinates</altenc>
<altres Sync="TRUE">1.000000</altres>
</altsys>
</vertdef>
</spref>
<eainfo>
<overview>
<eaover>
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.
Originally part of the Landfabric Arc/Info coverage, parcel features have been broken out to create this ArcGIS geodatabase, comprised of feature classes and object classes. If you have requested an Arc/Info coverage format, you may receive a portion of the Landfabric coverage which will have attributes similar to those listed for the geodatabase in the following "Entity_and_Attribute_Detail_Citation" section.
</eaover>
<eadetcit>
&gt;
&gt; Description: PARCEL
&gt;
&gt; Data Dictionary: Cook County, Illinois 1:1200-Scale Parcel Digital
&gt; Data Set, Version 1.0, June 2002
&gt;
&gt; Source: Cook County Tax Map
&gt; Format: Data stored in ESRI ArcGIS version 8.x
&gt; Feature Types Maintained: Feature classes, polygons,lines, and
&gt; annotation
&gt;
&gt;----------------------------------------------------------------------
&gt;
&gt; PARCEL
&gt; Description: The feaure class Parcel contains tax parcel polygons,
&gt; which are the basic units used for property tax
&gt; assessment at the County. Each parcel is uniquely
&gt; identified with a Property Index Number (PIN). Where
&gt; multiple parcels occupy the same space on the ground,
&gt; (condominiums), a separate polygon with coincidental
&gt; geometry is represented for each of the parcels so that
&gt; each PIN is represented in the RefPIN table.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; PIN14 The 14-digit unique PIN No. 14 string
&gt; PIN10 The 10-digit number part of PIN 10 string
&gt; PINA PIN portion that is area number 2 integer
&gt; PINSA PIN portion that is subarea number 2 integer
&gt; PINB PIN portion that is block number 3 integer
&gt; PINP PIN portion that is parcel number 3 integer
&gt; PINAC PIN acreage as shown on tax map 18 double
&gt; PINU Last 4 digits of PIN14; unit no. 4 integer
&gt; TAXCODE Internal code represting a unique
&gt; combination of tax agencies 5 integer
&gt; JOB_NO Internal value used to identify
&gt; Maintenence Job that created or
&gt; altered a parcel 9 integer
&gt; PARCELTYPE Code indicating parcel type 4 integer
&gt;
&gt; PIN14
&gt; Attribute Definition: Unique PIN numbers; includes condos and
&gt; leaseholds.
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PIN10
&gt; Attribute Definition: The 10-digit number part of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINA
&gt; Attribute Definition: PIN portion that is the area number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINSA
&gt; Attribute Definition: PIN portion that is the subarea number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINB
&gt; Attribute Definition: PIN portion that is the block number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINP
&gt; Attribute Definition: PIN portion that is the parcel number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINAC
&gt; Attribute Definition: PIN acreage as shown on the tax map
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINU
&gt; Attribute Definition: Last 4 digits of PIN14; usually refers to
&gt; the unit number of the condo or leasehold.
&gt; Attribute Definition Source: Tax map
&gt;
&gt; TAXCODE
&gt; Attribute Definition: Internal code represting a unique combination of
&gt; tax agencies
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; JOB_NO
&gt; Attribute Definition: Internal value used to identify Maintenence Job
&gt; that created or altered a parcel
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt; PARCELTYPE
&gt; Attribute Definition: Code indicating parcel type
&gt; Attribute Definition Source: Tax map
&gt; Attribute Domain Values and Definitions:
&gt; "1" Condo polygon
&gt; "2" Multi-PIN polygon (elevated)
&gt; "3" Multi-lot polygon (elevated)
&gt; "4" Condo and multi-PIN and multi-lot polygon (elevated)
&gt; "5" Leasehold
&gt; "6" Elevated leasehold
&gt; "7" Outlot
&gt; "98" Normal
&gt; "99" Not a parcel
&gt;
&gt;---------------------------------------------------------------
&gt;
&gt; PIN Table
&gt; Description: The object class PIN is a table that stores a variety
&gt; of information about a PIN. It is linked to the PIN
&gt; feature class by the key PIN. The object class PIN is
&gt; used in conjunction with the object classes RefPIN and
&gt; division entry objects to manage the assignment of new
&gt; PINs during the division process. There is one record
&gt; for every active PIN in the PIN table.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; PIN14 The 14-digit unique PIN 14 string
&gt; PIN10 The 10-digit part of PIN 10 string
&gt; PINA Area No. PIN portion 2 integer
&gt; PINSA Subarea No. PIN portion 2 integer
&gt; PINB Block No. PIN portion 3 integer
&gt; PINP Parcel No. PIN portion 3 integer
&gt; PINUNIT Unit No.last 4 PIN digits 5 integer
&gt; BASE_PIN The 10-digit No.PIN part 5 string
&gt; PARCEL_ID The 10-digit No.PIN part 10 integer
&gt; REF_PIN Reference PIN 10 string
&gt; PARCEL_ADDRESS Parcel's street address 100 string
&gt; PARCEL_CITY City location of parcel 50 string
&gt; PARCEL_STATE State location of parcel 2 string
&gt; PARCEL_ZIP Parcel's Postal ZIP code 10 string
&gt; NEIGHBORHOOD Neighborhood code 10 integer
&gt; HOUSE_NO House Number 10 string
&gt; STREET_DIRECTION Street direction prefix 2 string
&gt; STREET_NAME Street Name 30 string
&gt; STREET_SUFFIX Street suffix 4 string
&gt; APT_NO Apartment number 30 string
&gt; CITY_NAME City name 30 string
&gt; STATE State 2 string
&gt; ZIP ZIP Code 9 string
&gt; OWNER_NAME Parcel owner name 50 string
&gt; OWNER_ADDRESS Owner's address 100 string
&gt; OWNER_CITY Owner's city 50 string
&gt; OWNER_STATE Owner's state 2 string
&gt; OWNER_ZIP Owner's ZIP code 9 string
&gt; PECENT_OWNERSHIP Percent ownership parcel 6 double
&gt; VOLUME Internal code used by the
&gt; Clerk for Tax Redemption
&gt; purposes 10 integer
&gt; TAXCODE Internal code represting
&gt; a unique combination of 10 integer
&gt; tax agencies
&gt; ASSESSMENT_STATUS Internal code representing
&gt; the tax assessment status
&gt; of a parcel 5 integer
&gt; EXEMPTION_CODE Exemption (nontaxed) code 2 integer
&gt; EXEMPT_AGENCY_NAME Exemption agency name 30 string
&gt; STATUS Parcel maintenence status 1 string
&gt; COMMENT_ Maintenance related note 255 string
&gt; Assessment_Land_Value Assessed land value 9 integer
&gt; Assessment_Improvement_Value Assessed improvement value 9 integer
&gt; Assessment_Total_Value Sum of land and
&gt; improvement values 9 integer
&gt; Assessment_Age Age of improvements 9 integer
&gt; Assessment_TypeResidence Residential property code 9 integer
&gt; Assessment_TypeUse Property use code 9 integer
&gt; Assessment_Improvement_Class Property improvement code 3 string
&gt; Assessment_Overall_Class Overall class code 3 string
&gt; JOB_NO Internal value used to
&gt; identify Maintenence Job
&gt; that created or altered
&gt; a parcel 9 integer
&gt;
&gt;
&gt; PIN14
&gt; Attribute Definition: Unique PIN numbers; includes condos and
&gt; leaseholds.
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PIN10
&gt; Attribute Definition: The 10-digit number part of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINA
&gt; Attribute Definition: PIN portion that is the area number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINSA
&gt; Attribute Definition: PIN portion that is the subarea number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINB
&gt; Attribute Definition: PIN portion that is the block number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINP
&gt; Attribute Definition: PIN portion that is the parcel number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PINUNIT
&gt; Attribute Definition: Last 4 digits of PIN14; usually refers to
&gt; the unit number of the condo or leasehold.
&gt; Attribute Definition Source: Tax map
&gt;
&gt; BASE_PIN
&gt; Attribute Definition: The 10-digit number part of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PARCEL_ID
&gt; Attribute Definition: The 10-digit number part of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; REF_PIN
&gt; Attribute Definition: Reference PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PARCEL_ADDRESS
&gt; Attribute Definition: Street address of parcel
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; PARCEL_CITY
&gt; Attribute Definition: City in which parcel is located
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; PARCEL_STATE
&gt; Attribute Definition: State in which parcel is located
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; PARCEL_ZIP
&gt; Attribute Definition: ZIP code of parcel address
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; NEIGHBIRHOOD
&gt; Attribute Definition: Neighborhood code to generate neighborhood
&gt; administrative areas
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; HOUSE_NO
&gt; Attribute Definition: House number
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; STREET_DIRECTION
&gt; Attribute Definition: Street direction prefix
&gt; Attribute Definition Source: Assessor's Master File
&gt; Attribute Domain Values and Definitions:
&gt; E = East
&gt; N = North
&gt; NE = Northeast
&gt; NW = Northwest
&gt; S = South
&gt; SE = Southeast
&gt; SW = Southwest
&gt; W = West
&gt;
&gt; STEET_SUFFIX
&gt; Attribute Definition: Street suffix
&gt; Attribute Definition Source: Assessor's Master File
&gt; Attribute Domain Values and Definitions:
&gt;
&gt; APT_NO
&gt; Attribute Definition: Apartment number
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; CITY_NAME
&gt; Attribute Definition: City name
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; STATE
&gt; Attribute Definition: State
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ZIP
&gt; Attribute Definition: ZIP code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; OWNER_NAME
&gt; Attribute Definition: Pacel owner name
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; OWNER_ADDRESS
&gt; Attribute Definition: Owner's address
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; OWNER_CITY
&gt; Attribute Definition: Owner's city
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; OWNER_STATE
&gt; Attribute Definition: Owner's state
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; OWNER_ZIP
&gt; Attribute Definition: Owner's ZIP code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; PERCENT_OWNERSHIP
&gt; Attribute Definition: Percent ownership of the parcel
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; VOLUME
&gt; Attribute Definition: Internal code used by the Clerk for Tax
&gt; Redemption purposes
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; TAXCODE
&gt; Attribute Definition: Internal code represting a unique combination
&gt; of tax agencies
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_STATUS
&gt; Attribute Definition: Internal code representing the tax assessment
&gt; status of a parcel
&gt; Attribute Definition Source: Assessor's Master File
&gt; 0 = Assessable
&gt; 1 = Exempt
&gt; 2 = Railroad
&gt;
&gt; EXEMPTION_CODE
&gt; Attribute Definition: Exemption (non-taxed) code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; EXEMPT_AGENCY_NAME
&gt; Attribute Definition: Exemption agency name
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; STATUS
&gt; Attribute Definition: Parcel maintenence status
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt; COMMENT_
&gt; Attribute Definition: Notes related to parcel maintenence
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt; ASSESSMENT_LAND_VALUE
&gt; Attribute Definition: Assessed value of the land
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_IMPROVEMENT_VALUE
&gt; Attribute Definition: Assessed value of improvements
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_TOTAL_VALUE
&gt; Attribute Definition: Sum of land and improvement values
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_AGE
&gt; Attribute Definition: Age of improvements
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_TYPERESIDENCE
&gt; Attribute Definition: Residential property code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_TYPEUSE
&gt; Attribute Definition: Property use code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_IMPROVEMENT_CLASS
&gt; Attribute Definition: Property improvement code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; ASSESSMENT_OVERALL_CLASS
&gt; Attribute Definition: Overall class code
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; JOB_NO
&gt; Attribute Definition: Internal value used to identify the Maintenence
&gt; Job that created or altered a parcel
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt;-------------------------------------------------------------------
&gt;
&gt; REFERENCE PIN TABLE (RefPIN)
&gt; Description: The object class RefPIN is used to manage the
&gt; relationships between base PINs in multi-PIN situations,
&gt; PINs, and lots. RefPIN contains zero or more records
&gt; for each PIN10 depending on the number of PIN10s
&gt; associated with a reference PIN. It also contains
&gt; records for every PIN/lot combination.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; REF_PIN Reference PIN 10 string
&gt; PIN10 The 10-digit number part of PIN 10 string
&gt; LOT Lot number 3 string
&gt; PAGE_SUBREF Page and subdivision ref letter 11 string
&gt; SUBBLK Subdivision block number 3 string
&gt;
&gt;
&gt; REF_PIN
&gt; Attribute Definition: The PIN used to Reference
&gt; elevated/condominium/leasehold parcels
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PIN10
&gt; Attribute Definition: The 10-digit number part of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; LOT
&gt; Attribute Definition: Lot number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; PAGE_SUBREF
&gt; Attribute Definition: Page and subdivision reference letter
&gt; Attribute Definition Source: Tax map
&gt;
&gt; SUBBLK
&gt; Attribute Definition: Subdivision block number
&gt; Attribute Definition Source: Tax map
&gt;
&gt;-----------------------------------------------------------------------
&gt;
&gt; CONDOMINIUM TABLE (PIN_Condominium)
&gt; Description: The object class PIN_Condominium contains name and
&gt; address information, the document number and document
&gt; recording date of the condominium, notes appearing in
&gt; the condominium description, and a flag indicating
&gt; that there are amendments to the condominium charter
&gt; contained in the PIN_Condominium table. A condominium
&gt; may have more than one address.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; PIN_10 10-digit unique ID for condo 10 string
&gt; CONDO_ID 10-digit unique ID for condo 10 string
&gt; NAME Condominium name 255 string
&gt; ADDRESS Condo address; may have multiple 255 string
&gt; DOC_NO Condo may have multiple doc no 10 string
&gt; REC_DATE Condo may have multiple rec date ?? date
&gt; NOTES Condo notes in map margin 255 notes
&gt; AMENDMENT Flag indicating condo amendment 1 string
&gt;
&gt; PIN_10
&gt; Attribute Definition: The 10-digit PIN number that uniquely identifies
&gt; a condominium
&gt; Attribute Definition Source: Tax map
&gt;
&gt; CONDO_ID
&gt; Attribute Definition: The 10-digit PIN number that uniquely identifies
&gt; a condominium
&gt; Attribute Definition Source: Tax map
&gt;
&gt; NAME
&gt; Attribute Definition: Condominium name
&gt; Attribute Definition Source: Tax map
&gt;
&gt; ADDRESS
&gt; Attribute Definition: Condominium address; a condominium may have more
&gt; than one address
&gt; Attribute Definition Source: Assessor's Master File
&gt;
&gt; DOC_NO
&gt; Attribute Definition: A condominium may have more than one document
&gt; number
&gt; Attribute Definition Source: Tax map
&gt;
&gt; REC_DATE
&gt; Attribute Definition: A condominium may have more than one recording
&gt; date
&gt; Attribute Definition Source: Tax map
&gt;
&gt; NOTES
&gt; Attribute Definition: Condominium notes in map margin
&gt; Attribute Definition Source: Tax map
&gt;
&gt; AMENDMENT
&gt; Attribute Definition: Flag indicating that there are amendments to the
&gt; condominium document
&gt; Attribute Definition Source: Tax map
&gt;
&gt;----------------------------------------------------------------------
&gt;
&gt; CONDOMINIUM MISCELLANEOUS TABLE (PIN_CondoMisc)
&gt; Description: The object class PIN_CondoMisc is designed to store
&gt; unit-specific information about condominiums where
&gt; tabular information on upper and lower elevations for
&gt; each floor or building is provided instead of elevation
&gt; floor plans. There may be multiple records per
&gt; condominium in this table.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; PIN_10 10-digit unique ID for condo 10 string
&gt; DESC Descriptive attribute 255 string
&gt; UPPER_ELEV Upper elevation 18 double
&gt; LOWER_ELEV Lower elevation 18 double
&gt;
&gt; PIN_10
&gt; Attribute Definition: The 10-digit PIN number that uniquely identifies
&gt; a condominium
&gt; Attribute Definition Source: Tax map
&gt;
&gt; DESC
&gt; Attribute Definition: Descriptive attribute for elevation tables
&gt; Attribute Definition Source: Tax map
&gt;
&gt; UPPER_ELEV
&gt; Attribute Definition: Upper elevation
&gt; Attribute Definition Source: Tax map
&gt;
&gt; LOWER_ELEV
&gt; Attribute Definition: Lower elevation
&gt; Attribute Definition Source: Tax map
&gt;
&gt;-----------------------------------------------------------------------
&gt;
&gt; TAX BLOCK POLYGONS (BLOCK)
&gt; Description: The feature class Block is a multipart polygon feature
&gt; class representing the boundaries of tax (parcel)
&gt; blocks. Block polygons are aggregations of parcels that
&gt; share the same block number as part of the PIN. Since
&gt; the blocks do not include any part of a right-of-way
&gt; polygon, block polygons may be discontinuous.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; BLOCK_ID Unique ID of a block 7 string
&gt; BLOCK_NUM Subset of BLOCK_ID for ArcIMS 3 integer
&gt; JOB_NO Internal value used to identify
&gt; Maintenence Job that created or
&gt; altered a block 9 integer
&gt;
&gt; BLOCK_ID
&gt; Attribute Definition: Unique identification of a block including the
&gt; area, subarea, and block number as represented
&gt; in characters one to seven of the PIN
&gt; Attribute Definition Source: Tax map
&gt;
&gt; BLOCK_NUM
&gt; Attribute Definition: Subset of BLOCK_ID to support labeling
&gt; in ArcIMS
&gt; Attribute Definition Source: Tax map
&gt;
&gt; JOB_NO
&gt; Attribute Definition: Internal value used to identify
&gt; Maintenence Job that created or
&gt; altered a block
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt;-----------------------------------------------------------------------
&gt;
&gt; LEASE POLYGONS (LEASE)
&gt; Description: The feature class Lease contains lease polygons, where
&gt; lease geometry is shown on the tax map. Lease geometry
&gt; is shown in a minimum of leasehold situations. Where
&gt; lease geometry is not shown on the tax map, lease
&gt; numbers associated with a parcel are stored in the
&gt; object class Lease.
&gt;
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; PIN 14-digit unique ID number 14 string
&gt; PINU Lease number 4 string
&gt; JOB_NO Internal value used to identify
&gt; Maintenence Job that created or
&gt; altered a leasehold 9 integer
&gt;
&gt; PIN
&gt; Attribute Definition: The 14-digit number that uniquely identifies
&gt; a parcel/lease
&gt; Attribute Definition Source: Tax map
&gt;
&gt; JOB_NO
&gt; Attribute Definition: Internal value used to identify
&gt; Maintenence Job that created or
&gt; altered a leasehold
&gt; Attribute Definition Source: Maintenence Application
&gt;
&gt;
</eadetcit>
</overview>
<detailed Name="CensusBlk2012_uninc">
<enttyp>
<enttypl Sync="TRUE">CensusBlk2012_uninc</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">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>
<subtype>
<stname Sync="TRUE">ElevatedLeasehold</stname>
<stcode Sync="TRUE">7</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">7</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">ElevatedCondo</stname>
<stcode Sync="TRUE">5</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">5</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">ElevatedParcel</stname>
<stcode Sync="TRUE">2</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">CondominiumParcel</stname>
<stcode Sync="TRUE">3</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">3</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">ROWOverlap</stname>
<stcode Sync="TRUE">8</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">8</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">BaseParcel</stname>
<stcode Sync="TRUE">1</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">1</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">Leasehold</stname>
<stcode Sync="TRUE">6</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">6</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">NoPIN</stname>
<stcode Sync="TRUE">4</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">4</stflddv>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">CondominiumLeasehold</stname>
<stcode Sync="TRUE">9</stcode>
<stfield>
<stfldnm Sync="TRUE">PINA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINA</domname>
<domdesc Sync="TRUE">Area number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINSA</stfldnm>
<stflddd>
<domname Sync="TRUE">PINSA</domname>
<domdesc Sync="TRUE">Subarea number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PINB</stfldnm>
<stflddd>
<domname Sync="TRUE">PINB</domname>
<domdesc Sync="TRUE">Block number</domdesc>
<domtype Sync="TRUE">Range</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Default value</splttype>
<domowner Sync="TRUE">GIS</domowner>
<domfldtp Sync="TRUE">SmallInteger</domfldtp>
</stflddd>
</stfield>
<stfield>
<stfldnm Sync="TRUE">JOB_NO</stfldnm>
<stflddv Sync="TRUE">0</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">PARCELTYPE</stfldnm>
<stflddv Sync="TRUE">1</stflddv>
</stfield>
</subtype>
<attr>
<attrlabl Sync="TRUE">NAME</attrlabl>
<attalias Sync="TRUE">Agency Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SUM_POP100</attrlabl>
<attalias Sync="TRUE">Total Population</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">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>
<detailed Name="gis.GIS.Parcel2ParcelNum">
<enttyp>
<enttypl Sync="TRUE">gis.GIS.Parcel2ParcelNum</enttypl>
<enttypt Sync="TRUE">Relationship</enttypt>
</enttyp>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Office of the Cook County Clerk</cntorg>
<cntper>Tanya Anthofer</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>
Cook County Clerk
Room 434 Map Dept
118 N. Clark St
</address>
<city>Chicago</city>
<state>Illinois</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-6229</cntvoice>
<cntfax>312-603-6717</cntfax>
<cntemail>TANTHOF@cookcountygov.com</cntemail>
<hours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</hours>
</cntinfo>
</distrib>
<resdesc>
Cadastre
Parcel
</resdesc>
<distliab>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.</distliab>
<custom>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.</custom>
<techpreq>User must be able to read either an ArcInfo coverage (in .e00 export format), an ArcView shapefile, or a personal geodatabase. Format compatibility is the user's responsibility.</techpreq>
<availabl>
<timeinfo>
<rngdates>
<begdate>20020201</begdate>
<enddate>20030201</enddate>
</rngdates>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd Sync="TRUE">20120208</metd>
<metrd>20020626</metrd>
<metfrd>20020630</metfrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Northeastern Illinois Planning Commission</cntorg>
<cntper>Linda Schwab</cntper>
</cntorgp>
<cntpos>Metadata Specialist/GIS Analyst</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>222 S. Riverside Plaza, Suite 1800</address>
<city>Chicago</city>
<state>Illinois</state>
<postal>60606</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312/454-0400</cntvoice>
<cntfax>312/454-0411</cntfax>
<cntemail>lschwab@nipc.org</cntemail>
<hours>09:00 - 17:00, Central Time Zone, Monday-Friday, except holidays</hours>
<cntinst>Please contact during normal business hours</cntinst>
</cntinfo>
</metc>
<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>
<metac>None</metac>
<metuc>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.</metuc>
<langmeta Sync="TRUE">en</langmeta>
</metainfo>
<Esri>
<CreaDate>20140109</CreaDate>
<CreaTime>10121400</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20220801</SyncDate>
<SyncTime>09525300</SyncTime>
<ModDate>20220801</ModDate>
<ModTime>09525300</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">CensusBlk2012_uninc</itemName>
<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/2.9.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>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
</Esri>
<dataIdInfo>
<envirDesc Sync="FALSE">Esri ArcGIS 12.9.0.32739</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="TRUE">CensusBlk2012_uninc</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">1003175.748</westBL>
<eastBL Sync="TRUE">1205633.622</eastBL>
<northBL Sync="TRUE">1998851.705</northBL>
<southBL Sync="TRUE">1749884.652</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-88.264274</westBL>
<eastBL Sync="TRUE">-87.516926</eastBL>
<northBL Sync="TRUE">42.154371</northBL>
<southBL Sync="TRUE">41.468316</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
</dataIdInfo>
<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>
<distributor>
<distorTran>
<onLineSrc>
<orDesc Sync="TRUE">002</orDesc>
<linkage Sync="FALSE">withheld</linkage>
</onLineSrc>
</distorTran>
<distorFormat>
<formatName Sync="FALSE">Feature Class</formatName>
</distorFormat>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3435">NAD_1983_StatePlane_Illinois_East_FIPS_1201_Feet</identCode>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">8.9.3(9.3.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="CensusBlk2012_uninc">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="TRUE">20220801</mdDateSt>
</metadata>
