<?xml version="1.0"?>
<MIF profile_type="vector">
<!-- Identification Information -->	
<!-- Citation -->
<Originator section="citation" gid1="1">U.S. Department of Commerce, U.S. Census Bureau,Geography Division</Originator>
<Publication_Date section="citation">2005</Publication_Date>
<Title section="citation">TIGER/Line Files, 2004 Second Edition, North Carolina, Iredell County</Title>
<Edition section="citation">2004 Second Edition</Edition>
<Geospatial_Data_Presentation_Form section="citation">vector digital data</Geospatial_Data_Presentation_Form>

<!-- Series Information -->
<Series_Name section="citation">TIGER/Line Files</Series_Name>
<Issue_Identification section="citation">Each file contains a version code that uniquely identifies each specific 
release of a version of the TIGER/Line files.  The version code (MMYY) represents the month and year that the data in 
the file was extracted from the TIGER database.</Issue_Identification>
<Other_Citation_Details section="citation">This is a test, just a test </Other_Citation_Details>
<!-- Suggested addition to the GPMS. -->
<Online_Linkage section="citation" gid1="1">http://www.census.gov/geo/www/tiger</Online_Linkage>

<!-- Description -->
<Abstract>The 2004 Second Edition TIGER/Line files are an extract of selected geographic and cartographic information from the Census 
TIGER database.  The geographic coverage for a single TIGER/Line file is a county or statistical equivalent entity, with the coverage 
area based on the latest available governmental unit boundaries.  The Census TIGER database represents a seamless national file with no 
overlaps or gaps between parts.  However, each county-based TIGER/Line file is designed to stand alone as an independent data set or the 
files can be combined to cover the whole Nation.  The 2004 Second Edition TIGER/Line files consist of line segments representing physical features and governmental and 
statistical boundaries.  The files contain information distributed over a series of record types for the spatial objects of a county.  There are 19 record types, including
 the basic data record, the shape coordinate points, and geographic codes that can be used with appropriate software to prepare maps.  Other geographic information 
 contained in the files includes attributes such as feature identifiers/census feature class codes (CFCC) used to differentiate feature types, address ranges and ZIP Codes
 ,codes for legal and statistical entities, latitude/longitude coordinates of linear and point features, landmark point features, area landmarks, and area boundaries.
 </Abstract>
<Purpose>In order for others to use the information in the Census TIGER database in a geographic information system (GIS) or for other 
geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line files.</Purpose>
<Subject_Entity>North Carolina, Iredell County</Subject_Entity>
<Survey_Instance_Name> Test </Survey_Instance_Name>
<Survey_Name> Test </Survey_Name>
<Supplemental_Information>The TIGER/Line data are not in a mapping projection even though most of the features were scanned directly from
 source maps that were in a projection.  To find out more about TIGER/Line files and other Census TIGER database derived data sets visit 
 http://www.census.gov/geo/www/tiger.</Supplemental_Information>

<!-- Time Period of Content -->
<Beginning_Date section="time period of content">200501</Beginning_Date>
<Ending_Date section="time period of content">200502</Ending_Date>
<Currentness_Reference>2004</Currentness_Reference>
<!-- Status -->
<Progress>Complete</Progress>
<Maintenance_and_Update_Frequency>TIGER/Line files are extracted from the Census TIGER database twice a year or when needed for 
geographic programs required to support the census and survey programs of the U.S. Census Bureau.  No changes or updates will be made to 
the 2004 Second Edition TIGER/Line files.  Future releases of TIGER/Line files will reflect updates made to the Census TIGER database and
 will be released under a version numbering system based on the month and year the data is extracted</Maintenance_and_Update_Frequency>

<!-- Spatial Domain -->
<West_Bounding_Coordinate>-81.112888</West_Bounding_Coordinate>
<East_Bounding_Coordinate>-80.692698</East_Bounding_Coordinate>
<North_Bounding_Coordinate>36.057878</North_Bounding_Coordinate>
<South_Bounding_Coordinate>35.487699</South_Bounding_Coordinate>

<!-- Data Set G-Polygon -->
<Outer_G-Ring gid1="1">30.2,-88.5,35.0,-88.3,35.0,-84.8,31,-84.8,30.2,-88.5</Outer_G-Ring>
<Exclusion_G-Ring gid1="1"> 38.703651, -75.1912, 38.216366 </Exclusion_G-Ring>

