Federal Highway Administration (FHWA) 20050801 vector digital data Washington DC Federal Highway Administration (FHWA) State of Florida http://www.bts.gov/programs/geographic_information_services/ Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) 2006 vector digital data Washington DC Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) http://www.bts.gov/programs/geographic_information_services/ This dataset contains a comprehensive network database of Florida's major highway system. It consists of highways comprised of Rural Arterials, Urban Principal Arterials and all National Highway System routes. This is an update of a layer created in 2001. The data are created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. 20060430 publication date Complete As needed -87.429040 -79.872251 30.983191 24.492815 Network Highways NONE Highways Network ISO 19115 Topic Category transportation US State of Florida Florida 2005 NONE THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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 Florida Geographic Data Library (FGDL) mailing address

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 USA Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html Unclassified Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) 2006 vector digital data Washington DC Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) National Transportation Atlas Database (NTAD): http://www.bts.gov/ http://www.bts.gov/help/national_transportation_atlas_database.html http://www.bts.gov/programs/geographic_information_services/ GeoPlan relied on the integrity of the attribute information within the original data. Topological relationships of node and link and uniqueness of entity IDs are verified by the computer algorithm developed under ArcGIS 9.1 environment. Further QA/QC revealed that the NHPN version 2005.08 contains 8 polyline features (RECIDs 4000057, 4000855, 41000287, 41002220, 48000952, 72001074, 72001170, and 72001488) that are each defined by more than 500 shape points. These features will not import correctly into the workstation version of ArcInfo, which has a 500 shapepoint limit. When importing into the workstation version of ArcInfo, the 8 features will be automatically split into 2 features each. As part of this process, attributes are simply duplicated on the split features. Because of this, attributes such as MILES and KM become invalid for these features. 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 2002, 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 2005 is also included. 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 Federal Highway Administration (FHWA) 20050801 vector digital data http://www.fgdl.org 100000 19920701 NHWA Spatial and Attribute Information 1978 DLG-3 Spatial and Attribute Information 19921231 State Data Spatial and Attribute Information 19931101 State Data Spatial and Attribute Information 19931101 State Data Spatial and Attribute Information 1994 TIGER Spatial and Attribute Information 2000 TIGER Spatial and Attribute Information 2002 State Data Spatial and Attribute Information State 2005 State Data 2003 Spatial and Attribute Information 20021001 publication date NHPN 2002.10 Spatial and Attribute Information State 2003 HPMS 2002 Spatial and Attribute Information Transport Modeling and GIS-T Application Group, Transportation & Space division, Battelle 2003 Urban Area 2003 Spatial and Attribute Information 2003 NHPN Geo 2003 Spatial and Attribute Information 2005 STRAHNET connectors Spatial and Attribute Information 2005 FHWA Intermodal Facility and Connectors Spatial and Attribute Information Conflation of NHPN V1 to DLG-3 road alignments using R-MATCH software developed by the Geographic Information Systems Group, University of Tennessee. NHPN V1 DLG-3 19930701 Digitizing and converting of state-supplied digital and map data. Line work geodetically controlled to match DLG-3 line work. State Data DLG-3 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. 19940915 Integration of supplemental state data into the NHPN V2. NHS attributes verified. 19970115 Integration of intermodal connector links into the NHPN V2. States edge matched and NHS attributes verified. 19980101 Attachment of a Linear Referencing System to the NHPN V2. State Data used for LRS attribute information. 19991001 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. 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. 20000225 Update of Linear Referencing System to the NHPN V4.0. State data used for LRS attribute information. 20010601 Update and rebuild Linear Referencing System to the NHPN V 2002.10. State data used for LRS attribute information. 20020730 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. 20020730 Update NHS and intermodal connector links. States edge matched and NHS attributes verified. 20020730 Update and integrate intermodal terminals. States geo-location matched and attributes verified. 20020730 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. 20020730 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. 20020730 Coverage to geodatabase conversion. NHPN 2002.10 20030601 NHPN Geo 2003 Conversion of Spatial co-ordinate system from NAD 27 to NAD 83. NHPN Geo 2003 20030601 Assigned road name attributes for arcs where SIGN values are not available. State Data 2003 CENSUS/TIGER/Line 2000 20030701 Corrected topological errors using ArcGIS 8.3 geodatabase topology rules. NHPN Geo 2003 20030801 Transferred route information from the NHPN route to the NHPN arc features NHPN Geo 2003 20031001 Revised and modified arc feature's topology direction with state submitted route feature and/or HPMS route direction. State Data 2003 State Data 2002 HPMS 2002 20031101 Verified arcs direction with state submitted GIS data and HPMS. State Data 2003 State Data 2002 HPMS 2002 20031201 Created new NHPN route system from the NHPN arc's embedded route information with the aid of computer algorithm developed under ArcGIS environment. NHPN Geo 2003 20040101 Updated CENSUS small urban area code and HPMS urbanized area code to the arc and node features. Urban Area 2003 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. NHPN Geo 2003 20040301 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. NHPN 2004.10 20050615 Added STRAHNET connectors and corresponding to FAC_ID and CONN_DES. STRAHNET Connectors 20050701 Verified Intermodal terminals. 20050715 Modified NHS based on ammendments 20050615 Added status code as per direction of the FHWA. Status code 2 was added to identify ferry routes. 20050701 Identified and assigned status code 2 to the ferry routes. NHPN 2004.10 20050701 Geoplan, during the QA/QC process included the following aspects: 1.) Clipped to the state of Florida 2.) Projected data to FGDL Alvers HPGN 3.) DESCRIPT item added based on Sign1 4.) FGDLAQDATE item added to attribute table 5.) Upcased all records in attribute table 20060906 Metadata imported. Q:\finaldata\state\pre_load\ntad\nhpn_2006.shp.xml Vector String 176191 Network chain, nonplanar graph 176124 Node, network 138902 Albers Conical Equal Area 24.000000 31.500000 -84.000000 24.000000 400000.000000 0.000000 coordinate pair 0.002048 0.002048 meters D_North_American_1983_HARN Geodetic Reference System 80 6378137.000000 298.257222 0.001000 Explicit elevation coordinate included with horizontal coordinates NHPN_2005 NHPN_2005.DBF FHWA OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. RECTYPE Identifies arc file records. FHWA "L" FHWA 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. FHWA Character set RECID A unique numeric ID associated with each arc of NHPN version 2004.06. FHWA Positive Integers. ORIGID A unique numeric ID associated with each arc of previous versions of NHPN as appropriate. FHWA Positive Integers. FNRECID Identifies a node in the nhpnnod shapefile that corresponds to the starting position of the arc chain. FHWA Numeric Value TNRECID Identifies a node in the nhpnnod shapefile that corresponds to the ending position of the arc chain. FHWA Numeric Value CTFIPS 3 digit FIPS code for the county the arc resides. Federal Information Processing Standards Federal Information Processing Standard, Publication 6-4 National Institute for Standards and Technology (NIST) SOURCE Source of arc FHWA '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. Highway Performance Monitoring System 2001 00 999 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 Urban Area. CENSUS 2000 00 99999 SIGN1 Contains the designated primary Sign Route for the arc. FHWA The character string is composed of three sub fields SIGNT1, SIGNN1, and SIGNQ1. SIGNT1 Describes the type of the sign route. FHWA '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 (blank) Not signed or not applicable 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. FHWA Alpha Numeric SIGNQ1 Sign Route Qualifier Record which is used to qualify the sign route description follows the Sign Route Number. FHWA 'A' Alternate Route FHWA 'B' Business Route 'P' By Pass 'S' Spur 'L' Loop 'F' Proposed (future) 'D' Temporary (detour) 'T' Truck Route 'N' None of the above (Blank) No Qualifier, not signed, or not applicable. SIGN2 Contains the designated secondary Sign Route for the arc. FHWA The character string is composed of three sub fields SIGNT2, SIGNN2, and SIGNQ2. SIGNT2 Describes the type of the sign route. FHWA 'I' Interstate FHWA '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 (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. FHWA Alpha Numeric SIGNQ2 Sign Route Qualifier Record which is used to qualify the sign route description follows the Sign Route Number. FHWA 'A' Alternate Route FHWA 'B' Business Route 'P' By Pass 'S' Spur 'L' Loop 'F' Proposed (future) 'D' Temporary (detour) 'T' Truck Route 'N' None of the above (Blank) No Qualifier, not signed, or not applicable. SIGN3 Contains the designated additional secondary Sign Route for the arc. FHWA The character string is composed of three sub fields SIGNT3, SIGNN3, and SIGNQ3. SIGNT3 Describes the type of the sign route. FHWA 'I' Interstate FHWA '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 (blank) Not signed or not applicable 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. FHWA Alpha Numeric MILES Contains measurement in miles for the arc chain. FHWA Positive Integers KM Contains measurement in kilometers for the arc chain. FHWA Positive Integers FCLASS Identifies the assigned functional class of each arc. Original functional classification codes came from data sources submitted as part of 1992 Functional Reclassification by State agencies. For segments on the National Highway System this attribute has been quality controlled against the 2002 HPMS. 01 Rural Principal Arterial - Interstate FHWA 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 19 Urban Local RUCODE Describes the Rural/Urban classification of the arc. FHWA 1 Rural FHWA 2 Small Urban (2000 pop 5,000 -49,999) 3 Large Urban (2000 pop >= 50,000) STATUS Describes availability of the arc to through traffic. FHWA 0 Proposed/Under construction FHWA 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). FHWA 0 Not on NHS FHWA 1 Interstate 3 Non-Interstate STRAHNET 4 STRAHNET Connector 7 Other NHS 8 Approved Intermodal Connector STRAHNET Special subnetwork for the Strategic Highway Corridor Network. FHWA 0 Not on STRAHNET FHWA 1 Non-Interstate STRAHNET 2 STRAHNET Priority 1 Connector 3 STRAHNET Priority 2 Connector 4 STRAHNET Priority 3 Connector 5 Temporary STRAHNET Route CONN_MILES Total Mileage of the designated Connector. Federal Highway Administration 00 99 LRSKEY Uniquely identifies a route within a state. Highway Performance Monitoring System Created by combining 2 data items from the HPMS: the 12 character LRS Identification field (HPMS Data Item 10) plus the 3 character County FIPS Code (HPMS Data Item 4). LRSSEQ NHPN arc mile point sequence number. FHWA Alpha-Numeric character set (A-Z, 0-99) FHWA BEGMP Beginning mile point for the NHPN arc segment. FHWA 00 99 ENDMP Ending mile point of the NHPN arc segment. FHWA 00 99 AADT The Annual Average Daily Traffic field comes from the 2002 Highway Performance Monitoring System. FHWA Numeric Value THRULANES The Number of through lanes field indicates the number of striped lanes in both directions. This field does not include auxiliary lanes, such as collector-distributor lanes, weaving lanes, frontage road lanes, parking and turning lanes, acceleration/deceleration lanes, toll collection lanes and truck climbing lanes. FHWA: HPMS Numeric Value OWNERSHIP Identifies the road owner FHWA: HPMS 1 State Highway Agency FHWA: HPMS 2 County Highway Agency FHWA: HPMS 3 Town or Township Highway Agency FHWA: HPMS 4 Municipal Highway Agency FHWA: HPMS 5 Other State Agency FHWA: HPMS 6 Other Local Agency FHWA: HPMS 7 Federal Agency FHWA: HPMS 8 Other FHWA: HPMS STFIPS State FIPS Code FHWA Federal Information Processing Standard- FIPS Pub 6-4 National Institute for Standards and Technology (NIST) BTSVERSION Version of the database RITA/BTS 00 99 DESCRIPT Based on 'SIGN1' Geoplan FGDLAQDATE Date FGDL acquired data from source Geoplan SHAPE Feature geometry. ESRI Coordinates defining the features. AUTOID Unique ID added by GeoPlan SHAPE.LEN Florida Geographic Data Library (FGDL) mailing address

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 United States Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html DOWNLOADABLE DATA 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. ESRI Shapefile 2006 No compression applied. However, if using digital transfer online option, note access instructions. 145.986 Due to a significant reduction in resources, the NTAD is no longer available for download. The NTAD cdrom can be ordered from the online bookstore at www.bts.gov. If resources allow, download applications will be restored. When the applications become available, they will be found at www.bts.gov/programs/geographic_information_services. CD-ROM ISO 9660 None Call (202-366-DATA), fax (202-366-3640), or E-mail (answers@bts.gov) RITA/BTS to request the National Transportation Atlas Databases (NTAD) 2006 CD-ROM. This and other RITA/BTS products may be ordered from the RITA/BTS Internet site (<http://www.bts.gov/programs/geographic_information_services/>). This data is intended for use with a Geographic Information Systems or Remote Sensing software package. 2006 20060413 Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) Geospatial Information Program mailing address

400 7th Street, SW Room 4117

Washington DC 20590 USA 202-366-DATA 202-366-3640 answers@bts.gov FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile