<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="./fgdc_classic_fgdl.xsl"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">

<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Bureau of Transportation Statistics (BTS)</origin>
<pubdate>1999</pubdate>
<title>FLORIDA NATIONAL HIGHWAY PLANNING NETWORK</title>
<edition>20010000</edition>
<geoform>SHAPE</geoform>
<onlink>http://www.bts.gov</onlink>
</citeinfo>
</citation>
<descript>
<abstract>
This dataset contains the Florida Highway Planning Network which is a
comprehensive network database of Florida&apos;s principal arterial highway
system and other Florida Highway System routes.
</abstract>
<purpose>
This dataset contains the Florida Highway Planning Network which is a
comprehensive network database of Florida&apos;s principal arterial highway
system and other Florida Highway System routes.  For more information
consider the following resources:

National Highway Planning Network V1.1, Bruce Peterson, Oak Ridge National
Laboratory, 1992.

USGS Digital Line Graph (DLG-3) Series, 1978, Road alignments
for rural and urban highways.
</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>1999</caldate>
</sngdate>
</timeinfo>
<current>Ground Condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Irregular</update>
</status>
<spdom>
<bounding>
<westbc>-87.429040</westbc>
<eastbc>-79.872251</eastbc>
<northbc>30.983191</northbc>
<southbc>24.492815</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>NONE</themekt>
<themekey>Bureau of Transportation Statistics</themekey>
<themekey>BTS</themekey>
<themekey>Roads</themekey>
<themekey>Transporation</themekey>
<themekey>Planning</themekey>
</theme>
<place>
<placekt>NONE</placekt>
<placekey>Florida</placekey>
<placekey>Southeast United States</placekey>
<placekey>Southeast U.S</placekey>
</place>
<temporal>
<tempkt>NONE</tempkt>
<tempkey>1970s</tempkey>
<tempkey>1990s</tempkey>
</temporal>
</keywords>
<accconst>NONE</accconst>
<useconst>
THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING.

Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale data sets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries.

1:100000 scale data sets are recommended for projects that are at the multi-county or regional level.  1:250000 scale data sets are recommended for projects that are at the regional or state level or larger.

Vector datasets with no defined scale or accuracy should be considered
suspect. Make sure you are familiar with your data before using it for
projects or analyses. Every effort has been made to supply the user with
data documentation. For additional information, see the References section
and the Data Source Contact section of this documentation. For more
information regarding scale and accuracy, see our web pages at:

http://www.geoplan.ufl.edu/education.html
</useconst>
<native>For more information, visit: http://www.bts.gov</native>
<crossref>
<citeinfo>
<origin>Bureau of Transportation Statistics (BTS)</origin>
<pubdate>1999</pubdate>
<title>Unavailable</title>
<geoform>Map</geoform>
</citeinfo>
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>Relied on the integrity of the attribute information within the original data layer.</attraccr>
</attracc>
<logic>
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file.  All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly.  This process is documented in the Process_Step.)  Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates.  All internal polygons are tested for closure.  Certain attributes and/or entities, e.g. closure line, convey data quality information.  When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of &quot;9s&quot;; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of &quot;9s.&quot;
In addition, the following elements were considered:
(1) Conflation of NHPN V1 to DLG-3 road alignments using R-MATCH software developed by the Geographic Information Systems Group, University of Tennesse.
(2) Digitizing and conversion of state supplied digital and map data. Line work geodetically controlled to match DLG-3 line work.
(3) Integration of conflated version of NHPN V1 and assimilated State Data into a comprehensive topologically integrated network database. States edgematched and NHSattributes verified.
(4) Integration of supplemental State Data into the NHPN V2. NHS attributes verified.
(5) Integration of supplemental State data used for LRS attribute information.
(6) Integration of intermodal connector links into the NHPN V2. States edgematched and NHS attributes verified.
</logic>
<complete>Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file.  All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly.  This process is documented in the Process_Step.)  Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates.  All internal polygons are tested for closure.  Certain attributes and/or entities, e.g. closure line, convey data quality information.  When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of &quot;9s&quot;; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of &quot;9s.&quot;</complete>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Bureau of Transportation Statistics (BTS)</origin>
<pubdate>1999</pubdate>
<title>Unavailable</title>
<geoform>Map</geoform>
</citeinfo>
</srccite>
<srcscale>1000000</srcscale>
<typesrc>Map</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1999</caldate>
</sngdate>
</timeinfo>
<srccurr>Ground Condition</srccurr>
</srctime>
<srccitea>BTS</srccitea>
<srccontr>Data representing roads.</srccontr>
</srcinfo>
<procstep>
<procdesc>
The process step describes, in general, the process used in the production of data sets.  The originating agencies created the original spatial coverage.  GeoPlan, during the QA/QC process included the following aspects:
(1) Reprojected data to FGDL Albers
(2) Set Precision to DOUBLE
(3) Set Tolerances to FGDL Standards.
(4) Moved DESCRIPT item to the end of table
(5) Dropped item featureid (repeat of featureid)
(6) Joined related attribute tables from National Transporation Atlas Database CD-ROM
</procdesc>
<procdate>20000000</procdate>
</procstep>
</lineage>
</dataqual>
<spref>
<horizsys>
<planar>
<mapproj>
<mapprojn>Albers Conical Equal Area</mapprojn>
<albers>
<stdparll>24.000000</stdparll>
<stdparll>31.500000</stdparll>
<longcm>-84.000000</longcm>
<latprjo>24.000000</latprjo>
<feast>400000.00000</feast>
<fnorth>0.00000</fnorth>
</albers>
</mapproj>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.001024</absres>
<ordres>0.001024</ordres>
</coordrep>
<plandu>METERS</plandu>
</planci>
</planar>
<geodetic>
<horizdn>HPGN</horizdn>
<ellips>GRS1980</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>FLNHPN.DBF</enttypl>
<enttypd>Database File</enttypd>
<enttypds>None</enttypds>
</enttyp>
<attr>
<attrlabl>RECTYPE</attrlabl>
<attrdef>Record type; always &apos;L&apos; for line</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>VERSION</attrlabl>
<attrdef>File Version number: 02</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>REVISION</attrlabl>
<attrdef>Record Revision number: 20</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>MODDATE</attrlabl>
<attrdef>Record modification date</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LINKID</attrlabl>
<attrdef>Unique line identification number</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FEATUREID</attrlabl>
<attrdef>Unique line identifier</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ANODE</attrlabl>
<attrdef>The record in the node file (NODEID) that corresponds to the starting position of the link</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>BNODE</attrlabl>
<attrdef>The record in the node file (NODEID) that corresponds to the ending position of the link</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STFIPS1</attrlabl>
<attrdef>Two digit State FIPS Code</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STFIPS2</attrlabl>
<attrdef>Two digit State FIPS Code</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FEATURID</attrlabl>
<attrdef>Unique line identification</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SOURCE</attrlabl>
<attrdef>Original source of the coordinate information</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STFIPS</attrlabl>
<attrdef>State FIPS Code</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>CTFIPS</attrlabl>
<attrdef>County FIPS Code</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ORNL_ID</attrlabl>
<attrdef>Oakridge National Lab assigned link ID</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LGURB</attrlabl>
<attrdef>Adjusted Urbanized Area</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SMURB</attrlabl>
<attrdef>Adjusted Small Urban Area</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SIGN1</attrlabl>
<attrdef>Composite field: SIGNT1, SIGNN1, SIGNQ1</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SIGN2</attrlabl>
<attrdef>Composite field: SIGNT2, SIGNN2, SIGNQ2</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SIGN3</attrlabl>
<attrdef>Composite field: SIGNT3, SIGNN3, SIGNQ3</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>MILES</attrlabl>
<attrdef>Measurement in miles</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>KM</attrlabl>
<attrdef>Measurement in kilometers</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FACTYPE</attrlabl>
<attrdef>Permissible flow of traffic</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>TOLL</attrlabl>
<attrdef>Links which have one or more toll features</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LANES</attrlabl>
<attrdef>Number of through lanes in both directions</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ACONTROL</attrlabl>
<attrdef>Access control to the link from adjoining roads</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>MEDIAN</attrlabl>
<attrdef>Type of median</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SURFACE</attrlabl>
<attrdef>Predominant surface type</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>FLCASS</attrlabl>
<attrdef>Assigned functional class</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ACLASS</attrlabl>
<attrdef>Administrative class</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>RUCODE</attrlabl>
<attrdef>Rural/Urban classification</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STATUS</attrlabl>
<attrdef>Describes availability to through traffic</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>NHS</attrlabl>
<attrdef>Special subnetwork for the Proposed National Highway System</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>STRAHNET</attrlabl>
<attrdef>Special subnetwork for the Strategic Highway Corridor Network</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>TRANSAM</attrlabl>
<attrdef>Special subnetwork for the Trans-America corridor</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SPECSYST</attrlabl>
<attrdef>Special FHWA Flag</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>DESCRIPT</attrlabl>
<attrdef>Line name or identification</attrdef>
<attrdefs>Unknown</attrdefs>
<attrdomv>
<udom>Unknown</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntperp>
<cntper>Operator</cntper>
<cntorg>FLORIDA GEOGRAPHIC DATA LIBRARY</cntorg>
</cntperp>
<cntaddr>
<addrtype>Physical</addrtype>
<address>
431 Architecture Building
PO Box 115706
</address>
<city>Gainesville</city>
<state>Florida</state>
<postal>32611-5706</postal>
</cntaddr>
<cntvoice>(352) 3920997, Operator</cntvoice>
<cntemail>http://www.fgdl.org/fgdldocs/document/techsupp.htm</cntemail>
<hours>24 Hours / Day</hours>
<cntinst>
Please visit the web site, http://www.fgdl.org, for all
questions or concerns.
</cntinst>
</cntinfo>
</distrib>
<distliab>Florida Geographic Data Library is a product of the University of Florida GeoPlan Center with support from the Florida Department of Transportation and the Florida Department of Environmental Protection. THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE &quot;MATERIALS&quot;) ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE &quot;DATA PROVIDERS&quot;). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED &quot;AS IS&quot;. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS.</distliab>
</distinfo>
<metainfo>
<metd>2001</metd>
<metc>
<cntinfo>
<cntperp>
<cntper>Operator</cntper>
</cntperp>
<cntaddr>
<addrtype>Physical</addrtype>
<address>
Bureau of Transportation Statistics (BTS)
400 Seventh Street, SW
</address>
<city>Washington</city>
<state>DC</state>
<postal>20590</postal>
</cntaddr>
<cntvoice>1 202 366 DATA</cntvoice>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
</metainfo>
</metadata>