<!-- Keywords (ANSI and FW will be added automatically) -->
<Theme_Keyword_Thesaurus gid1="1">FGDC Framework Themes</Theme_Keyword_Thesaurus>
<Theme_Keyword gid1="1">FWGOVERNMENTALUNITS</Theme_Keyword>
<Theme_Keyword gid1="1">FWTRANSPORTATION</Theme_Keyword>
<Theme_Keyword gid1="1">FWROADS</Theme_Keyword>
<Theme_Keyword_Thesaurus gid1="2">ISO 19115 Topic Categories</Theme_Keyword_Thesaurus>
<Theme_Keyword gid1="2">Boundaries</Theme_Keyword>
<Theme_Keyword_Thesaurus gid1="3">None</Theme_Keyword_Thesaurus>
<Theme_Keyword gid1="3">Linear Feature</Theme_Keyword>
<Theme_Keyword gid1="3">Feature Identifier</Theme_Keyword>
<Theme_Keyword gid1="3">Census Feature Class Code (CFCC)</Theme_Keyword>
<Theme_Keyword gid1="3">Address Range</Theme_Keyword>
<Theme_Keyword gid1="3">Geographic Entity</Theme_Keyword>
<Theme_Keyword gid1="3">Point Node</Theme_Keyword>
<Theme_Keyword gid1="3">Landmark Feature</Theme_Keyword>
<Theme_Keyword gid1="3">Legal Boundary</Theme_Keyword>
<Theme_Keyword gid1="3">Statistical Boundary</Theme_Keyword>
<Theme_Keyword gid1="3">Legal Entity</Theme_Keyword>
<Theme_Keyword gid1="3">Statistical Entity</Theme_Keyword>
<Theme_Keyword gid1="3">Polygon</Theme_Keyword>
<Theme_Keyword gid1="3">State or Equivalent Entity</Theme_Keyword>
<Theme_Keyword gid1="3">County or Equivalent Entity</Theme_Keyword>
<Theme_Keyword gid1="3">TIGER/Line</Theme_Keyword>
<Theme_Keyword gid1="3">Topology</Theme_Keyword>
<Theme_Keyword gid1="3">Street Centerline</Theme_Keyword>
<Theme_Keyword gid1="3">Latitude/Longitude</Theme_Keyword>
<Theme_Keyword gid1="3">ZCTA</Theme_Keyword>
<Theme_Keyword gid1="3">Zip Code Tabulation Area</Theme_Keyword>
<Theme_Keyword gid1="3">Urban Area</Theme_Keyword>
<Theme_Keyword gid1="3">Urbanized Area</Theme_Keyword>
<Theme_Keyword gid1="3">Urban Cluster</Theme_Keyword>
<Theme_Keyword gid1="3">Congressional District</Theme_Keyword>
<Theme_Keyword gid1="3">Combined Statistical Area</Theme_Keyword>
<Theme_Keyword gid1="3">Micropolitan Statistical Area</Theme_Keyword>
<Theme_Keyword gid1="3">Metropolitan Statistical Area</Theme_Keyword>
<Theme_Keyword gid1="3">Metropolitan Division</Theme_Keyword>
<Theme_Keyword gid1="3">New England City and Town Area</Theme_Keyword>
<Theme_Keyword gid1="3">Combined New England City and Town Area</Theme_Keyword>
<Theme_Keyword gid1="3">New England City and Town Area Division</Theme_Keyword>
<Theme_Keyword gid1="3">Metropolitan District</Theme_Keyword>
<Theme_Keyword gid1="3">Core Based Statistical Area</Theme_Keyword>
<Theme_Keyword gid1="3">Metropolitan Area</Theme_Keyword>
<Theme_Keyword gid1="3">Vector</Theme_Keyword>
<Theme_Keyword gid1="3">TIGER/Line Identification Number(TLID)</Theme_Keyword>
<Theme_Keyword gid1="3">TIGER Zero-Cell ID (TZID)</Theme_Keyword>
<Theme_Keyword gid1="3">Street Segment</Theme_Keyword>
<Theme_Keyword gid1="3">Coordinate</Theme_Keyword>
<Theme_Keyword gid1="3">Geographic Code</Theme_Keyword>
<Theme_Keyword gid1="3">Internal Point</Theme_Keyword>
<Theme_Keyword gid1="3">County Subdivision</Theme_Keyword>
<Theme_Keyword gid1="3">Sub-Minor Civil Division</Theme_Keyword>
<Theme_Keyword gid1="3">Place</Theme_Keyword>
<Theme_Keyword gid1="3">American Indian Area</Theme_Keyword>
<Theme_Keyword gid1="3">Alaska Native Area</Theme_Keyword>
<Theme_Keyword gid1="3">Hawaiian Home Land</Theme_Keyword>
<Theme_Keyword gid1="3">Census Tract</Theme_Keyword>
<Theme_Keyword gid1="3">Block Group</Theme_Keyword>
<Theme_Keyword gid1="3">Census Block</Theme_Keyword>
<Theme_Keyword gid1="3">State Legislative District</Theme_Keyword>
<Theme_Keyword gid1="3">Voting District</Theme_Keyword>
<Theme_Keyword gid1="3">Public Use Microdata Area (PUMA)</Theme_Keyword>
<Theme_Keyword gid1="3">School District</Theme_Keyword>
<Theme_Keyword gid1="3">Boundary</Theme_Keyword>

<Theme_Keyword_Thesaurus gid1="4">Two Themes</Theme_Keyword_Thesaurus>
<Theme_Keyword gid1="4">Two</Theme_Keyword>
<Theme_Keyword gid1="4">three</Theme_Keyword>
<Theme_Keyword gid1="4">four</Theme_Keyword>

<!-- Place-->
<Place_Keyword_Thesaurus gid1="1">FIPS Publication 5-2, FIPS Publication 6-4,FIPS Publication 8-6, FIPS Publication 9-1, FIPS Publication
 55-3</Place_Keyword_Thesaurus>
