FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION

TITLE: NATIONAL HIGHWAY PLANNING NETWORK IN FLORIDA - 2015

Geodataset Name:       NHPN_2015
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polyline
Feature Count:         15433
GENERAL DESCRIPTION:
This dataset contains the Florida subset of The National Highway Planning Network. The National Highway Planning Network is a comprehensive network database of the nation's major highway system. It consists of the nation's highways comprised of Rural Arterials, Urban Principal Arterials and all National Highway System routes. The nominal scale of the data set is 1:100,000 with a maximal positional error of 80 meters. This is an update to the NHPN_2014 layer.
DATA SOURCE(S):                    U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Highway Administration
SCALE OF ORIGINAL SOURCE MAPS:     100000
GEODATASET EXTENT:                 State of Florida
PUBLICATION DATE: 201505 TIME PERIOD OF CONTENT: 201505 DOWNLOAD LINK: http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: NHPN_2015.DBF
ITEM NAME WIDTH TYPE
OBJECTID
4 OID
Shape
4 Geometry
RECTYPE
1 String
VERSION
10 String
RECID
8 Double
ORIGID
8 Double
CTFIPS
2 SmallInteger
SOURCE
1 String
LGURB
8 Double
SMURB
8 Double
SIGN1
6 String
SIGNT1
1 String
SIGNN1
5 String
SIGNQ1
1 String
SIGN2
10 String
SIGNT2
1 String
SIGNN2
5 String
SIGNQ2
1 String
SIGN3
10 String
SIGNT3
1 String
SIGNN3
5 String
SIGNQ3
1 String
LNAME
30 String
MILES
8 Double
KM
8 Double
FCLASS
2 SmallInteger
RUCODE
2 SmallInteger
STATUS
2 SmallInteger
NHS
2 SmallInteger
STRAHNET
2 SmallInteger
FAC_ID
10 String
CONN_ID
10 String
CONN_DES
165 String
CONN_MILES
8 Double
LRSKEY
15 String
LRSSEQ
2 SmallInteger
BEGMP
8 Double
ENDMP
8 Double
URBAN_CODE
8 Double
BEGIN_POIN
8 Double
END_POINT
8 Double
ROUTE_ID
10 String
F_SYSTEM
2 SmallInteger
FACILITY_T
2 SmallInteger
YEAR_RECOR
2 SmallInteger
STFIPS
2 String
DESCRIPT
25 String
FGDLAQDATE
36 Date
AUTOID
4 Integer
SHAPE.LEN
0 Double

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item
Item Description
OBJECTID Internal feature number.

Shape Feature geometry.

RECTYPE Identifies arc file records.

VERSION Used for maintaining consistency across data files containing alternate releases of the NHPN. The Version Code consists of a leading Version Number (the year of release) and a trailing number (the month of release), thus, 2004.06 describes Major Release for the year 2004 and month 06

RECID A unique numeric ID associated with each arc of NHPN version 2014.05

ORIGID A unique numeric ID associated with each arc of previous versions of NHPN as appropriate

CTFIPS 3 digit FIPS code for the county the arc resides.

SOURCE Source of arc
'T' = Tiger File

'D' = Digitized

'S' = State

'U' = Unknown


LGURB 3 digit HPMS Urbanized Area code for the Urbanized Area in which the arc lies. A value of 0 indicates the arc is outside any HPMS Urbanized Areas.

SMURB 5 digit CENSUS Small Urban Area code for cities under 50,000 population in 2000. A value of 0 indicates the arc is outside any Small U

SIGN1 Contains the designated primary Sign Route for the arc

SIGNT1 Describes the type of the sign route.
'I' = Interstate

'U' = US Route

'S' = State Route

'O' = Off-Interstate Business Marker

'C' = County Route

'T' = Township

'M' = Municipal

'P' = Parkway or Forest Route Marker

'N' = None of the above


SIGNN1 Contains the actual sign route numbers . Using HPMS standards, an optional directional indicator (N, S, E, W) can also be used as part of this field

SIGNQ1 Sign Route Qualifier Record which is used to qualify the sign route description follows the Sign Route Number.
'A' = Alternate Route

'B' = Business Route

'P' = By Pass

'S' = Spur

'L' = Loop

'F' = Proposed (future)

'D' = Temporary (detour)

'T' = Truck Route

'N' = None of the above


SIGN2 Contains the designated secondary Sign Route for the arc.
(Blank) = No Qualifier, not signed, or not applicable.


SIGNT2 Describes the type of the sign route.
'I' = Interstate

'U' = US Route

'S' = State Route

'O' = Off-Interstate Business Marker

'C' = County Route

'T' = Township

'T' = Township

'M' = Municipal

'P' = Parkway or Forest Route Marker

'N' = None of the above

