Virgo GIS

FGDC
<metadata xml:lang="en">
  <Esri>
    <CreaDate>20081029</CreaDate>
    <CreaTime>13412400</CreaTime>
    <SyncDate>20020209</SyncDate>
    <SyncTime>11195100</SyncTime>
    <ModDate>20081014</ModDate>
    <ModTime>14443100</ModTime>
    <Sync>FALSE</Sync>
    <MetaID>{40A54C52-B51D-48BE-B665-19EC1DF56F38}</MetaID>
    <SyncOnce>TRUE</SyncOnce>
    <PublishedDocID>{5804EB12-BDE7-43DE-9165-A9F1DBCEE5F8}</PublishedDocID>
    <PublishStatus>Published</PublishStatus>
  </Esri>
  <idinfo>
    <native Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.1.3.679</native>
    <descript>
      <langdata Sync="TRUE">en</langdata>
      <abstract>Colorado Major Roads represents interstate, U.S., and state highways and other major thoroughfares within Colorado.</abstract>
      <purpose>Colorado Major Roads provides an invaluable reference and cartographic layer that make it easy to identify areas in other data sets. Colorado Major Roads overlays accurately on streets and other boundary data.</purpose>
      <supplinf>Largest scale when displaying the data: 1:50,000.</supplinf>
    </descript>
    <citation>
      <citeinfo>
        <origin>Geographic Data Technology, Inc. (GDT)</origin>
        <pubdate>20020401</pubdate>
        <title>Colorado Major Roads 2002</title>
        <ftname Sync="TRUE">cords</ftname>
        <geoform Sync="TRUE">vector digital data</geoform>
        <edition>2002</edition>
        <serinfo>
          <sername>ESRI Data &amp; Maps</sername>
          <issue>2002</issue>
        </serinfo>
        <pubinfo>
          <pubplace>Redlands, California, USA</pubplace>
          <publish>Environmental Systems Research Institute, Inc. (ESRI)</publish>
        </pubinfo>
        <origin>Environmental Systems Research Institute, Inc. (ESRI)</origin>
        <onlink>http://map.princeton.edu/data/ng/45/1k/03/s/content/restricted/data.zip</onlink>
      </citeinfo>
    </citation>
    <timeperd>
      <current>publication date</current>
      <timeinfo>
        <sngdate>
          <caldate>199901</caldate>
        </sngdate>
      </timeinfo>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>Matches software update releases</update>
    </status>
    <spdom>
      <bounding>
        <westbc Sync="TRUE">-109.060108</westbc>
        <eastbc Sync="TRUE">-102.041802</eastbc>
        <northbc Sync="TRUE">41.002342</northbc>
        <southbc Sync="TRUE">36.992515</southbc>
      </bounding>
      <lboundng>
        <leftbc Sync="TRUE">-109.060108</leftbc>
        <rightbc Sync="TRUE">-102.041802</rightbc>
        <bottombc Sync="TRUE">36.992515</bottombc>
        <topbc Sync="TRUE">41.002342</topbc>
      </lboundng>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>line</themekey>
        <themekey>highways</themekey>
        <themekey>roads</themekey>
        <themekey>interstates</themekey>
        <themekey>cfcc</themekey>
        <themekey>transportation</themekey>
      </theme>
      <place>
        <placekey>United States</placekey>
        <placekt>None</placekt>
        <placekey>Colorado</placekey>
      </place>
      <temporal>
        <tempkey>1999</tempkey>
        <tempkt>None</tempkt>
      </temporal>
    </keywords>
    <accconst>Access granted to Licensee only.</accconst>
    <useconst>The data are provided by multiple, third party data vendors under license to ESRI for inclusion on ESRI Data &amp; Maps CD&#8211;ROMs for use with ESRI&#174; software.  Each data vendor has its own data licensing policies and may grant varying redistribution rights to end users. Please consult the redistribution rights below for this data set provided on ESRI Data &amp; Maps CD&#8211;ROMs. As used herein, &#8220;Geodata&#8221; shall mean any digital data set consisting of geographic data coordinates and associated attributes.