<Place_Keyword gid1="1">United States</Place_Keyword>
<Place_Keyword gid1="1">State or Equivalent Entity</Place_Keyword>
<Place_Keyword gid1="1">Ohio</Place_Keyword>
<Place_Keyword gid1="1">OH</Place_Keyword>
<Place_Keyword gid1="1">County or Equivalent Entity</Place_Keyword>
<Place_Keyword gid1="1">Wayne</Place_Keyword>
<Place_Keyword gid1="1">County</Place_Keyword>
<Place_Keyword gid1="1">39169</Place_Keyword>
<Access_Constraints>None</Access_Constraints>
<Use_Constraints>Acknowledgment of the U.S. Census Bureau would be appreciated for products derived from these files.  TIGER, TIGER/Line, and Census TIGER are
 registered trademarks of the U.S. Census Bureau.  ZCTA is a trademark of the U.S. Census Bureau.  The boundary information in the TIGER/Line files are for 
 statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitue a determination of 
 jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions.  The horizontal spatial accuracy information present 
 in these files is provided for the purposes of statistical analysis and census operations only.  No warranty, expressed or implied is made with regard to the 
 accuracy of the spatial accuracy, and no liability is assumed by the U.S. Government in general or the U.S. Census Bureau, specifically as to the spatial or 
 attribute accuracy of the data.  The TIGER/Line may not be suitable for high-precision measurement applications such as engineering problems, property 
 transfers, or other uses that might require highly accurate measurements of the earth's surface.  Coordinates in the TIGER/Line files have six implied 
 decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.</Use_Constraints>
<Title_13_Restrictions>None</Title_13_Restrictions>
<Contact_Organization section="point of contact">U.S. Department of Commerce,U.S. Census Bureau, Geography Division, Geographic Products 
Management Branch</Contact_Organization>
<Address_Type section="point of contact">mailing</Address_Type>
<Address section="point of contact">4700 Silver Hill Road, Stop 7400</Address>
<City section="point of contact">Washington</City>
<State_or_Province section="point of contact">DC</State_or_Province>
<Postal_Code section="point of contact">20233-7400</Postal_Code>
<Country section="point of contact">United States</Country>
<Contact_Voice_Telephone section="point of contact">301-763-1128</Contact_Voice_Telephone>
<Contact_Facsimile_Telephone section="point of contact">301-457-4710</Contact_Facsimile_Telephone>
<Contact_Electronic_Mail_Address section="point of contact">tiger@census.gov</Contact_Electronic_Mail_Address>
<!-- Browse Graphic -->
<Browse_Graphic_File_Name gid1="1"> http://www.census.gov/geo/www/geodiagram.pdf</Browse_Graphic_File_Name>
<Browse_Graphic_File_Description gid1="1"> A graphic explanation of the Census Bureau's Legal and Statistical Geogrpahic Entities and how they 
relate to one another </Browse_Graphic_File_Description>
<Browse_Graphic_File_Type gid1="1"> PDF </Browse_Graphic_File_Type>
<Data_Set_Character_Set>8859part1</Data_Set_Character_Set>
<Data_Set_Language>eng</Data_Set_Language>
<Native_Data_Set_Environment> The Spatial files used to produce the map were first generalized and processed in ArcInfo 
Workstation 8.01</Native_Data_Set_Environment>
<!-- Cross Reference -->
<!-- Citation Information -->       
<Originator section ="cross reference" gid1="1" gid2="1"> U.S Census Bureau, Geography Division, Catographic Products Management Branch 
</Originator>
<Publication_Date section="cross reference" gid1="1">20040721</Publication_Date>
<Title section ="cross reference" gid1="1"> TIGER/Line Files, 2003, Maryland, Talbot County </Title>
<Online_Linkage section ="cross reference" gid1="1" gid2="1">http://www.census.gov/geo/www/cob/bg20000.html</Online_Linkage>

<!---Data Quality Information -->
<Attribute_Accuracy_Report>Accurate against Federal information Processing Standards (FIPS), FIPS Publication 6-4, and FIPS-55 at the 
100 percent level for the codes and base names.  The remaining attribute information has been examined but has not been fully tested for 
accuracy.</Attribute_Accuracy_Report>
<Logical_Consistency_Report>The feature network of lines (as represented by Record Types 1 and 2) is complete for census purposes.  
Spatial objects in TIGER/Line belong to the "Geometry and Topology" (GT) class of objects in the "Spatial Data Transfer Standard" (SDTS) 
FIPS Publication 173 and are topologically valid. Node/geometry and topology GT-polygon/chain relationships are collected or generated to
 satisfy topological edit requirements.  These requirements include: (1) Complete chains must begin and end at nodes.(2) Complete chains 
 must connect to each other at nodes.  (3) Complete chains do not extend through nodes.(4) Left and right GT-polygons are defined for 
 each complete chain element and are consistent throughout the extract process.  (5) The chains representing the limits of the files are 
 free of gaps.  The Census Bureau performed automated tests to ensure logical consistency and limits of files.  All polygons are tested 
 for closure.  The Census Bureau uses its internally developed Geographic Update System to enhance and modify spatial and attribute data 
 in the Census TIGER database.  Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, 
 places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities.  The 
 Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census TIGER 
 database files.  Most of the codes for all geographic entities except states, counties, and congressional districts were provided to the 
 Census Bureau by the USGS, the agency responsible for maintaining FIPS 55.  Feature attribute information has been examined but has not 
 been fully tested for consistency.</Logical_Consistency_Report>