(blank) = Not signed or not applicable


SIGNN2 Contains the actual sign route numbers . Using HPMS standards, an optional directional indicator (N, S, E, W) can also be used as part of this field
'C' = County Route


SIGNQ2 Sign Route Qualifier Record which is used to qualify the sign route description follows the Sign Route Number.
'A' = Alternate Route

'B' = Business Route

'P' = By Pass

'S' = Spur

'L' = Loop

'F' = Proposed (future)

'D' = Temporary (detour)

'T' = Truck Route

'N' = None of the above


SIGN3 Contains the designated additional secondary Sign Route for the arc
(Blank) = No Qualifier, not signed, or not applicable.


SIGNT3 Describes the type of the sign route.
'I' = Interstate

'U' = US Route

'S' = State Route

'O' = Off-Interstate Business Marker

'C' = County Route

'T' = Township

'M' = Municipal

'P' = Parkway or Forest Route Marker

'N' = None of the above


SIGNN3 Contains the actual sign route numbers . Using HPMS standards, an optional directional indicator (N, S, E, W) can also be used as part of this field.
(blank) = Not signed or not applicable


SIGNQ3 Sign Route Qualifier Record which is used to qualify the sign route description follows the Sign Route Number
'A' = Alternate Route

'B' = Business Route

'P' = By Pass

'S' = Spur

'L' = Loop

'F' = Proposed (future)

'D' = Temporary (detour)

'T' = Truck Route

'N' = None of the above


LNAME Contains the local street name for the arc.
(Blank) = No Qualifier, not signed, or not applicable.


MILES Contains measurement in miles for the arc chain

KM Contains measurement in kilometers for the arc chain

FCLASS Identifies the assigned functional class of each arc.
01 = Rural Principal Arterial - Interstate

02 = Rural Principal Arterial - Other

06 = Rural Minor Arterial

07 = Rural Major Collector

08 = Rural Minor Collector

09 = Rural Local

11 = Urban Principal Arterial - Interstate

12 = Urban Principal Arterial-Other Freeways & Expressways

14 = Urban Principal Arterial - Other

16 = Urban Minor Arterial

17 = Urban Collector


RUCODE Describes the Rural/Urban classification of the arc.
1 = Rural

2 = Small Urban (2000 pop 5,000 -49,999)


STATUS Describes availability of the arc to through traffic.
0 = Proposed/Under construction

1 = Open to traffic


NHS Special subnetwork for the National Highway System. The following values were converted per direction from the FHWA: 2 (ISTEA High Priority Corridor) was converted to 7 (Other NHS) , 5 (ISTEA High Priority Corridor/ Non-Interstate STRAHNET) was converted to 3 (Non-Interstate STRAHNET), 6 (ISTEA High Priority Corridor/STRAHNET Connector) was converted to 4 (STRAHNET Connector)
0 = Not on NHS

1 = Interstate

3 = Non-Interstate STRAHNET

4 = STRAHNET Connector

7 = Other NHS

8 = Approved Intermodal Connector

9 = Intermodal/STRAHNET Connector


STRAHNET Special subnetwork for the Strategic Highway Corridor Network.
0 = Not on STRAHNET

1 = STRAHNET Priority 1 Connector

2 = STRAHNET Priority 2 Connector

3 = Non-Interstate STRAHNET

4 = Interstate -Designated Urban 16ft. Vertical Clearance Route

5 = Interstate -Non-Designated Urban 16ft. Vertical Clearance Route


FAC_ID FHWA designated Intermodal Facility unique ID
6 = Interstate all other


CONN_ID FHWA designated Intermodal Facility Connector unique ID
6 = Interstate all other


CONN_DES Description of Intermodal Facility Connectors or Military Installation Connectors
6 = Interstate all other


CONN_MILES Total Mileage of the designated Connector.

LRSKEY Uniquely identifies a route within a state.
6 = Interstate all other


LRSSEQ NHPN arc mile point sequence number.

BEGMP Beginning mile point for the NHPN arc segment

ENDMP Ending mile point of the NHPN arc segment.

URBAN_CODE The U.S. Census Urban Area Code.

BEGIN_POIN The point of origin for a given section of road. This value from the HPMS has been calibrated using computer algorithm during conflation process.

END_POINT The terminus point for a given section of road. This value from the HPMS has been calibrated using computer algorithm during conflation process.

ROUTE_ID The unique identifier for a given roadway (i.e., route).

F_SYSTEM the functional system upon which the section is located
1 = Rural Principal Arterial - Interstate

2 = Rural Principal Arterial - Other

6 = Rural Minor Arterial

7 = Rural Major Collector

8 = Rural Minor Collector

9 = Rural Local

11 = Urban Principal Arterial - Interstate

12 = Urban Principal Arterial - Other Freeways and Expressways

14 = Urban Principal Arterial - Other

16 = Urban Minor Arterial

17 = Urban Collector

19 = Urban Local


FACILITY_T This item is used to determine whether a roadway or structure is a one- or two-way operation. The operational characteristic of the roadway
1 = One-Way Roadway

2 = Two-Way Roadway

3 = One-Way Structure (Bridge, Tunnel, Causeway, etc.)

4 = Two-Way Structure (Bridge, Tunnel, Causeway, etc.)


YEAR_RECOR The calendar year for which the data are being reported.

STFIPS State FIPS Code

DESCRIPT GeoPlan added field based on SIGN1.

FGDLAQDATE The date GeoPlan acquired the data from the source

AUTOID Unique ID added by GeoPlan

SHAPE.LEN Length in meters


USER NOTES:
Topological relationships of node and link and uniqueness of entity IDs 
are verified by the computer algorithm developed under ArcGIS 9.1 
environment.
The complete urban principal arterial system and arterials in rural areas as reported 
to FHWA by December 1992 are inventoried in the database. Functional 
classification as reported in HPMS 2007, NHS system and intermodal 
connectors are reported to the FHWA by 2003. SIGN1, LNAME, route 
designation, route direction and route milepost as reported in HPMS 2002 are 
updated. Functional classes below arterial vary on a state-by-state basis. Any 
addition and modification to the National Highway System as reported to the 
FHWA by February 2010 is also included.
GeoPlan relied on the integrity of the attribute information within
the original data.

The primary purpose of this geospatial data set is to serve the FHWA 
needs in highway planning, policy analysis, visualization of the 
Highway Performance Monitoring System (HPMS) database and 
network modeling. The NHPN is the digital source used for coding 
and publishing the FHWA approved National Highway System maps.

The original elements of the NHPN have been conflated to the 1:100,000 
DLG-3 data set, which maintains a nominal accuracy of at least 80 meters. 
Where new roads have been added which are not in the DLG-3 database, 
link alignments have been digitized or converted from digital sources 
acquired from state DOTs with a map scale of at least 1:100,000. Where 
State data source was not available, CENSUS TIGER/Line 2000 was used.

This data is provided 'as is' and its vertical positional accuracy
has not been verified by GeoPlan

The NHPN Version 09.03 database, or any portion thereof, 
can be freely distributed as long as this metadata entry is 
included with each distribution. The original metadata entry 
cannot be modified or deleted from any data transfer.

The Florida Geographic Data Library is a collection of Geospatial Data
compiled by the University of Florida GeoPlan Center with support from
the Florida Department of Transportation. GIS data available in FGDL is
collected from various state, federal, and other agencies (data sources)
who are data stewards, producers, or publishers. The data available in
FGDL may not be the most current version of the data offered by the
data source. University of Florida GeoPlan Center makes no guarantees
about the currentness of the data and suggests that data users check
with the data source to see if more recent versions of the data exist.

Furthermore, the GIS data available in the FGDL are provided 'as is'.
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 data sources. 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
shall not be liable for any damages suffered as a result of using,
modifying, contributing or distributing the materials.

A note about data scale: 

Scale is an important factor in data usage.  Certain scale datasets
are not suitable for some project, analysis, or modeling purposes.
Please be sure you are using the best available data. 

1:24000 scale datasets 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 datasets are recommended for projects that are at the
multi-county or regional level.
1:125000 scale datasets 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 analysis. 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 webpage at:
http://geoplan.ufl.edu/education.html

REFERENCES:
Federal Highway Administration:
http://www.fhwa.dot.gov/

National Transportation Atlas Database:
http://www.bts.gov/publications/national_transportation_atlas_database/

DATA LINEAGE SUMMARY:
Conflation of NHPN V1 to DLG-3 road alignments 
using R-MATCH software developed by the Geographic 
Information Systems Group, University of Tennessee.
Process Date: 19930701