The redistribution rights for this data set: Redistribution rights are granted by the data vendor for hard-copy renditions or static, electronic map images (e.g. .gif, .jpeg, etc.) that are plotted, printed, or publicly displayed with proper metadata and source/copyright attribution to the respective data vendor(s).  Geodata is redistributable with a Value-Added Software Application developed by ESRI Business Partners on a royalty-free basis with proper metadata and source/copyright attribution to the respective data vendor(s).

The terms and conditions below apply to all the data sets provided on the ESRI Data &amp; Maps CD&#8211;ROMs.

Proprietary Rights and Copyright: Licensee acknowledges that the Data and Related Materials contain proprietary and confidential property of ESRI and its licensor(s). The Data and Related Materials are owned by ESRI and its licensor(s) and are protected by United States copyright laws and applicable international copyright treaties and/or conventions.

Limited Warranty and Disclaimer: ESRI warrants that the media upon which the Data and Related Materials are provided will be free from defects in materials and workmanship under normal use and service for a period of ninety (90) days from the date of receipt.

THE DATA AND RELATED MATERIALS ARE EXCLUDED FROM THE LIMITED WARRANTY, AND THE LICENSEE EXPRESSLY ACKNOWLEDGES THAT THE DATA CONTAINS SOME NONCONFORMITIES, DEFECTS, OR ERRORS. ESRI DOES NOT WARRANT THAT THE DATA WILL MEET LICENSEE'S NEEDS OR EXPECTATIONS; THAT THE USE OF THE DATA WILL BE UNINTERRUPTED; OR THAT ALL NONCONFORMITIES, DEFECTS, OR ERRORS CAN OR WILL BE CORRECTED. ESRI IS NOT INVITING RELIANCE ON THIS DATA, AND THE LICENSEE SHOULD ALWAYS VERIFY ACTUAL DATA.

EXCEPT FOR THE LIMITED WARRANTY SET FORTH ABOVE, THE DATA AND RELATED MATERIALS CONTAINED THEREIN ARE PROVIDED "AS-IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Exclusive Remedy and Limitation of Liability: The entire liability of ESRI or its licensor(s) and Licensee's exclusive remedy shall be to terminate the Agreement upon Licensee returning the Data and Related Materials to ESRI with a copy of Licensee's invoice/receipt and ESRI returning the license fees paid to Licensee.

IN NO EVENT SHALL ESRI AND/OR ITS LICENSOR(S) BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOST PROFITS, LOST SALES, OR BUSINESS EXPENDITURES, INVESTMENTS, OR COMMITMENTS IN CONNECTION WITH ANY BUSINESS; LOSS OF ANY GOODWILL; OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT OR USE OF THE DATA AND RELATED MATERIALS, HOWEVER CAUSED, ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT ESRI OR ITS LICENSOR(S) HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THESE LIMITATIONS SHALL APPLY NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY EXCLUSIVE REMEDY.

Third Party Beneficiary: ESRI's licensor(s) has (have) authorized ESRI to (sub)distribute and (sub)license its (their) data as incorporated into the Data and Related Materials. As an intended third party beneficiary to this Agreement, the ESRI licensor(s) is (are) entitled to directly enforce, in its own name, the rights and obligations undertaken by the Licensee and to seek all legal and equitable remedies as are afforded to ESRI.