<Completeness_Report>Data completeness of the TIGER/Line files reflects the contents of the Census TIGER database at the time the TIGER/Line files (2004 Second Edition 
version) were created.</Completeness_Report>
<Horizontal_Positional_Accuracy_Report>The Census Bureau uses Global Positioning System (GPS) coordinates at road centerline intersections to evaluate the horizontal spatial
 accuracy of source files that may be used to realign road features in the TIGER database and test the horizontal spatial accuracy of the road features in the TIGER/Line 
 files.  The test compares a survey-grade GPS coordinate to its associated road centerline intersection in the TIGER file.  The test is based upon an independent collection
 of GPS coordinates for a random sample of road intersections from a centerline file that meet certain criteria.  The points are referred to as the sample points and are 
 gathered through a private contractor working for the Census Bureau.  Since the collection method uses survey-quality GPS-based field techniques, the resulting control 
 points are considered "ground truth" against which the TIGER road centerline intersection coordinates are compared.  The distances between the coordinates are calculated 
 and the Census Bureau determines the Circular Error 95% (CE95).  That is, the accuracy of the file in meters with 95% confidence.  The CE95 can be calculated from the mean
 and standard deviation by using the formula: mean of differences plus (2.65 times the standard deviation).  CE95 results reported for each file tested are determined using
 a spreadsheet with embedded statistical formula.  The use and applicability of the spreadsheet and its embedded formula have been verified by Census Bureau statisticians.
 The basis of the calculation is the use of the root mean square error (RMSE).  This is the method as stated in the U.S. Government's Federal Geographic Data Committee 
 Standard FGDC-STD-007.3-1998, Geospatial Positioning Accuracy Standards. Part 3: National Standard for Spatial Data Accuracy.  The results of using this measure of accuracy
 are in compliance with Federal Spatial Data requirements.  In terms of the Census Bureau application, the dataset coordinate values are those taken from the centerline file
 and the coordinate values from an independent source of higher accuracy are those acquired through the Census Bureau's contractor. Please note that the horizontal spatial 
 accuracy, where reported, refers only to the realigned road features identified as matched to the positionally accurate source file with that accuracy.  It is not the 
 spatial accuracy of the TIGER/Line file as a whole.</Horizontal_Positional_Accuracy_Report>
<Horizontal_Positional_Accuracy_Value gid1="1">193.520 meters for 0</Horizontal_Positional_Accuracy_Value>
<Horizontal_Positional_Accuracy_Explanation gid1="1">The Census Bureau uses root mean square error (RSME)as stated in the FGDC-STD-007.3-1998, Geospatial Positioning 
Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy.</Horizontal_Positional_Accuracy_Explanation>
<Horizontal_Positional_Accuracy_Value gid1="2">4.146 meters for 261</Horizontal_Positional_Accuracy_Value>
<Horizontal_Positional_Accuracy_Explanation gid1="2">The Census Bureau uses root mean square error (RSME)as stated in the FGDC-STD-007.3-1998, Geospatial Positioning 
Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy.</Horizontal_Positional_Accuracy_Explanation>

<!--Source Information -->
<Originator section="source" gid1="1" gid2="1">11: U.S. Department of Commerce, U.S. Census Bureau,Geography Division</Originator>
<Publication_Date section="source" gid1="1">11: Unpublished material</Publication_Date>
<Title section="source" gid1="1">11: Census TIGER database</Title>
<Type_of_Source_Media gid1="1">11: On Line</Type_of_Source_Media>
<Beginning_Date section="source" gid1="1">11: 200408</Beginning_Date>
<Ending_Date section="source" gid1="1">11: 200502</Ending_Date>
<Source_Currentness_Reference section="source" gid1="1">11:Date the file was made available to create TIGER/Line extracts.</Source_Currentness_Reference>
<Source_Citation_Abbreviation section="source" gid1="1">11:TIGER</Source_Citation_Abbreviation>
<Source_Contribution section="source" gid1="1">11: Selected geographic and cartographic information(line segments) from the Census TIGER database.</Source_Contribution>

<!--Source Information -->
<Originator section="source" gid1="2" gid2="2">22: 261, Cabarrus County</Originator>
<Publication_Date section="source" gid1="2">22: Unknown</Publication_Date>
<Title section="source" gid1="2">22: Cabarrus County Data</Title>
<Type_of_Source_Media gid1="2">22: CD-ROM</Type_of_Source_Media>
<Beginning_Date section="source" gid1="2">22: Unknown</Beginning_Date>
<Ending_Date section="source" gid1="2">22: Unknown</Ending_Date>
<Source_Currentness_Reference gid1="2">22: Unknown</Source_Currentness_Reference>
<Source_Citation_Abbreviation gid1="2">22: None</Source_Citation_Abbreviation>
<Source_Contribution gid1="2">22: Coordinates to realign selected road features in the Census TIGER database.</Source_Contribution>

