This dataset is a subset of the National Bridge Inventory for the state of Florida. The NBI is a collection of information (database) describing more than 600,000 of the Nation's bridges located on public roads including Interstate Highways, US highways, State and county roads, as well as publicly-accessible bridges on Federal lands. It presents a summary analysis of the number, location, and general condition of highway bridges within the state. This is an update to the bts_bridge_2017 layer.
To document the nation's bridge inventory.
publication date
The NBI 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.
1200 New Jersey Ave. SE
Federal Highway Administration
GeoPlan relied on the integrity of the attribute information within the original data.
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan
Spatial and Attribute Information
The GeoPlan Center took the following steps during the QA/QC process: - Downloaded the dataset from BTS on 8/23/2018 using this link: https://www.fhwa.dot.gov/bridge/nbi/disclaim.cfm?nbiYear=2017/delimited&nbiState=FL17 - This dataset was originally in the form of a text file - The text file was exported to a .csv file - The .csv was imported into ArcMap and converted to a file geodatabase table - Two fields were added to the table, LAT_DD and LONG_DD. These fields were then calculated using information from the LAT_016 and LONG_017 and the following formulas: Left( [LAT_016], 2 ) + (Mid( [LAT_016], 3, 2 )/60) + ((Mid( [LAT_016], 5, 2 ) & "." & Mid( [LAT_016], 7, 2 ))/3600) and Left( [LONG_017], 3 ) + (Mid( [LONG_017], 4, 2 )/60) + ((Mid( [LONG_017], 6, 2 ) & "." & Mid( [LONG_017], 8, 2 ))/3600) - XY locations were displayed using the information in the newly calculated LAT_DD and LONG_DD fields (the WGS 1984 geographic coordinate system was used as the coordinate system when displaying the data) - The point event layer was exported to shapefile to preserve the spatial location of the bridge data points - Dataset projected into the FGDL Albers HPGN projection using WGS_1984_(ITRF00)_To_NAD_1983 + NAD_1983_To_HARN_Florida. - NOTE: significant changes were found to locations of features. These changes were often large, exceeding a couple meters. However, upon inspection, it seemed these changes often improved the description of the physical location of the bridge. The most dramatic shift noted from prior data upon general inspection was 7071 meters - Three features were removed from the dataset because they lacked accurate spatial data - The fields FEATURES_D, FACILITY_C, and LOCATION_0 were edited to remove tick marks from the attributes. The following calculations were used: Replace( [fieldname], "'", "") Trim( [fieldname] ) - DESCRIPT field added based on a combination of the FEATURES_D, FACILITY_C, and LOCATION_0 fields. Any records with no data in the FACILITY_C field had their DESCRIPT field calculated as 'NO DESCRIPT AVAILABLE'. The formula used to create the descript field was: [FEATURES_D] & " BRIDGE" & " [" & [FACILITY_C] & " - " & [LOCATION_0] & "]" - FGDLAQDATE field added based on the date the dataset was downloaded from source. - The longest record for each field was found and field character lengths were shortened to the appropriate shortest length possible. - Uppercased fields and appropriate records in the dataset. - Layer name changed from FL17.txt to bts_bridge_jun017.shp. - After contacting the office of bridges and structures for missing field definitions a number of fields were removed as they were deemed obsolete. These fields are listed below: FED_AGENCY DATE_LAST_UPDATE TYPE_LAST_UPDATE DEDUCT_CODE REMARKS PROGRAM_CODE PROJ_NO PROJ_SUFFIX NBI_TYPE_OF_IMP DTL_TYPE_OF_IMP SPECIAL_CODE STEP_CODE STATUS_WITH_10YR_RULE SUFFICIENCY_ASTERC SUFFICIENCY_RATING STATUS_NO_10YR_RULE
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
Esri
State Code
FHWA
Structure Number
FHWA
Record Type
FHWA
Route Signing Prefix
FHWA
Designated Level of Service
FHWA
Route Number
FHWA
Directional Suffix
FHWA
Highway Agency District
FHWA
County (Parish) Code
FHWA
Place Code
FHWA
Features Intersected
FHWA
Critical Facility Indicator
FHWA
Facility Carried By Structure
FHWA
Location
FHWA
Inventory Route, Min Vertical Clearance
FHWA
Kilometerpoint
FHWA
Base Highway Network
FHWA
LRS Inventory ROute
FHWA
Subroute Number
FHWA
Latitude
FHWA
Longitude
FHWA
Bypass/Detour Length
FHWA
Toll
FHWA
Maintenance Responsibility
FHWA
Owner
FHWA
Functional Class of Inventory Route
FHWA
Year Built
FHWA
Lanes on Structure
FHWA
Lanes Under Structure
FHWA
Average Daily Traffic
FHWA
Year of Average Daily Traffic
FHWA
Design Load
FHWA
Approach Roadway Width
FHWA
Bridge Median
FHWA
Skew
FHWA
Structure Flared
FHWA
Traffic Safety Features
FHWA
Transitions
FHWA
Approach Guardrail
FHWA
Approach Guardrail Ends
FHWA
Historical Significance
FHWA
Navigation Control
FHWA
Navigation Vertical Clearance
FHWA
Navigation Horizontal Clearance
FHWA
Strucutre Open/Posted/Closed
FHWA
Type of Service on Bridge
FHWA
Type of Service Under Bridge
FHWA
Kind of Material/Design
FHWA
Type of Design/Construction
FHWA
Approach Spans, Kind of Material/Design
FHWA
Approach Spans, Type of Design/Construction
FHWA
Number of Spans in Main Unit
FHWA
Number of Approach Spans
FHWA
Inventory Rte Total Horizontal Clearance
FHWA
Length of Maximum Span
FHWA
Structure Length
FHWA
Left Curb/Sidewalk Width
FHWA
Right Curb/Sidewalk Width
FHWA
Bridge Roadway Width Curb-To-Curb
FHWA
Deck Width, Out-To-Out
FHWA
Min Vertical Clearance Over Bridge Roadway
FHWA
Minimum Vertical Underclearance Reference Feature
FHWA
Minimum Vertical Underclearance
FHWA
Min Lateral Underclear on Right, Reference Feature
FHWA
Minimum Lateral Underclearance
FHWA
Min Lateral Underclear On Left
FHWA
Deck
FHWA
Superstructure
FHWA
Substructure
FHWA
Channel/Channel Protection
FHWA
Culverts
FHWA
Method Used to Determine Operating Rating
FHWA
Operating Rating
FHWA
Method Used to Determine Inventory Rating
FHWA
Inventory Rating
FHWA
Structural Evaluation
FHWA
Deck Geometry
FHWA
Underclear, Vertical & Horizontal
FHWA
Bridge Posting
FHWA
Waterway Adequacy
FHWA
Approach Road Alignment
FHWA
Type of Work Proposed
FHWA
Work Done By
FHWA
Length of Structure Improvement
FHWA
Inspection Date
FHWA
Designated Inspection Frequency
FHWA
Fracture Critical Details
FHWA
Underwater Inspection
FHWA
Other Special Inspection
FHWA
Fracture Critical Details Date
FHWA
Underwater Inspection Date
FHWA
Other Special Inspection Date
FHWA
Bridge Improvement Cost
FHWA
Roadway Improvement Cost
FHWA
Total Project Cost
FHWA
Year Of Improvement Cost Estimate
FHWA
Neighboring State Code
FHWA
Percent Responsibility
FHWA
Border Bridge Structure Number
FHWA
STRAHNET Highway Designation
FHWA
Parallel Structure Designation
FHWA
Direction Of Traffic
FHWA
Temporary Structure Designation
FHWA
Highway System Of Inventory Route
FHWA
Federal Lands Highways
FHWA
Year Reconstructed
FHWA
Deck Structure Type
FHWA
Type of Wearing Surface
FHWA
Type of Membrane
FHWA
Deck Protection
FHWA
Average daily truck traffic
FHWA
Designated national network
FHWA
Pier/Abutment protection
FHWA
NBIS bridge length
FHWA
Scour critical bridges
FHWA
Future average daily traffic
FHWA
Year of future average daily traffic
FHWA
Minimum navigation vertical clearance vertical lift bridge
FHWA
Bridge Condition
FHWA
Condition code value that dictates the overall Bridge Condition
FHWA
Deck area as defined by the Pavement and Bridge Condition Performance Measures final rule, published in January of 2017
FHWA
Latitude Decimal Degrees
GeoPlan
Longitude Decimal Degrees
GeoPlan
Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the earth. The MGRS provides a means to represent any location on the surface of the Earth using an alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) coordinate system. The MGRS is used for the entire earth. http://mgrs-data.org/
GeoPlan
Webpage hyperlink to location in Google Maps.
GeoPlan
GeoPlan added field based on [FEATURES_D], [FACILITY_C], and [LOCATION_0]
GeoPlan
GeoPlan added field based on date acquired from source
GeoPlan
Unique ID added by GeoPlan
GeoPlan
431 Architecture PO Box 115706
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
1200 New Jersey Ave, SE