FLORIDA NATIONAL HIGHWAY PLANNING NETWORK

Metadata also available as - [Questions & Answers]

Metadata:
Identification_Information:
Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics (BTS)
Publication_Date: 1999
Title: FLORIDA NATIONAL HIGHWAY PLANNING NETWORK
Edition: 20010000
Geospatial_Data_Presentation_Form: SHAPE
Online_Linkage: <http://www.bts.gov>
Description:
Abstract:
This dataset contains the Florida Highway Planning Network which is a comprehensive network database of Florida's principal arterial highway system and other Florida Highway System routes.
Purpose:
This dataset contains the Florida Highway Planning Network which is a comprehensive network database of Florida'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.

Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 1999
Currentness_Reference: Ground Condition
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Irregular
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Bureau of Transportation Statistics
Theme_Keyword: BTS
Theme_Keyword: Roads
Theme_Keyword: Transporation
Theme_Keyword: Planning
Place:
Place_Keyword_Thesaurus: NONE
Place_Keyword: Florida
Place_Keyword: Southeast United States
Place_Keyword: Southeast U.S
Temporal:
Temporal_Keyword_Thesaurus: NONE
Temporal_Keyword: 1970s
Temporal_Keyword: 1990s
Access_Constraints: NONE
Use_Constraints:
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>

Native_Data_Set_Environment: For more information, visit: <http://www.bts.gov>
Cross_Reference:
Citation_Information:
Originator: Bureau of Transportation Statistics (BTS)
Publication_Date: 1999
Title: Unavailable
Geospatial_Data_Presentation_Form: Map
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Relied on the integrity of the attribute information within the original data layer.
Logical_Consistency_Report:
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 "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." 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.
Completeness_Report:
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 "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics (BTS)
Publication_Date: 1999
Title: Unavailable
Geospatial_Data_Presentation_Form: Map
Source_Scale_Denominator: 1000000
Type_of_Source_Media: Map
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 1999
Source_Currentness_Reference: Ground Condition
Source_Citation_Abbreviation: BTS
Source_Contribution: Data representing roads.
Process_Step:
Process_Description:
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
Process_Date: 20000000
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.00000
False_Northing: 0.00000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.001024
Ordinate_Resolution: 0.001024
Planar_Distance_Units: METERS
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: GRS1980
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: FLNHPN.DBF
Entity_Type_Definition: Database File
Entity_Type_Definition_Source: None
Attribute:
Attribute_Label: RECTYPE
Attribute_Definition: Record type; always 'L' for line
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: VERSION
Attribute_Definition: File Version number: 02
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: REVISION
Attribute_Definition: Record Revision number: 20
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: MODDATE
Attribute_Definition: Record modification date
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: LINKID
Attribute_Definition: Unique line identification number
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: FEATUREID
Attribute_Definition: Unique line identifier
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: ANODE
Attribute_Definition:
The record in the node file (NODEID) that corresponds to the starting position of the link
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: BNODE
Attribute_Definition:
The record in the node file (NODEID) that corresponds to the ending position of the link
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: STFIPS1
Attribute_Definition: Two digit State FIPS Code
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: STFIPS2
Attribute_Definition: Two digit State FIPS Code
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: FEATURID
Attribute_Definition: Unique line identification
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SOURCE
Attribute_Definition: Original source of the coordinate information
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: STFIPS
Attribute_Definition: State FIPS Code
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: CTFIPS
Attribute_Definition: County FIPS Code
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: ORNL_ID
Attribute_Definition: Oakridge National Lab assigned link ID
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: LGURB
Attribute_Definition: Adjusted Urbanized Area
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SMURB
Attribute_Definition: Adjusted Small Urban Area
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SIGN1
Attribute_Definition: Composite field: SIGNT1, SIGNN1, SIGNQ1
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SIGN2
Attribute_Definition: Composite field: SIGNT2, SIGNN2, SIGNQ2
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SIGN3
Attribute_Definition: Composite field: SIGNT3, SIGNN3, SIGNQ3
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: MILES
Attribute_Definition: Measurement in miles
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: KM
Attribute_Definition: Measurement in kilometers
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: FACTYPE
Attribute_Definition: Permissible flow of traffic
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: TOLL
Attribute_Definition: Links which have one or more toll features
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: LANES
Attribute_Definition: Number of through lanes in both directions
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: ACONTROL
Attribute_Definition: Access control to the link from adjoining roads
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: MEDIAN
Attribute_Definition: Type of median
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SURFACE
Attribute_Definition: Predominant surface type
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: FLCASS
Attribute_Definition: Assigned functional class
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: ACLASS
Attribute_Definition: Administrative class
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: RUCODE
Attribute_Definition: Rural/Urban classification
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: STATUS
Attribute_Definition: Describes availability to through traffic
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: NHS
Attribute_Definition: Special subnetwork for the Proposed National Highway System
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: STRAHNET
Attribute_Definition: Special subnetwork for the Strategic Highway Corridor Network
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: TRANSAM
Attribute_Definition: Special subnetwork for the Trans-America corridor
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: SPECSYST
Attribute_Definition: Special FHWA Flag
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: Line name or identification
Attribute_Definition_Source: Unknown
Attribute_Domain_Values:
Unrepresentable_Domain: Unknown
Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Operator
Contact_Organization: FLORIDA GEOGRAPHIC DATA LIBRARY
Contact_Address:
Address_Type: Physical
Address:
431 Architecture Building PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Contact_Voice_Telephone: (352) 3920997, Operator
Contact_Electronic_Mail_Address: <http://www.fgdl.org/fgdldocs/document/techsupp.htm>
Hours_of_Service: 24 Hours / Day
Contact_Instructions:
Please visit the web site, <http://www.fgdl.org>, for all questions or concerns.
Distribution_Liability:
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 "MATERIALS") ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE "DATA PROVIDERS"). 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 "AS IS". 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.
Metadata_Reference_Information:
Metadata_Date: 2001
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Operator
Contact_Address:
Address_Type: Physical
Address:
Bureau of Transportation Statistics (BTS) 400 Seventh Street, SW
City: Washington
State_or_Province: DC
Postal_Code: 20590
Contact_Voice_Telephone: 1 202 366 DATA
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Generated by mp version 2.7.3 on Fri Aug 3 15:42:43 2001