<!--Source Information -->
<Originator section="source" gid1="3" gid2="3">33: 261, Cabarrus County</Originator>
<Publication_Date section="source" gid1="3">33: 20010201</Publication_Date>
<Title section="source" gid1="3">33: Cabarrus County Data</Title>
<Type_of_Source_Media gid1="3">33: CD-ROM</Type_of_Source_Media>
<Beginning_Date section="source" gid1="3">33: 20010201</Beginning_Date>
<Ending_Date section="source" gid1="3">33:20010201</Ending_Date>
<Source_Currentness_Reference gid1="3">33: Publication Date</Source_Currentness_Reference>
<Source_Citation_Abbreviation gid1="3">33: None</Source_Citation_Abbreviation>
<Source_Contribution gid1="3">33: Coordinates to realign selected hydrographic features in the Census TIGER database.</Source_Contribution>

<!-- Process Step -->
<Process_Description gid1="2">2 In order for others to use the information in the Census TIGER database in a GIS or for other geographic 
applications, the Census Bureau releases periodic extracts of selected information from the Census TIGER database, organized as topologically consistent networks.  Software (TIGER DB routines) written by the Geography Division allows for efficient access to Census TIGER system data.  TIGER/Line files are extracted from the Census TIGER database by county or statistical equivalent area.  Census TIGER data for a given county or statistical equivalent area is then distributed among 19 fixed length record ASCII files, each one containing attributes for either line, polygon,or landmark geographic data types.  The Census Bureau has released various versions of the TIGER/Line files since 1988, with each version having more updates (feature and feature names, address ranges and ZIP Codes, coordinate updates, revised field definitions, etc.) than the previous version.</Process_Description>
<Source_Used_Citation_Abbreviation gid1="2">2 Census TIGER database</Source_Used_Citation_Abbreviation>
<Process_Date gid1="2">2005</Process_Date>
<Source_Produced_Citation_Abbreviation gid1="2">2 BAS20040831</Source_Produced_Citation_Abbreviation>

<!-- Spatial Data Organization Information -->
<Indirect_Spatial_Reference>Federal Information Processing Standards (FIPS) and feature names.</Indirect_Spatial_Reference>
<Direct_Spatial_Reference_Method>Vector</Direct_Spatial_Reference_Method>
<SDTS_Point_and_Vector_Object_Type gid1="1">Node, network</SDTS_Point_and_Vector_Object_Type>
<Point_and_Vector_Object_Count gid1="1">23587</Point_and_Vector_Object_Count>
<SDTS_Point_and_Vector_Object_Type gid1="2">Entity point</SDTS_Point_and_Vector_Object_Type>
<Point_and_Vector_Object_Count gid1="2">5</Point_and_Vector_Object_Count>
<SDTS_Point_and_Vector_Object_Type gid1="3">Complete chain</SDTS_Point_and_Vector_Object_Type>
<Point_and_Vector_Object_Count gid1="3">17786</Point_and_Vector_Object_Count>
<SDTS_Point_and_Vector_Object_Type gid1="4">GT-polygon composed of chains</SDTS_Point_and_Vector_Object_Type>
<Point_and_Vector_Object_Count gid1="4">5830</Point_and_Vector_Object_Count>

<!-- Spatial Reference Information -->
<!-- Geographic -->
<!-- <Latitude_Resolution>0.000458</Latitude_Resolution>
<Longitude_Resolution>0.000458</Longitude_Resolution>
<Geographic_Coordinate_Units>Decimal degrees</Geographic_Coordinate_Units> -->

<!-- Planar -->
<!-- Map Projection -->
<!-- <Map_Projection_Name gid1="1">Albers Conical Equal Area</Map_Projection_Name>
<Standard_Parallel gid1="1">37.661388888888889</Standard_Parallel>
<Standard_Parallel gid1="1">40.334722222222222</Standard_Parallel>
<Longitude_of_Central_Meridian gid1="1">-105.545555555555556</Longitude_of_Central_Meridian>
<Latitude_of_Projection_Origin gid1="1">36.993055555555556</Latitude_of_Projection_Origin>
<False_Easting gid1="1">0.00000</False_Easting>
<False_Northing gid1="1">0.00000</False_Northing> -->

<!-- Grid Coordinate System -->
<Grid_Coordinate_System_Name gid1="1">Universal Transverse Mercator</Grid_Coordinate_System_Name>
<UTM_Zone_Number gid1="1">18</UTM_Zone_Number>
<Map_Projection_Name gid1="1">Transverse Mercator</Map_Projection_Name>
<Scale_Factor_at_Central_Meridian gid1="1">1.0000591525</Scale_Factor_at_Central_Meridian>
<Longitude_of_Central_Meridian gid1="1">-96.000000</Longitude_of_Central_Meridian>
<Latitude_of_Projection_Origin gid1="1" >37.50000</Latitude_of_Projection_Origin>
<False_Easting gid1="1">0</False_Easting>
<False_Northing gid1="1">525</False_Northing>

<!-- Planar Coordinate Information > -->
<Planar_Coordinate_Encoding_Method gid1="1">coordinate pair</Planar_Coordinate_Encoding_Method> 
<!-- Coordinate Representation -->
<Abscissa_Resolution gid1="1">.082</Abscissa_Resolution>
<Ordinate_Resolution gid1="1">.082</Ordinate_Resolution>
<Planar_Distance_Units gid1="1">meters</Planar_Distance_Units> 