In the event that the data vendor(s) has (have) granted the end user permission to redistribute the Geodata, please use proper proprietary or copyright attribution for the various data vendor(s), and provide the associated metadata file(s) with the Geodata. In compliance with FGDC metadata standards, ESRI has attempted to practice proper metadata methodologies by providing any data source information, descriptions, and file names to assist in this effort.</useconst>
    <natvform Sync="TRUE">Shapefile</natvform>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Princeton University Library</cntorg>
          <cntper>Tsering Wangyal Shawa</cntper>
        </cntorgp>
        <cntvoice>609-258-6804</cntvoice>
        <cntemail>shawatw@princeton.edu</cntemail>
        <hours>8:45 a.m.&#8211;5:00 p.m. EST, Monday&#8211;Friday</hours>
      </cntinfo>
    </ptcontac>
    <browse BrowseGraphicType="Thumbnail">
      <browsed>Thumbnail</browsed>
      <browset>BMP</browset>
    </browse>
  </idinfo>
  <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>
        <cntaddr>
          <addrtype>mailing and physical address</addrtype>
          <address>Digital Map and Geospatial Information Center, The Lewis Library, Room 228, Princeton University</address>
          <city>Princeton</city>
          <state>NJ</state>
          <postal>08544</postal>
          <country>USA</country>
        </cntaddr>
        <cntorgp>
          <cntper>Tsering Wangyal Shawa</cntper>
          <cntorg>Princeton University Library</cntorg>
        </cntorgp>
        <cntvoice>609-258-6804</cntvoice>
        <cntemail>shawatw@princeton.edu</cntemail>
        <hours>8:45 a.m.&#8211;5:00 p.m. EST, Monday&#8211;Friday</hours>
      </cntinfo>
    </metc>
    <metd Sync="TRUE">20081014</metd>
    <metextns>
      <onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink>
      <metprof Sync="TRUE">ESRI Metadata Profile</metprof>
    </metextns>
  </metainfo>
  <spdoinfo>
    <direct Sync="TRUE">Vector</direct>
    <ptvctinf>
      <esriterm Name="cords">
        <efeatyp Sync="TRUE">Simple</efeatyp>
        <efeageom Sync="TRUE">Polyline</efeageom>
        <esritopo Sync="TRUE">FALSE</esritopo>
        <efeacnt Sync="TRUE">6375</efeacnt>
        <spindex Sync="TRUE">TRUE</spindex>
        <linrefer Sync="TRUE">FALSE</linrefer>
        <featdesc>Colorado Major Road</featdesc>
      </esriterm>
      <sdtsterm Name="cords">
        <sdtstype Sync="TRUE">String</sdtstype>
        <ptvctcnt Sync="TRUE">6375</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <cordsysn>
        <geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
      </cordsysn>
      <geograph>
        <geogunit Sync="TRUE">Decimal degrees</geogunit>
        <latres Sync="TRUE">0.000000</latres>
        <longres Sync="TRUE">0.000000</longres>
      </geograph>
      <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>
    </horizsys>
  </spref>
  <eainfo>
    <detailed Name="cords">
      <enttyp>
        <enttypl Sync="TRUE">cords</enttypl>
        <enttypt Sync="TRUE">Feature Class</enttypt>
        <enttypc Sync="TRUE">6375</enttypc>
        <enttypd>The lines represent the interstates, highways, and other major thoroughfares within Colorado.</enttypd>
        <enttypds>Geographic Data Technology, Inc.</enttypds>
      </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">LENGTH</attrlabl>
        <attalias Sync="TRUE">LENGTH</attalias>
        <attrtype Sync="TRUE">Number</attrtype>
        <attwidth Sync="TRUE">18</attwidth>
        <attrdef>The length of the road segment in miles based on Albers Equal Area Projection.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Calculated lengths for the features.</udom>
        </attrdomv>
        <atnumdec Sync="TRUE">4</atnumdec>
      </attr>
      <attr>
        <attrlabl Sync="TRUE">HWYNAME</attrlabl>
        <attalias Sync="TRUE">HWYNAME</attalias>
        <attrtype Sync="TRUE">String</attrtype>
        <attwidth Sync="TRUE">40</attwidth>
        <attrdef>The primary name of the road.</attrdef>
        <attrdefs>Geographic Data Technology, Inc.</attrdefs>
        <attrdomv>
          <udom>Names for the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl Sync="TRUE">FCC</attrlabl>
        <attalias Sync="TRUE">FCC</attalias>
        <attrtype Sync="TRUE">String</attrtype>
        <attwidth Sync="TRUE">3</attwidth>
        <attrdef>The Feature Classification Code of the road.</attrdef>
        <attrdefs>Department of Commerce, Census Bureau</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>Census Feature Classification Codes (also called "FCC")</codesetn>
            <codesets>Department of Commerce, Census Bureau</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl Sync="TRUE">STATEFIPS</attrlabl>
        <attalias Sync="TRUE">STATEFIPS</attalias>
        <attrtype Sync="TRUE">String</attrtype>
        <attwidth Sync="TRUE">2</attwidth>
        <attrdef>The FIPS code (two-digit number) for the state in which the road segment is located.</attrdef>
        <attrdefs>Department of Commerce, National Institute of Standards and Technology</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>Federal Information Processing Standards</codesetn>
            <codesets>National Institute of Standards and Technology</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl Sync="TRUE">ALT1_NAME</attrlabl>
        <attalias Sync="TRUE">ALT1_NAME</attalias>
        <attrtype Sync="TRUE">String</attrtype>
        <attwidth Sync="TRUE">40</attwidth>
        <attrdef>The alternate name of the road.</attrdef>
        <attrdefs>Geographic Data Technology, Inc.</attrdefs>
        <attrdomv>
          <udom>Names for the features.</udom>
        </attrdomv>
      </attr>
    </detailed>
  </eainfo>
  <dataqual>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <title>Dynamap/2000 v9.0</title>
            <origin>Geographic Data Technology, Inc.</origin>
            <pubdate>199901</pubdate>
            <edition>Version 9.0</edition>
            <geoform>vector digital data</geoform>
            <serinfo>
              <sername>Dynamap/2000&#174;</sername>
              <issue>v9.0</issue>
            </serinfo>
            <pubinfo>
              <publish>Geographic Data Technology, Inc</publish>
              <pubplace>Lebanon, New Hampshire, USA</pubplace>
            </pubinfo>
          </citeinfo>
        </srccite>
        <srcscale>100000</srcscale>
        <typesrc>CD&#8211;ROM</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>199901</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>publication date</srccurr>
        </srctime>
        <srccitea>GDT Dynamap/2000 v9.0</srccitea>
        <srccontr>Attribute and geospatial data</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>GDT maintains Highways data from its internal, master database that includes nationwide street and road network data and 1990 Census data. Technicians then begin a state-by-state editing process that includes (but is not limited to): Eliminating errant segments&#8211;Occasionally, we have discovered cases where the highway, as digitized, deviates considerably from the actual course. In these cases, GDT technicians digitize the correct segments and delete the erroneous ones.

