<?xml version="1.0"?>
<!--<!DOCTYPE metadata SYSTEM "http://www.esri.com/metadata/esriprof80.dtd">-->
<metadata xml:lang="en"><Esri><CreaDate>20031125</CreaDate><CreaTime>14170400</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20040511</SyncDate><SyncTime>16364900</SyncTime><ModDate>20040511</ModDate><ModTime>16364900</ModTime><MetaID>{DC469F71-21D0-4EE1-86EB-196EEF5334E8}</MetaID></Esri><idinfo><native>TIGER/Line files are created and processed in a VMS environment.  The environment
    consists of two Alpha Server 8400s clustered together running OpenVMS version
    6.2-1H3 used for production operations.  The Census TIGER system is driven by
    DEC Command language (DCL) procedures which invoke C software routines to extract
    selected geographic and cartographic information (TIGER/Line files) from the
    operational Census TIGER data base.</native><descript><langdata Sync="TRUE">en</langdata><abstract>The coverage includes towns within Colfax County that were clipped from the TIGER data of towns, cities within New Mexico. The metadata for the original file follows:TIGER, TIGER/Line, and Census TIGER are registered trademarks of the Bureau
      of the Census. The Redistricting Census 2000 TIGER/Line files are an extract
      of selected geographic and cartographic information from the Census TIGER
      data base.  The geographic coverage for a single TIGER/Line file is a county
      or statistical equivalent entity, with the coverage area based on January 1,
      2000 legal boundaries.  A complete set of Redistricting Census 2000 TIGER/Line
      files includes all counties and statistically equivalent entities in the United
      States and Puerto Rico.  The Redistricting Census 2000 TIGER/Line files will
      not include files for the Island Areas. The Census TIGER data base 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 Redistricting
      Census 2000 TIGER/Line files consist of line segments representing physical
      features and governmental and statistical boundaries.  The Redistricting Census
      2000 TIGER/Line files do NOT contain the ZIP Code Tabulation Areas (ZCTAs) and
      the address ranges are of approximately the same vintage as those appearing in
      the 1999 TIGER/Line files.  That is, the Census Bureau is producing the
      Redistricting Census 2000 TIGER/Line files in advance of the computer processing
      that will ensure that the address ranges in the TIGER/Line files agree with the
      final Master Address File (MAF) used for tabulating Census 2000.  The files contain
      information distributed over a series of record types for the spatial objects of a
      county.  There are 17 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, key geographic features, and area
      boundaries.  The Redistricting Census 2000 TIGER/Line data dictionary contains
      a complete list of all the fields in the 17 record types.</abstract><purpose> In order for others to use the information in the Census TIGER data base in a
      geographic information system (GIS) or for other geographic applications, the
      Census Bureau releases to the public extracts of the data base in the form of
      TIGER/Line files.  Various versions of the TIGER/Line files have been released;
      previous versions include the 1990 Census TIGER/Line files, the 1992 TIGER/Line
      files, the 1994 TIGER/Line files, the 1995 TIGER/Line files, the 1997 TIGER/Line
      files, the 1998 TIGER/Line files, and the 1999 TIGER/Line files.  The Redistricting
      Census 2000 TIGER/Line files were originally produced to support the Census 2000
      Redistricting Data Program..</purpose><supplinf>To find out more about TIGER/Line files and other Census TIGER
      data base derived data sets visit http://www.census.gov/geo/www/tiger.</supplinf></descript><citation><citeinfo><origin>U.S. Department of Commerce</origin><pubdate>2001</pubdate><title Sync="TRUE">ColfaxTowns</title><ftname Sync="TRUE">ColfaxTowns</ftname><geoform Sync="TRUE">vector digital data</geoform><edition> Redistricting Census 2000</edition><serinfo><sername>TIGER/Line Files</sername><issue>Version (MMYY) represents the month and year file created</issue></serinfo><pubinfo><pubplace>Washington, DC</pubplace><publish>U.S. Department of Commerce</publish></pubinfo><onlink Sync="TRUE">\\GRETCHEN\I$\NFS2004\Culture\ColfaxTowns.shp</onlink><othercit>Clipped to include only towns within Colfax County.</othercit></citeinfo></citation><timeperd><current>2000</current><timeinfo><sngdate><caldate>2000</caldate></sngdate></timeinfo></timeperd><status><progress>Complete</progress><update>TIGER/Line files are extracted from the Census TIGER data base when needed for</update></status><spdom><bounding><westbc Sync="TRUE">-105.278610</westbc><eastbc Sync="TRUE">-104.403152</eastbc><northbc Sync="TRUE">36.920204</northbc><southbc Sync="TRUE">36.356289</southbc></bounding><lboundng><leftbc Sync="TRUE">-105.278610</leftbc><rightbc Sync="TRUE">-104.403152</rightbc><bottombc Sync="TRUE">36.356289</bottombc><topbc Sync="TRUE">36.920204</topbc></lboundng></spdom><keywords><theme><themekt>None</themekt><themekey>Line Feature</themekey><themekey>Feature Identifier</themekey><themekey>Census Featrue Class Code (CFCC)</themekey><themekey>Address Range</themekey><themekey>Geographic Entity</themekey></theme><place><placekey>Raton</placekey><placekey>Cimarron</placekey><placekey>Eagle Nest</placekey><placekey>Maxwell</placekey><placekey>Springer</placekey></place></keywords><accconst>None</accconst><useconst>None.  Acknowledgment of the U.S. Bureau of the Census would be appreciated for
    products derived from these files.  TIGER, TIGER/Line, and Census TIGER are
    registered trademarks of the Bureau of the Census..</useconst><natvform Sync="TRUE">Shapefile</natvform><ptcontac><cntinfo><cntaddr><addrtype>physical address</addrtype><address>8903 Presidential Parkway, WP I</address><city>Upper Marlboro</city><state>Maryland</state><postal>20772</postal><country>USA</country></cntaddr><cntorgp><cntorg> U.S. Department of Commerce</cntorg></cntorgp><cntvoice>(301) 457-1128</cntvoice><cntfax> (301) 457-4710</cntfax><cntemail>tiger@census.gov</cntemail><cntaddr><addrtype>mailing address</addrtype><address>Bureau of the Census</address><city>Washington</city><state>District of Columbia</state><postal>20233-7400</postal><country>USA</country></cntaddr></cntinfo></ptcontac></idinfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows 2000 Version 5.1 (Build 2600) Service Pack 1; ESRI ArcCatalog 8.2.0.700</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">ColfaxTowns</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="001"></SpatRepTypCd></spatRpType><geoBox esriExtentType="native"><westBL Sync="TRUE">-105.27861</westBL><eastBL Sync="TRUE">-104.403152</eastBL><northBL Sync="TRUE">36.920204</northBL><southBL Sync="TRUE">36.356289</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-105.27861</westBL><eastBL Sync="TRUE">-104.403152</eastBL><northBL Sync="TRUE">36.920204</northBL><southBL Sync="TRUE">36.356289</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><metainfo><langmeta Sync="TRUE">en</langmeta><metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv><mettc Sync="TRUE">local time</mettc><metc><cntinfo><cntorgp><cntper>REQUIRED: The person responsible for the metadata information.</cntper><cntorg>REQUIRED: The organization responsible for the metadata information.</cntorg></cntorgp><cntaddr><addrtype>REQUIRED: The mailing and/or physical address for the organization or individual.</addrtype><city>REQUIRED: The city of the address.</city><state>REQUIRED: The state or province of the address.</state><postal>REQUIRED: The ZIP or other postal code of the address.</postal></cntaddr><cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice></cntinfo></metc><metd Sync="TRUE">20040511</metd><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distinfo><resdesc Sync="TRUE">Downloadable Data</resdesc><stdorder><digform><digtinfo><transize Sync="TRUE">0.031</transize><dssize Sync="TRUE">0.031</dssize><formname>TGRLN (compressed)</formname><formverd> Redistricting Census 2000</formverd><filedec>PK-ZIP, version 1.93A or higher</filedec></digtinfo></digform><fees>The online copy of the TIGER/Line files may be accessed without charge.  See</fees><ordering>To obtain more information about ordering TIGER/Line files visit
      http://www.census.gov/geo/www/tiger.
      Technical_Prequisites: The Redistricting Census 2000 TIGER/Line files contain geographic
      data only and do not include display or mapping software or statistical data.  A
      list of vendors who have developed software capable of processing TIGER/Line files
      can be found by visiting http://www.census.gov/geo/www/tiger</ordering></stdorder><distliab>No warranty, expressed or implied is made and no liability is
    assumed by the U.S. Government in general or the U.S. Census Bureau in specific as
    to the positional 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.</distliab></distinfo><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\GRETCHEN\I$\NFS2004\Culture\ColfaxTowns.shp</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">0.031</transSize></distorTran><distorFormat><formatName Sync="TRUE">Shapefile</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Vector</direct><ptvctinf><esriterm Name="ColfaxTowns"><efeatyp Sync="TRUE">Simple</efeatyp><efeageom Sync="TRUE">Polygon</efeageom><esritopo Sync="TRUE">FALSE</esritopo><efeacnt Sync="TRUE">5</efeacnt><spindex Sync="TRUE">TRUE</spindex><linrefer Sync="TRUE">FALSE</linrefer></esriterm><sdtsterm Name="ColfaxTowns"><sdtstype Sync="TRUE">G-polygon</sdtstype><ptvctcnt Sync="TRUE">5</ptvctcnt></sdtsterm></ptvctinf></spdoinfo><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_North_American_1927</geogcsn></cordsysn><geograph><geogunit Sync="TRUE">Decimal degrees</geogunit><latres>0.000458</latres><longres>0.0004580.000000</longres></geograph><geodetic><horizdn Sync="TRUE">North American Datum of 1927</horizdn><ellips Sync="TRUE">Clarke 1866</ellips><semiaxis Sync="TRUE">6378206.400000</semiaxis><denflat Sync="TRUE">294.978698</denflat></geodetic></horizsys></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">GCS_North_American_1927</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><VectSpatRep><topLvl><TopoLevCd Sync="TRUE" value="001"></TopoLevCd></topLvl><geometObjs Name="ColfaxTowns"><geoObjTyp><GeoObjTypCd Sync="TRUE" value="001"></GeoObjTypCd></geoObjTyp><geoObjCnt Sync="TRUE">5</geoObjCnt></geometObjs></VectSpatRep></spatRepInfo><eainfo><detailed Name="ColfaxTowns"><enttyp><enttypl Sync="TRUE">ColfaxTowns</enttypl><enttypt Sync="TRUE">Feature Class</enttypt><enttypc Sync="TRUE">5</enttypc></enttyp><attr><attrlabl Sync="TRUE">FID</attrlabl><attalias Sync="TRUE">FID</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><attr><attrlabl Sync="TRUE">AREA</attrlabl><attalias Sync="TRUE">AREA</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">15</attwidth><atnumdec Sync="TRUE">3</atnumdec></attr><attr><attrlabl Sync="TRUE">PERIMETER</attrlabl><attalias Sync="TRUE">PERIMETER</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">15</attwidth><atnumdec Sync="TRUE">3</atnumdec></attr><attr><attrlabl Sync="TRUE">PLACES_</attrlabl><attalias Sync="TRUE">PLACES_</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">PLACES_ID</attrlabl><attalias Sync="TRUE">PLACES_ID</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">11</attwidth></attr><attr><attrlabl Sync="TRUE">ID</attrlabl><attalias Sync="TRUE">ID</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">8</attwidth></attr><attr><attrlabl Sync="TRUE">COUNTY</attrlabl><attalias Sync="TRUE">COUNTY</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">5</attwidth></attr><attr><attrlabl Sync="TRUE">PLACE</attrlabl><attalias Sync="TRUE">PLACE</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">5</attwidth></attr><attr><attrlabl Sync="TRUE">NAME</attrlabl><attalias Sync="TRUE">NAME</attalias><attrtype Sync="TRUE">String</attrtype><attwidth Sync="TRUE">66</attwidth></attr><attr><attrlabl Sync="TRUE">POP2000</attrlabl><attalias Sync="TRUE">POP2000</attalias><attrtype Sync="TRUE">Number</attrtype><attwidth Sync="TRUE">6</attwidth></attr></detailed></eainfo><mdDateSt Sync="TRUE">20040511</mdDateSt><dataqual><attracc><attraccr> Accurate against Federal information Processing Standards
      (FIPS), FIPS Publication 6-4, and FIPS-55 at the 100% level for the codes and base
      names.  The remaining attribute information has been examined but has not been fully
      tested for accuracy.</attraccr></attracc><logic>The feature network of lines (as represented by Record Types 1 and 2) is compete
    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:
    * Complete chains must begin and end at nodes.
    * Complete chains must connect to each other at nodes.
    * Complete chains do not extend through nodes.
    * Left and right GT-polygons are defined for each complete chain element and are
    consistent throughout the extract process.
    * 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 data base.  Standard geographic codes, such as FIPS codes for states,
    counties, municipalities, and places, 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 data base files.  Most of the Codes
    themselves 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.</logic><complete>  Data completeness of the TIGER/Line files reflects the contents of the Census TIGER
    data base at the time the TIGER/Line files (Redistricting Census 2000 version) were
    created.</complete><posacc><horizpa><horizpar> The information present in these files is provided for the purposes of statistical
        analysis and census operations only.  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.  The positional accuracy varies with the
        source materials used, but generally the information is no better than the established
        national map Accuracy standards for 1:100,000-scale maps from the U.S. Geological
        Survey (USGS); thus it is NOT 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.  The USGS 1:100,000-scale maps
        met national map accuracy standards and use coordinates defined by the North
        American Datum, 1983.  For the contiguous 48 States, the cartographic fidelity of
        most of the Redistricting Census 2000 TIGER/Line files, in areas outside the
        1980 census Geographic Base File/Dual Independent map Encoding (GBF/DIME) file
        coverage and selected other large metropolitan areas, compare favorable with the
        USGS 1:100,000-scale maps.  The Census Bureau cannot specify the accuracy of
        features inside of what was the 1980 GBF/DIME-File coverage or selected metropolitan
        areas.  The Census Bureau added updates to the TIGER/Line files that enumerators
        annotated on maps sheets prepared from the Census TIGER data base as they attempted
        to traverse every street feature shown on the Census 2000 map sheets; the Census
        Bureau also made other corrections from updated map sheets supplied by local
        participants for Census Bureau programs.  The locational accuracy of these updates
        is of unknown quality.  In addition to the Federal, State, and local sources,
        portions of the files may contain information obtained in part from maps and
        other materials prepared by private companies.  Despite the fact the TIGER/Line
        data positional accuracy is not as high as the coordinate values imply, the
        six-decimal place precision is useful when producing maps.  The precision allows
        features that are next to each other on the ground to be placed in the correct
        position, on the map, relative to each other, without overlap.</horizpar></horizpa></posacc><lineage><srcinfo><typesrc>On line</typesrc><srccitea>TIGER</srccitea><srccontr>Selected geographic and cartographic information (line segments) from
        the Census TIGER data base.</srccontr></srcinfo><procstep><procdesc> In order for others to use the information in the Census TIGER data base in
        a GIS or for other geographic applications, the Census Bureau releases periodic
        extracts of selected information from the Census TIGER data base, 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 data base by county or
        statistical equivalent area.  Census TIGER data for a given county or statistical
        equivalent area is then distributed among 17 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.</procdesc></procstep><procstep><procdesc Sync="TRUE">Dataset copied.</procdesc><srcused Sync="TRUE"></srcused><date Sync="TRUE">20031125</date><time Sync="TRUE">14170500</time></procstep></lineage></dataqual></metadata>