<!-- Local -->
<!-- <Local_Description> This is a two dimensional coordinate system and has the following parameters. It is a Transverse Mercator Projection
(TM) with a false northing 4,600 meters (15,091.8333 feet) at 43.00000 degrees latitude and a false easting of 31,600 meters (103674.3333 feet)
at 88.0000 degrees latitude </Local_Description>
<Local_Georeference_Information> The Brown County Coordinate System is referenced to the North American Datum of 1983 with 1991 (NAD83-91)
adjustment values</Local_Georeference_Information> -->
<!-- Geodetic Model -->
<Horizontal_Datum_Name>North American Datum of 1983 in the 48 contiguous states, the District of Columbia, Alaska, Puerto Rico, and the 
Virgin Islands of the United States.  Regional datums were used in Hawaii and the Pacific Island Areas (American Samoa, Guam, and the 
Commonwealth of the Northern Mariana Islands)</Horizontal_Datum_Name>
<Ellipsoid_Name>Geodetic Reference System 80 where the datum is the North American Datum of 1983</Ellipsoid_Name>
<Semi-Major_Axis>6378137</Semi-Major_Axis>
<Denominator_of_Flattening_Ratio>298257</Denominator_of_Flattening_Ratio>

<!-- Entity and Attribute Information-->
<!-- Detailed Description -->
<!-- Entity Type -->
<Entity_Type_Label gid1="1" >1: Primary Highway with Limited Access</Entity_Type_Label>
<Entity_Type_Definition gid1="1">1:Interstate highways and some toll highways are in this category (A1) and are distinguished by the presence of
interchanges</Entity_Type_Definition>
<Entity_Type_Definition_Source gid1="1">1: 2003 TIGER/Line files Technical Documentation </Entity_Type_Definition_Source>

<!-- Entity Type -->
<Entity_Type_Label gid1="2" >2: Primary Highway with Limited Access</Entity_Type_Label>
<Entity_Type_Definition gid1="2">2:Interstate highways and some toll highways are in this category (A1) and are distinguished by the presence of
interchanges</Entity_Type_Definition>
<Entity_Type_Definition_Source gid1="2">2: 2003 TIGER/Line files Technical Documentation </Entity_Type_Definition_Source>

<!--Attribute-->
<Attribute_Label gid1="1" gid2="1">11: Census Feature Class Codes</Attribute_Label>
<Attribute_Definition gid1="1" gid2="1">11: 2003 TIGER\Line Files Technical Documentation</Attribute_Definition>
<Attribute_Definition_Source gid1="1" gid2="1">11: 2003 TIGER/Line Files Technical Documentation</Attribute_Definition_Source>

<!--Attribute-->
<Attribute_Label gid1="1" gid2="2">12; Census Feature Class Codes</Attribute_Label>
<Attribute_Definition gid1="1" gid2="2">12; 2003 TIGER\Line Files Technical Documentation</Attribute_Definition>
<Attribute_Definition_Source gid1="1" gid2="2">12; 2003 TIGER/Line Files Technical Documentation</Attribute_Definition_Source>

<!--Attribute-->
<Attribute_Label gid1="2" gid2="1">21; Census Feature Class Codes</Attribute_Label>
<Attribute_Definition gid1="2" gid2="1">21; 2003 TIGER\Line Files Technical Documentation</Attribute_Definition>
<Attribute_Definition_Source gid1="2" gid2="1">21; 2003 TIGER/Line Files Technical Documentation</Attribute_Definition_Source>

<!--Attribute-->
<Attribute_Label gid1="2" gid2="2">22; Census Feature Class Codes</Attribute_Label>
<Attribute_Definition gid1="2" gid2="2">22; 2003 TIGER\Line Files Technical Documentation</Attribute_Definition>
<Attribute_Definition_Source gid1="2" gid2="2">22; 2003 TIGER/Line Files Technical Documentation</Attribute_Definition_Source>

<!-- Attribute Domain Values -->
<!-- Enumerated Domain-->
<Enumerated_Domain_Value gid1="1" gid2="1" gid3="1" >111: A25</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="1" gid2="1" gid3="1">111: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="1" gid2="1" gid3="1">111: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>
<!-- Enumerated Domain-->
<Enumerated_Domain_Value gid1="1" gid2="1" gid3="2" >112: A25</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="1" gid2="1" gid3="2" >112: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="1" gid2="1" gid3="2" >112: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>
<!-- Enumerated Domain-->
<Enumerated_Domain_Value gid1="1" gid2="2" gid3="1" >121: A25</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="1" gid2="2" gid3="1" >121: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="1" gid2="2" gid3="1" >121: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>
<!-- Enumerated Domain-->
<Enumerated_Domain_Value gid1="1" gid2="2" gid3="2" >122: A25</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="1" gid2="2" gid3="2" >122: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="1" gid2="2" gid3="2" >122: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>
<!-- Enumerated Domain-->
<Enumerated_Domain_Value gid1="2" gid2="1" gid3="1" >211: A25</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="2" gid2="1" gid3="1">211: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="2" gid2="1" gid3="1">211: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>
<!-- second Enumerated Domain -->
<Enumerated_Domain_Value gid1="2" gid2="2" gid3="2" >222: A25-two</Enumerated_Domain_Value>
<Enumerated_Domain_Value_Definition gid1="2" gid2="2" gid3="2">222: Two: Primary road without limited access, U.S highways, seperated </Enumerated_Domain_Value_Definition>
<Enumerated_Domain_Value_Definition_Source gid1="2" gid2="2" gid3="2">222: Two: 2003 TIGER/Line Files Technical Documentation</Enumerated_Domain_Value_Definition_Source>