Feature reclassification&#8211;Another drawback to TIGER-derived files was their feature classification codes (FCCs). These codes were an attempt to classify streets and roads based on maintenance, a procedure that varied dramatically in different geographic areas. To correct this problem and create a consistent nationwide highway system, GDT reclassified almost every street and road in the nation based on its use.

Highways names are applied according to a layered hierarchy. Where a highway segment has more than one name, the higher-level name will always be used, and always in this order: Interstates, then U.S. Highways, State Highways and Local Names.

The data GDT uses to define highways and ensure completeness is culled from the following sources:
&#183; Dwight D. Eisenhower System of Interstate and Defense Highways. Published by the U.S. Department of Transportation, Federal Highway Administration. Lists all interstates.
&#183; U.S. Numbered Highways. Published by the American Association of State Highway and Transportation Officers. Lists all state and U.S. highways.
&#183; State highway maps. Highway maps from state travel and tourism agencies and/or state departments of transportation.</procdesc>
        <procsv>ArcView GIS 3.x</procsv>
        <srcprod>GDT Dynamap/2000 v9.0</srcprod>
        <procdate>199901</procdate>
      </procstep>
    </lineage>
    <posacc>
      <horizpa>
        <horizpar>The geospatial part of this data set was extracted from the 1990 Census Version TIGER/Line&#8482; files (CD&#8211;ROM edition). To improve the accuracy, GDT ran a process against the entire nationwide database. The positional accuracy of this data set exceeds the positional accuracy of the TIGER/Line coordinates.

