<?xml version="1.0" encoding="UTF-8"?><metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Cook County Board of Commissioners</origin>
<pubdate>200206</pubdate>
<title Sync="FALSE">HydroLine</title>
<edition>1.0</edition>
<geoform Sync="TRUE">vector digital data</geoform>
<pubinfo>
<pubplace>Chicago, Illinois</pubplace>
<publish>Cook County Board of Commissioners</publish>
</pubinfo>
<ftname Sync="FALSE">HydroLine</ftname>
<onlink Sync="FALSE">withheld</onlink>
</citeinfo>
</citation>
<descript>
<abstract>
Hydrographic data was collected for all of Cook County. Significant flowing and standing water features that were visible on the aerial photography were stereocompiled from 1998 aerial photography. The hydrographic midline data set represents, as a single line, the interpreted midline of flowing water features as seen on the aerial photography.
The hydrographic midline data layer is used to show the location of the midline of natural drainage features, and is connected to polygonal (standing) hydrographic features such as lakes and ponds. The midline data layer also includes drainage features less than five feet in width, which were not included in the polygon hydrography data set.
Midlines were added to water bodies such as double-line rivers to maintain the linear connectivity of the hydrographic network. Where the course of linear features (such as streams and rivers) in the hydrographic midline layer could not be compiled photogrammetrically due to being obscured by other features (such as vegetation or shadows), the obscured line segment was coded as "interpreted". In some cases, a flowing water feature may have run through an underground drain or culvert or its course otherwise obscured from view on the aerial photography. For such cases, in order to maintain linear connectivity of the features, its path was also interpreted and coded as such. Some hydrographic data was provided by the City of Chicago and incorporated into this data layer. These hydrographic data layers are modeled and stored as a network coverage containing polygons and/or lines.
This midline data layer was created out of need by Cook County to develop a hydrographic layer in which water features are represented as single lines. The intended primary use of this data layer is for small-scale mapping and networking.
The hydrographic midline layer was intersected with the street midline and railroad data layers to create nodes in the coverage model. It was also intersected with the bridge polygon data layer. Where hydrographic midline segments fall within a bridge polygon, they have been given a grade separation code of zero (0) to indicate the water level is technically "at grade".
Hydrographic attributes include feature name, tax map name, and type. The primary source of the attribute information was the Cook County Highway Department database. Hydrographic names and alias IDs are linked to lookup tables based on the hydrographic name ID attribute.
</abstract>
<purpose>Hydrography is the depiction of water. This data set contains information about the location and name of flowing water features and some standing water features in Cook County. This linear data set represents interpreted midlines of water features, and was created to depict linear connectivity of hydrographic features. The purpose of creating this planimetric data set was to update existing hydrographic data sets and to integrate the new data with other newly created data sets based on a common geography (digital orthoimagery). The new planimetric data sets were also created to serve as a standard database for virtually all geospatial applications in Cook County, and are intended to support general location, planning, and cartography projects, as well as general inventory and asset management, Census analysis and mapping, and geocoding by address.</purpose>
<supplinf>
This planimetric 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 (objects). 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.
For information regarding available distribution formats, please contact the individual listed as the Contact_Person in the Distribution_Information section of this metadata document.
This data set is one in a series of seven planimetric data sets, including digital orthoimagery, building footprints, hydrology polygons, hydrology midlines, railroads, road edges, and street midlines, for Cook County, Illinois.
</supplinf>
<langdata Sync="TRUE">en</langdata>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>199804</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Continually</update>
</status>
<spdom>
<bounding>
<westbc Sync="TRUE">-88.275861</westbc>
<eastbc Sync="TRUE">-87.510009</eastbc>
<northbc Sync="TRUE">42.157533</northbc>
<southbc Sync="TRUE">41.467450</southbc>
</bounding>
<lboundng>
<leftbc Sync="TRUE">1000000.621500</leftbc>
<rightbc Sync="TRUE">1207498.289000</rightbc>
<bottombc Sync="TRUE">1749586.818000</bottombc>
<topbc Sync="TRUE">2000001.849000</topbc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>flowing water</themekey>
<themekey>river</themekey>
<themekey>tributaries</themekey>
<themekey>canal</themekey>
<themekey>channel</themekey>
<themekey>stream</themekey>
<themekey>gully</themekey>
<themekey>rill</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Cook County</placekey>
<placekey>Illinois</placekey>
<placekey>Chicago</placekey>
<placekey>northeastern Illinois</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 CCook County Department of Office Technology.
It is required that the 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 1998 Hydrography Midlines, Version 1.0, March 2002."
</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Cook County Bureau of Information Technology and Automation</cntorg>
<cntper>Alan Hobscheid</cntper>
</cntorgp>
<cntpos>GIS Coordinator, Cook County Department of Office Technology</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>69 W. Washington Street</address>
<address>room 2700</address>
<city>Chicago</city>
<state>Illinois</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-1399</cntvoice>
<cntfax>312-603-9904</cntfax>
<cntemail>ahobscheid@cookcountygov.com</cntemail>
<hours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</hours>
<cntinst>Please contact during normal business hours.</cntinst>
</cntinfo>
</ptcontac>
<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. The software provided verification of topology and existence of label points in a coverage format.
As planimetric features were stereocompiled from aerial imagery and completed, they were checked against those images adjacent to them to ensure correct edgematching, completeness, and correct coding of lines that crossed onto adjoining images.
</logic>
<complete>This planimetric feature data set includes all features observable as of 17 April 1998. Completeness is judged to be excellent, based on repeated examination and usage.</complete>
<posacc>
<horizpa>
<horizpar>
This data set meets National Map Accuracy Standards for 1"=100' data products, and has an absolute positional accuracy of +/- 2.5 feet (+/- 0.7625 meters).
This data set was checked for positional accuracy against the 1998 Cook County 1:1200-scale digital orthophotos. 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 Aerial Photography, February 2002</title>
<edition>1.0</edition>
<geoform>remote-sensing image</geoform>
<pubinfo>
<pubplace>Chicago, Illinois</pubplace>
<publish>Cook County Board of Commissioners</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>1200</srcscale>
<typesrc>stable-base material</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>Cook County 1998 1:1200-scale Black and White Aerial Photography (1998_Aerial_Photos)</srccitea>
<srccontr>Provided base for planimetric stereocompilation of data set.</srccontr>
</srcinfo>
<procstep>
<procdesc>1.0 Perform Model Orientation: Merrick &amp; Company (Merrick) was contracted for photogrammetric compilation of planimetric data. Merrick performed internal relative and absolute positioning of each aerial photograph (1998_Aerial_Photos) using a least-squares analysis. The photogrammetric supervisor inspected all residuals to ensure that they conform to accuracy standards for 1" = 100' mapping.</procdesc>
<srcused>withheld</srcused>
<procdate>1998-1999</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>2.0 Photogrammetrically Collect Planimetric Data: Planimetry for all of the feature-type coverages was digitized concurrently. Merrick utilized CADMAP photogrammetric software for real-time planimetric data acquisition and coding from the Oriented_1998_Aerial_Photos. To populate attributes, each planimetric entity was collected by entering a unique identification number, thus enabling a CADMAP Collection Macro. The macro specified graphic collection parameters (i.e., building squaring, polygon closure, and 2-D or 3-D coordinates). Each model was edgematched during stereo-digitizing to form a continuous database.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2000</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>3.0 Data Merge and Quality Control: Merrick merged the All_Planimetric_Data into a specified delivery area. Then, the Quality Control/Edit team performed a quality inspection of the data to ensure feature completeness and attribute conformity.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2000</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>4.0 Digitize Midlines: The Merrick QC/edit team performed heads-up interpolation and digitization of the road and hydrography midlines from All_Planimetric_Data. This work involved a process of automated and manual procedures at edit workstations.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>
5.0 Coding Obscured Midlines: In previous process steps, technicians who created the planimetric data sets observed areas on the Oriented_1998_Aerial_Photos that were obscured from clear view by shadows, vegetation, bridges, etc. The obscured features could not be accurately identified and thus an Obscured_Polygon was drawn around that area.
The road and hydrography midline interpolations were overlaid with Obscured_Polygons. Where the midlines and Obscured_Polygons intersected, the resulting midline segment was coded as "interpreted".
</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>6.0 Conversion to ArcInfo: Merrick converted the QC_Planimetric_Data from a *.dgn format into separate ArcInfo coverages for each feature type by using ARCIGDS software tools to create separate planimetric coverages (Feature_Planimetric_Data). Each of the Feature_Planimetric_Data was verified for completeness before moving on to the next process step.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>7.0 Internal Quality Inspection/Quality Control: A series of manual and automatic quality control procedures were performed on each of the Feature_Planimetric_Data both throughout their creation and prior to their final approval. Each feature type was inspected for the following items: edgematching of homogenous features that span tiles; undershoots and overshoots; cartographic quality; line smoothness and zero-length line segments; linear connectivity; closure of polygonal features; node and vertex quality; verification of consistent label and line attributes; inspection of building squaring; cartographic placement; and graphic comparison of data to the source documents. The automatic quality control checks included: automated inventory and validation of all coverages; automated plot generation; validation of State Plane Coordinate System zone and double-precision coordinates; interactive inspection of data, maps, and production reports; conformance to file naming convention; validation of line attributes (where applicable); validation of network topology of linear features (where applicable); and validation of correct annotation characteristics.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-2001</procdate>
<srcprod>withheld</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Merrick &amp; Company</cntorg>
<cntper>Brian R. Raber</cntper>
</cntorgp>
<cntpos>Vice President and Project Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>2450 S. Peoria St.</address>
<city>Aurora</city>
<state>Colorado</state>
<postal>80014</postal>
<country>USA</country>
</cntaddr>
<cntvoice>303/751-0741</cntvoice>
<cntfax>303/751-2581</cntfax>
<cntemail>brian.raber@merrick.com</cntemail>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>8.0 Independent Quality Control: ESRI performed an independent quality review of the planimetric data coverages, including automated checks with QCView, and on-screen review of data using 1998_Digital_Orthophotos as background, etc.</procdesc>
<srcused>withheld</srcused>
<procdate>1999-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>9.0 Convert to ArcGIS 8.2 Geodatabase: ESRI developed a coverage-to-geodatabase conversion module and converted the completed planimetric data (Independent_QC_Planimetric_Coverages) from ArcInfo coverage format to ArcGIS geodatabase format. ESRI 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</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 Sync="TRUE">Metadata imported.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<date Sync="TRUE">20090316</date>
<time Sync="TRUE">09455800</time>
</procstep>
<procstep>
<procdesc Sync="TRUE">Dataset copied.</procdesc>
<srcused Sync="FALSE">withheld</srcused>
<procdate Sync="TRUE">20100906</procdate>
<proctime Sync="TRUE">23431000</proctime>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<indspref>rivers, streams, canals, channels, Cook County Illinois</indspref>
<direct Sync="TRUE">Vector</direct>
<ptvctinf>
<esriterm Name="HydroLine">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">23888</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 coverage contains hydrographic midlines (for flowing features) collected from 1998 aerial photography and nodes created by intersection with street midlines and railroad lines in the coverage model. This data set is used to show (as a single line) the location of the midline of natural drainage features. This layer also includes the single line representations for polygonal (standing) hydrographic features such as lakes and ponds.</eaover>
<eadetcit>
&gt;
&gt; Description: Hydrography Midlines
&gt;
&gt; Data Dictionary: Cook County, Illinois 1:1200-Scale 1998 Hydrography
&gt; Midlines, Version 1.0, March 2002
&gt;
&gt; Source: Aerial photography and Cook County Highway Department (CCHD)
&gt; Format: Data stored in ESRI ArcGIS version 8.x
&gt; Feature Types Maintained: Lines, attribute tables, look-up tables
&gt;
&gt;--------------------------------------------------------------------
&gt;--------------------------------------------------------------------
&gt;
&gt; HYDRO_LINE
&gt;
&gt; Coverages: Arcs and nodes (HYDRO_LINE.AAT, HYDRO_LINE.NAT)
&gt; Geodatabase: Lines (HydroLine)
&gt;
&gt; Description: This coverage contains hydrographic midlines (for
&gt; flowing features) collected from 1998 aerial photography and nodes
&gt; created by intersection with street midlines and railroad lines.
&gt; This data set is used to show (as a single line) the location of
&gt; the midline of natural drainage features. This layer also includes
&gt; the single line representations for polygonal (standing) hydrographic
&gt; features such as lakes and ponds.
&gt;
&gt; HYDRO_LINE.AAT
&gt; Description: Linear hydrographic feature midlines.
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; FID Internal feature number -- - --
&gt; SHAPE Feature geometry -- - --
&gt; FNODE# From node 5 bin
&gt; TNODE# To node 5 bin
&gt; LPOLY# Left polygon 5 bin
&gt; RPOLY# Right polygon 5 bin
&gt; LENGTH# Arc length 18 5 float
&gt; HYDRO_LINE# Arc internal number 5 bin
&gt; HYDRO_LINE-ID Arc User-ID 5 bin
&gt; NAME_ID ID linking to HYDRO_NAMES table 7 int
&gt; TAXMAP_ID ID linking to HYDRO_NAMES table 7 int
&gt; TYPE Hydrographic type 2 int
&gt; VIS Visible (plotted or not plotted) 1 int
&gt; INTRP Interpreted features 1 int
&gt; ANNO_NAME Name of linear hydro feature 40 char
&gt; ALIAS_NAME Linear hydro feature alias name 80 char
&gt;
&gt; HydroLine
&gt; Description: Linear hydrographic feature midlines.
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; UID Unique segment identifier 7 int
&gt; NAME_ID ID linking to HYDRO_NAMES table 7 int
&gt; TAXMAP_ID ID linking to HYDRO_NAMES table 7 int
&gt; TYPE Hydrographic type 2 int
&gt; VIS Visible (plotted or not plotted) 1 int
&gt; INTRP Interpreted features 1 int
&gt; ANNO_NAME Name of linear hydro feature 40 string
&gt; ALIAS_NAME Linear hydro feature alias name 80 string
&gt;
&gt;
&gt; TYPE
&gt; Attribute Definition: Hydrographic type
&gt; Attribute Definition Source: Aerial photography
&gt; Attribute Domain Values and Definitions:
&gt; "1" Single line representation of minor flow feature including
&gt; streams, rills, gullies, irrigation canals, intermittent
&gt; streams, etc. with a width of less that five percent of the
&gt; map scale (less than five feet). The features are collected
&gt; in a downstream direction.
&gt; "2" Midline representation of flowing features greater than or
&gt; equal to five percent of the map scale (at least five feet
&gt; wide). The features are collected in a downstream direction.
&gt;
&gt; VIS
&gt; Attribute Definition: Cartographic display item for use in mapping
&gt; to describe if a feature is visible or not.
&gt; For internal use only.
&gt; Attribute Definition Source: Postprocess done by County
&gt; Attribute Domain Values and Definitions:
&gt; "0" Plotted
&gt; "1" Not plotted
&gt;
&gt; INTRP
&gt; Attribute Definition: Indicates if midline was interpreted. If the
&gt; water feature was partially obscured by
&gt; vegetation, shadows, or some other obstruction
&gt; when viewed on the aerial photography, an
&gt; "obscured view" polygon was drawn. When the
&gt; midlines of water features were compiled, the
&gt; interpreted midline line set was overlain with
&gt; the "obscured polygon" data set and line segments
&gt; where the two intersected were coded to indicate
&gt; that the midline location was interpreted. In
&gt; some instances where the linear hydrographic
&gt; feature is hidden (i.e., by a drain, culvert,
&gt; etc), and there was a need to maintain linear
&gt; connectivity of the hydrographic flow, the hidden
&gt; segment was coded as interpreted as well.
&gt;
&gt; Attribute Definition Source: Aerial photography, Obscured Polygon data
&gt; Attribute Domain Values and Definitions:
&gt; "0" Not interpreted
&gt; "1" Interpreted
&gt;
&gt; ANNO_NAME
&gt; Attribute Definition: Name of linear hydrographic feature for
&gt; annotating purposes
&gt; Attribute Definition Source: Cook County Highway Department (CCHD)
&gt;
&gt; ALIAS_ANNO
&gt; Attribute Definition: Alias name of linear hydrographic feature
&gt; for annotating purposes
&gt; Attribute Definition Source: Cook County Highway Department (CCHD)
&gt;
&gt;
&gt;----------------------------------------------------------------------
&gt;
&gt; HYDRO_LINE.NAT
&gt; Description: Hydrographic nodes created when intersecting with street
&gt; midlines and railroad lines
&gt; Attribute Label Attribute Definition Attribute Format
&gt; wdth dec type
&gt; FID Internal feature number -- - --
&gt; SHAPE Feature geometry -- - --
&gt; ARC# Internal sequence number 5 bin
&gt; HYDRO_LINE# Arc internal numer 5 bin
&gt; HYDRO_LINE-ID Arc User-ID 5 bin
&gt; NODETYPE Type of node intersection 1 int
&gt;
&gt; NODETYPE
&gt; Attribute Definition: Types of node intersection
&gt; Attribute Definition Source: User
&gt; Attribute Domain Values and Definitions:
&gt; "1" Hydro arc intersection
&gt; "2" Railroad arc intersection
&gt; "3" Road arc intersection
&gt; "4" Tile edge node **will be obsolete in final database**
&gt;
</eadetcit>
</overview>
<detailed Name="HydroLine">
<enttyp>
<enttypl Sync="FALSE">HydroLine</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">23888</enttypc>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">NAME_ID</attrlabl>
<attalias Sync="TRUE">NAME_ID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">UNIQID</attrlabl>
<attalias Sync="TRUE">UNIQID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ANNO_NAME</attrlabl>
<attalias Sync="TRUE">ANNO_NAME</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">40</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">ALIAS_NAME</attrlabl>
<attalias Sync="TRUE">ALIAS_NAME</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">80</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">TAXMAP_ID</attrlabl>
<attalias Sync="TRUE">TAXMAP_ID</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">INTRP</attrlabl>
<attalias Sync="TRUE">INTRP</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">TYPE</attrlabl>
<attalias Sync="TRUE">TYPE</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">VIS</attrlabl>
<attalias Sync="TRUE">VIS</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE</attrlabl>
<attalias Sync="TRUE">SHAPE</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</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">SingleLineMinorFlow</stname>
<stcode Sync="TRUE">1</stcode>
<stfield>
<stfldnm Sync="TRUE">INTRP</stfldnm>
<stflddd>
<domname Sync="TRUE">Interpreted</domname>
<domdesc Sync="TRUE">Interpreted type code</domdesc>
<domtype Sync="TRUE">Coded Value</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">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">VIS</stfldnm>
<stflddd>
<domname Sync="TRUE">Visible</domname>
<domdesc Sync="TRUE">Plotting code</domdesc>
<domtype Sync="TRUE">Coded Value</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">OrthoYear</stfldnm>
<stflddd>
<domname Sync="TRUE">OrthYear</domname>
<domdesc Sync="TRUE">Year of Orthoimagery used to edit feature</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domowner Sync="TRUE">SDE</domowner>
<domfldtp Sync="TRUE">String</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">DualLineMidline</stname>
<stcode Sync="TRUE">2</stcode>
<stfield>
<stfldnm Sync="TRUE">INTRP</stfldnm>
<stflddd>
<domname Sync="TRUE">Interpreted</domname>
<domdesc Sync="TRUE">Interpreted type code</domdesc>
<domtype Sync="TRUE">Coded Value</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">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">VIS</stfldnm>
<stflddd>
<domname Sync="TRUE">Visible</domname>
<domdesc Sync="TRUE">Plotting code</domdesc>
<domtype Sync="TRUE">Coded Value</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">OrthoYear</stfldnm>
<stflddd>
<domname Sync="TRUE">OrthYear</domname>
<domdesc Sync="TRUE">Year of Orthoimagery used to edit feature</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domowner Sync="TRUE">SDE</domowner>
<domfldtp Sync="TRUE">String</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">Atlas</stname>
<stcode Sync="TRUE">4</stcode>
<stfield>
<stfldnm Sync="TRUE">INTRP</stfldnm>
<stflddd>
<domname Sync="TRUE">Interpreted</domname>
<domdesc Sync="TRUE">Interpreted type code</domdesc>
<domtype Sync="TRUE">Coded Value</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">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">VIS</stfldnm>
<stflddd>
<domname Sync="TRUE">Visible</domname>
<domdesc Sync="TRUE">Plotting code</domdesc>
<domtype Sync="TRUE">Coded Value</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">OrthoYear</stfldnm>
<stflddd>
<domname Sync="TRUE">OrthYear</domname>
<domdesc Sync="TRUE">Year of Orthoimagery used to edit feature</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domowner Sync="TRUE">SDE</domowner>
<domfldtp Sync="TRUE">String</domfldtp>
</stflddd>
</stfield>
</subtype>
<subtype>
<stname Sync="TRUE">Outside County</stname>
<stcode Sync="TRUE">3</stcode>
<stfield>
<stfldnm Sync="TRUE">INTRP</stfldnm>
<stflddd>
<domname Sync="TRUE">Interpreted</domname>
<domdesc Sync="TRUE">Interpreted type code</domdesc>
<domtype Sync="TRUE">Coded Value</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">TYPE</stfldnm>
<stflddv Sync="TRUE">2</stflddv>
</stfield>
<stfield>
<stfldnm Sync="TRUE">VIS</stfldnm>
<stflddd>
<domname Sync="TRUE">Visible</domname>
<domdesc Sync="TRUE">Plotting code</domdesc>
<domtype Sync="TRUE">Coded Value</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">OrthoYear</stfldnm>
<stflddd>
<domname Sync="TRUE">OrthYear</domname>
<domdesc Sync="TRUE">Year of Orthoimagery used to edit feature</domdesc>
<domtype Sync="TRUE">Coded Value</domtype>
<mrgtype Sync="TRUE">Default value</mrgtype>
<splttype Sync="TRUE">Duplicate</splttype>
<domowner Sync="TRUE">SDE</domowner>
<domfldtp Sync="TRUE">String</domfldtp>
</stflddd>
</stfield>
</subtype>
<attr>
<attrlabl Sync="TRUE">OrthoYear</attrlabl>
<attalias Sync="TRUE">OrthoYear</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">GlobalID</attrlabl>
<attalias Sync="TRUE">GlobalID</attalias>
<attrtype Sync="TRUE">GlobalID</attrtype>
<attwidth Sync="TRUE">38</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">created_user</attrlabl>
<attalias Sync="TRUE">created_user</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">created_date</attrlabl>
<attalias Sync="TRUE">created_date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">last_edited_user</attrlabl>
<attalias Sync="TRUE">last_edited_user</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">last_edited_date</attrlabl>
<attalias Sync="TRUE">last_edited_date</attalias>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE.len</attrlabl>
<attalias Sync="TRUE">SHAPE.len</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
<detailed Name="HydroLine2HydroLineAlias">
<enttyp>
<enttypl Sync="FALSE">HydroLine2HydroLineAlias</enttypl>
<enttypt Sync="TRUE">Relationship</enttypt>
</enttyp>
</detailed>
<detailed Name="HydroName2HydroLine">
<enttyp>
<enttypl Sync="FALSE">HydroName2HydroLine</enttypl>
<enttypt Sync="TRUE">Relationship</enttypt>
</enttyp>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Cook County Bureau of Information Technology and Automation</cntorg>
<cntper>Alan Hobscheid</cntper>
</cntorgp>
<cntpos>GIS Coordinator, Cook County Department of Office Technology</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>69 W. Washington Street</address>
<address>room 2700</address>
<city>Chicago</city>
<state>Illinois</state>
<postal>60602</postal>
<country>USA</country>
</cntaddr>
<cntvoice>312-603-1399</cntvoice>
<cntfax>312-603-9904</cntfax>
<cntemail>ahobscheid@cookcountygov.com</cntemail>
<hours>09:00 - 17:00, Central Time Zone, Monday - Friday, except holidays</hours>
<cntinst>Please contact during normal business hours.</cntinst>
</cntinfo>
</distrib>
<resdesc>Hydrography Midlines</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>20020228</begdate>
<enddate>Present</enddate>
</rngdates>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd Sync="TRUE">20120208</metd>
<metrd>20020625</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>20201124</CreaDate>
<CreaTime>15341500</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20180417</SyncDate>
<SyncTime>13355200</SyncTime>
<ModDate>20180417</ModDate>
<ModTime>13355200</ModTime>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">HydroLine</itemName>
<imsContentType Sync="TRUE">002</imsContentType>
<nativeExtBox>
<westBL Sync="TRUE">1000000.621500</westBL>
<eastBL Sync="TRUE">1207498.289000</eastBL>
<southBL Sync="TRUE">1749586.818000</southBL>
<northBL Sync="TRUE">2000001.849000</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<relatedItems>
<item>
<itemName/>
</item>
<item>
<itemName/>
</item>
</relatedItems>
</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/10.4'&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;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.002&lt;/XYTolerance&gt;&lt;ZTolerance&gt;2&lt;/ZTolerance&gt;&lt;MTolerance&gt;2&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>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<dataIdInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.4.1.5686</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">HydroLine</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="native">
<westBL Sync="TRUE">1000000.6215</westBL>
<eastBL Sync="TRUE">1207498.289</eastBL>
<northBL Sync="TRUE">2000001.849</northBL>
<southBL Sync="TRUE">1749586.818</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<geoBox esriExtentType="decdegrees">
<westBL Sync="TRUE">-88.275861</westBL>
<eastBL Sync="TRUE">-87.510009</eastBL>
<northBL Sync="TRUE">42.157533</northBL>
<southBL Sync="TRUE">41.46745</southBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</geoBox>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-88.275861</westBL>
<eastBL Sync="TRUE">-87.510009</eastBL>
<northBL Sync="TRUE">42.157533</northBL>
<southBL Sync="TRUE">41.467450</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
</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="FALSE">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">6.12(9.3.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="HydroLine">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">23888</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<mdDateSt Sync="TRUE">20180417</mdDateSt>
</metadata>