<!--Range Domain-->
<Range_Domain_Minimum gid1="1" gid2="1" gid3 ="1">111: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="1" gid2="1" gid3 ="1">111: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="1" gid2="1" gid3 ="1">111: meters</Attribute_Units_of_Measure>
<!--Range Domain-->
<Range_Domain_Minimum gid1="1" gid2="1" gid3="2" >112: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="1" gid2="1" gid3="2" >112: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="1" gid2="1" gid3="2" >112: meters</Attribute_Units_of_Measure>
<!--Range Domain-->
<Range_Domain_Minimum gid1="1" gid2="2" gid3="1" >121: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="1" gid2="2" gid3="1" >121: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="1" gid2="2" gid3="1" >121: meters</Attribute_Units_of_Measure>
<!--Range Domain-->
<Range_Domain_Minimum gid1="1" gid2="2" gid3="2" >122: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="1" gid2="2" gid3="2" >122: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="1" gid2="2" gid3="2" >122: meters</Attribute_Units_of_Measure>
<!--Range Domain-->
<Range_Domain_Minimum gid1="2" gid2="1" gid3="1" >211: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="2" gid2="1" gid3="1" >211:: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="2" gid2="1" gid3="1" >211: meters</Attribute_Units_of_Measure>
<!--Range Domain-->
<Range_Domain_Minimum gid1="2" gid2="2" gid3="2" >222: 25</Range_Domain_Minimum>
<Range_Domain_Maximum gid1="2" gid2="2" gid3="2" >222:: 100</Range_Domain_Maximum>
<Attribute_Units_of_Measure gid1="2" gid2="2" gid3="2" >222: meters</Attribute_Units_of_Measure>

<!-- Codeset Domain -->
<Codeset_Name gid1="1" gid2="1" gid3 ="1">111: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="1" gid2="1" gid3 ="1">111: The Secretary of Commerce</Codeset_Source>
<!-- Codeset Domain -->
<Codeset_Name gid1="1" gid2="1" gid3="2" >112: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="1" gid2="1" gid3="2" >112: The Secretary of Commerce</Codeset_Source> -->
<!-- Codeset Domain -->
<Codeset_Name gid1="1" gid2="2" gid3="1" >121: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="1" gid2="2" gid3="1" >121: The Secretary of Commerce</Codeset_Source>
<!-- Codeset Domain -->
<Codeset_Name gid1="1" gid2="2" gid3="2" >122: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="1" gid2="2" gid3="2" >122: The Secretary of Commerce</Codeset_Source> -->
<!-- Codeset Domain -->
<Codeset_Name gid1="2" gid2="1" gid3="1" >211: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="2" gid2="1" gid3="1" >211: The Secretary of Commerce</Codeset_Source>
<!-- Codeset Domain -->
<Codeset_Name gid1="2" gid2="2" gid3="2" >222: FIPS PUB6-4 Counties and Equivalent Entities of the United States, its Possessions, and Associated Areas</Codeset_Name>
<Codeset_Source gid1="2" gid2="2" gid3="2" >222: The Secretary of Commerce</Codeset_Source>

<!-- unreperesenatable Domain -->
<Unrepresentable_Domain gid1="1" gid2="1" gid3 ="1">111: whatever </Unrepresentable_Domain>
<!-- unreperesenatable Domain -->
<Unrepresentable_Domain gid1="1" gid2="1" gid3="2" >112: whatever </Unrepresentable_Domain>
<!-- unreperesenatable Domain -->
<Unrepresentable_Domain gid1="1" gid2="2" gid3 ="1">121: whatever </Unrepresentable_Domain>


<!-- Overview Description -->
<Entity_and_Attribute_Overview gid1="1">The TIGER/Line files contain data describing three major types of features/entities; Line 
Features - (1) Roads (2) Railroads (3) Hydrography (4) Miscellaneous transportation features and selected power lines and pipe lines 
(5) Legal (governmental unit) and statistical boundaries. Landmark Features - (1) Point landmarks, e.g., schools and churches; sporadic 
coverage added on an as-needed basis (2) Area landmarks, e.g., Parks and cemeteries; sporadic coverage added on an as-needed basis.  
Polygon features - (1) Geographic entity codes for areas used to tabulate the Census 2000 census statistical data and governmental unit 
boundaries legally in effect as of the latest Boundary and Annexation Survey (BAS) (2) Locations of area landmarks. The line features and
 polygon information form the majority of data in the TIGER/Line files.  Some of the data/attributes describing the lines include 
 coordinates, feature identifiers (names), CFCCs (used to identify the most noticeable characteristic of a feature), address ranges, and 
 geographic entity codes.  The Census Bureau includes landmark features on an as-needed-basis and has made no attempt to ensure that all 
 instances of a particular landmark feature were included. The TIGER/Line files contain point and area labels that describe landmark features 
 and provide locational reference. Area landmarks consist of a feature name or label and feature Landmarks may overlap or refer to the same set of 
 polygons. The Census TIGER database uses collections of spatial objects (points, lines, and polygons) to model or describe real-world geography.
   The Census Bureau uses these spatial objects to represent features such as streets, rivers, and political boundaries and assigns attributes to 
   these features to identify and describe specific features such as the 500 block of Market Street in Philadelphia, Pennsylvania.</Entity_and_Attribute_Overview>