The positional accuracy of the TIGER/Line coordinates varies with the source materials used but at best meets the established National Map Accuracy standards (+/- 167 feet approximately) where 1:100,000-scale maps from the USGS are the source. The Census Bureau cannot specify the accuracy of feature updates added by its field staff or of features derived from the GBF/DIME-Files or other map sources. Thus, the level of positional accuracy in the TIGER/Line files 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.</horizpar>
      </horizpa>
    </posacc>
    <logic>No duplicate features are present.  The shapefile is exported using Avenue request ExportClean.  This request verifies and enforces the correctness of shapes.</logic>
    <complete>After processing, the data set is checked for drawing display and number of records and file sizes compared with source materials.</complete>
  </dataqual>
  <dataIdInfo>
    <envirDesc Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.1.3.679</envirDesc>
    <dataLang>
      <languageCode Sync="TRUE" value="en" />
    </dataLang>
    <idCitation>
      <resTitle Sync="TRUE">cords</resTitle>
      <presForm>
        <PresFormCd Sync="TRUE" value="005" />
      </presForm>
    </idCitation>
    <spatRpType>
      <SpatRepTypCd Sync="TRUE" value="001" />
    </spatRpType>
    <geoBox esriExtentType="native">
      <westBL Sync="TRUE">-109.0601</westBL>
      <eastBL Sync="TRUE">-102.0418</eastBL>
      <northBL Sync="TRUE">36.99252</northBL>
      <southBL Sync="TRUE">41.00234</southBL>
      <exTypeCode Sync="TRUE">1</exTypeCode>
    </geoBox>
    <geoBox esriExtentType="decdegrees">
      <westBL Sync="TRUE">-109.0601</westBL>
      <eastBL Sync="TRUE">-102.0418</eastBL>
      <northBL Sync="TRUE">36.99252</northBL>
      <southBL Sync="TRUE">41.00234</southBL>
      <exTypeCode Sync="TRUE">1</exTypeCode>
    </geoBox>
  </dataIdInfo>
  <mdLang>
    <languageCode Sync="TRUE" value="en" />
  </mdLang>
  <mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName>
  <mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer>
  <mdFileID Sync="TRUE">{1F7DDF21-BC01-4C20-8AA5-243B33ED0B1E}</mdFileID>
  <mdChar>
    <CharSetCd Sync="TRUE" value="001" />
  </mdChar>
  <mdHrLv>
    <ScopeCd Sync="TRUE" value="005" />
  </mdHrLv>
  <mdHrLvName Sync="TRUE">dataset</mdHrLvName>
  <distInfo>
    <distributor>
      <distorTran>
        <onLineSrc>
          <orDesc Sync="TRUE">002</orDesc>
          <protocol Sync="TRUE">Local Area Network</protocol>
          <linkage Sync="TRUE">file://</linkage>
        </onLineSrc>
        <tranSize Sync="TRUE">2.852</tranSize>
      </distorTran>
      <distorFormat>
        <formatName Sync="TRUE">Shapefile</formatName>
      </distorFormat>
    </distributor>
  </distInfo>
  <refSysInfo>
    <RefSystem>
      <refSysID>
        <identCode Sync="TRUE">GCS_North_American_1983</identCode>
      </refSysID>
    </RefSystem>
  </refSysInfo>
  <spatRepInfo>
    <VectSpatRep>
      <topLvl>
        <TopoLevCd Sync="TRUE" value="001" />
      </topLvl>
      <geometObjs Name="cords">
        <geoObjTyp>
          <GeoObjTypCd Sync="TRUE" value="003" />
        </geoObjTyp>
        <geoObjCnt Sync="TRUE">6375</geoObjCnt>
      </geometObjs>
    </VectSpatRep>
  </spatRepInfo>
  <mdDateSt Sync="TRUE">20081014</mdDateSt>
  <distinfo>
    <resdesc>Downloadable Data</resdesc>
  </distinfo>
</metadata>