Digitizing and converting of state-supplied digital and map data. Line work geodetically controlled to match DLG-3 line work. Process Date: 19931231
Integration of conflated version of NHPN V1 and assimilated state data into a comprehensive topologically integrated network database. States edge matched and NHS attributes verified. Process Date: 19940915
Integration of supplemental state data into the NHPN V2. NHS attributes verified. Process Date: 19970115
Integration of intermodal connector links into the NHPN V2. States edge matched and NHS attributes verified. Process Date: 19980101
Attachment of a Linear Referencing System to the NHPN V2. State Data used for LRS attribute information. Integration of Ramp Group Cordon Boundary nodes into the NHPN for future addition of ramp group features. States edge matched, NHS attributes verified, and national LRSKEY added to facilitate a national route system. Process Date: 19991001
Further integration of Ramp Group Cordon Boundary nodes into the NHPN for future addition of ramp group features. States edge matched, NHS attributes verified. Process Date: 20000225
Update of Linear Referencing System to the NHPN V4.0. State data used for LRS attribute information. Process Date: 20010601
Update LRS directionality and calibrate LRS milepost attribute value to match state supplied HPMS to the NHPN V 2002.10 route system. State and FHWA HPMS-2001 data used for LRS attribute information. NHPN V.4 Route System's directionality, Route Attribute Table and milepost anchor values verified with state- submitted HPMS data elements. Anomalies are corrected or modified onto the NHPN V 2002.10 route system. Conflation of NHPN V.4 RAT data to NHPN V 2002.10 arc and calibrate arc milepost LRS anchor information using R-TAG Interface developed by the Transport Modeling and GIS-T Applications Group, Transportation & Space division, Battelle, Columbus, Ohio. Update NHS and intermodal connector links. States edge matched and NHS attributes verified. Update and integrate intermodal terminals. States geo-location matched and attributes verified. Process Date: 20020730
Update and rebuild Linear Referencing System to the NHPN V 2002.10. State data used for LRS attribute information. Process Date: 200210
Conversion of Spatial co-ordinate system from NAD 27 to NAD 83. Coverage to geodatabase conversion. Process Date: 20030601
Assigned road name attributes for arcs where SIGN values are not available. Process Date: 20030701
Corrected topological errors using ArcGIS 8.3 geodatabase topology rules. Process Date: 20030801
Transferred route information from the NHPN route to the NHPN arc features Revised and modified arc feature's topology direction with state submitted route feature and/or HPMS route direction. Process Date: 20031101
Verified arcs direction with state submitted GIS data and HPMS. Process Date: 20031201
Created new NHPN route system from the NHPN arc's embedded route information with the aid of computer algorithm developed under ArcGIS environment. Process Date: 20040101
Updated CENSUS small urban area code and HPMS urbanized area code to the arc and node features. Process Date: 20040201
Modified NHS codes as per direction of the FHWA. NHS codes 2,5, and 6 as reported in the previous versions of NHPN were changed to 7,3, and 4 respectively. Process Date: 20040301
Modified NHS based on amendments Changed STRAHNET codes 1, 2, and 3 to 6, 1 and 2 respectively. Replaced definition of codes 3, 4 and 5 as Rural Non-Designated Interstate, Urban Designated Interstate and Urban Non-Designated Interstate respectively. Process Date: 20050615
Identified and assigned status code 2 to the ferry routes. Added STRAHNET connectors and corresponding to FAC_ID and CONN_DES. Added status code as per direction of the FHWA. Status code 2 was added to identify ferry routes. Process Date: 20050701
Verified Intermodal terminals. Process Date: 20050715
In 2015 GeoPlan obtained the data from the Bureau of Transportation Statistics (BTS) in CDROM format. The data was in the following geographical coordinate system: WGS 1984 Datum, Units: Degrees. During the QA/QC process GeoPlan performed the following tasks. - Extracted features where "STFIPS" = '12' or "FIPS2" = '12' to select features in Florida - When checking 2015 metadata for date, no date was found. Opened text file associated with nhpn.shp and found date of May 2015 at the end of the text file. Checked NHPN_2014.shp to compare dates and found a publication date of June 2014. Used the May date because it is close to June and shapefile was most likely updated in May. - Original shapefile was projected in GCS_WGS_1984. Reprojected the shapefile to Albers Conical Equal Area (fgdl_square) using the WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida transformation. - Added DESCRIPT field and populated it based on "SIGN1". Changed 1770 fields with no data to say "No descript available" - Added FGDLAQDATE field and populated it based on the date GeoPlan received the data - Restructured table by reducing field lengths to better suit data - Uppercased all fields NOTE: Found that the margin of error was higher than 0.005 between 2015 and 2014 shapefiles because GeoPlan switched transformation methods in January of 2015. Tested this by transforming original 2015 data using the old transformation method and comparing it to the 2014 ETAT shapefile. Lines from the old transformation didn't match up with the 2014 data so compared it to 2013 data. 2013 data was completely different from 2014 data. Compared new data to imagery and found that the newly transformed 2015 data fit the imagery better than all other transformations. Future transformation of this data should line up with the newest transformation. Process Date: 20150915
MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:
U.S. Department of Transportation, Bureau of Transportation Statistics, Federal Highway Administration
RITA/BTS/FHWA
1200 New Jersey Ave., SE
Washington, D.C.
20590
202-366-DATA

http://www.rita.dot.gov/bts/sites/rita.dot.gov.bts/files/subject_areas/geographic_information_services/index.html answers@bts.gov Office of Geospatial Information Systems

FGDL CONTACT:
Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html