<Entity_and_Attribute_Detail_Citation gid1="1">U.S. Census Bureau, TIGER/Line files, 2004 Second Edition Technical Documentation.  The 
TIGER/Line documentation defines the terms and definitions used within the files.</Entity_and_Attribute_Detail_Citation>

<!--Distribution Information-->
<!--Contact Information-->
<!-- Contact Organization Primary-->
<Contact_Organization section="distributor">U.S. Department of Commerce, U.S. Census Bureau,Geography Division, Geographic Products Management Branch</Contact_Organization>
<Address_Type section="distributor">mailing</Address_Type>
<Address section="distributor" gid1="1">4600 Silver Hill Road, Stop 7400</Address>
<City section="distributor">Washington</City>
<State_or_Province section="distributor">DC</State_or_Province>
<Postal_Code section="distributor">20233-7400</Postal_Code>
<Country section="distributor">USA</Country>
<Contact_Voice_Telephone section="distributor" gid1="1">301-763-1128</Contact_Voice_Telephone>
<Contact_Facsimile_Telephone section="distributor">301-457-4710</Contact_Facsimile_Telephone>
<Contact_Electronic_Mail_Address section="distributor">tiger@census.gov</Contact_Electronic_Mail_Address>
<Resource_Description>2004 Second Edition TIGER/Line Files</Resource_Description>
<Distribution_Liability>No warranty, expressed or implied is made with regard to the accuracy of these data, and no 
liability is assumed by the U.S. Government in general or the U.S. Census Bureau in specific as to the spatial or 
attribute accuracy of the data.  The act of distribution shall not constitute any such warranty and no responsibility is
 assumed by the U.S. Government in the use of these files.  The boundary information in the TIGER/Line files are for 
 statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does
  not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not 
  legal land descriptions.</Distribution_Liability>
 <!-- Standard Order Process -->
<!-- Digital Form -->
<!-- Digital Transfer Information-->
<Format_Name gid1="1" gid2="1">TGRLN (compressed)</Format_Name>
<File_Decompression_Technique gid1="1" gid2="1">PK-ZIP, version 1.93A or higher</File_Decompression_Technique>
<Transfer_Size gid1="1" gid2="1">5505050</Transfer_Size>
<!-- Digital Transfer Option-->
<!-- Online Option-->
<!-- Computer Contact Information -->
<!-- Network Address -->
<Network_Resource_Name gid1="1" gid2="1" gid3="1">http://www.census.gov/geo/www/tiger</Network_Resource_Name>
<!-- Offline Option -->
<!-- Offline_Media gid1="1" gid2="1">CD-ROM, DVD-ROM</Offline_Media>
<Recording_Format gid1="1" gid2="1">ISO 9660</Recording_Format -->
<Fees gid1="1">The online copy of the TIGER/Line files may be accessed without charge.  See http://www.census.gov/geo/www/tiger for information on availability on CD-ROM/DVD and associated costs for these products.</Fees>
<Ordering_Instructions gid1="1">To obtain more information about ordering TIGER/Line files visit http://www.census.gov/geo/www/tiger.</Ordering_Instructions>
<Technical_Prerequisites>The TIGER/Line files contain geographic data only and do not include display or mapping software or statistical data.  For information on how to 
use the TIGER/Line data with a specific software package users should contact the company that produced the software.  A list of some vendors who have developed software
 capable of processing TIGER/Line files can be found by visiting http://www.census.gov/geo/www/tiger.  The TIGER/Line files are provided in ASCII text format only.  Users 
 are responsible for converting or translating the files into a format used by their specific software package.</Technical_Prerequisites>

<!-- Metadata Reference Information -->
<Metadata_Date>20050112</Metadata_Date>
<!-- Metadata Contact -->
<!-- Contact Information -->
<!-- Contact Organization Primary -->
<Contact_Organization section="metadata">U.S. Department of Commerce, U.S. Census Bureau,Geography Division, Geographic Products Management Branch</Contact_Organization>
<!-- Contact Address -->
<Address_Type section="metadata">mailing</Address_Type>
<Address section="metadata" gid1="1">4700 Silver Hill Road, Stop 7400</Address>
<City section="metadata">Washington</City>
<State_or_Province section="metadata">DC</State_or_Province>
<Postal_Code section="metadata">20233-7400</Postal_Code>
<Country section="metadata">United States</Country>
<Contact_Voice_Telephone section="metadata">301-763-1128</Contact_Voice_Telephone>
<Contact_Facsimile_Telephone section="metadata">301-457-4710</Contact_Facsimile_Telephone>
<Contact_Electronic_Mail_Address section="metadata">tiger@census.gov</Contact_Electronic_Mail_Address>
<Metadata_Standard_Name>FGDC Content Standards for Digital Geospatial Metadata</Metadata_Standard_Name>
<Metadata_Standard_Version>FGDC-STD-001-1998</Metadata_Standard_Version>
<Metadata_Character_Set>8859part1</Metadata_Character_Set>
<Metadata_File_Identifier>geo_vector_TIGERLine.xml</Metadata_File_Identifier>
<Metadata_Language>eng</Metadata_Language>
</MIF>				
