Drilldown: bridge data
From Indian River Lagoon Project
Choose a table:
- Event (169)
- News Link (111)
- Organization (18)
- Waterbody (27)
- bridge (13)
- bridge data (1468)
- definition (254)
- fips (487)
- repository (98)
- timeline (19)
- weblink (123)
Use the filters below to narrow your results.
ObjectID:
County 003:
Place 004:
None (1) ·
30975 (1) ·
54175 (1) ·
55385 (1) ·
58725 (1) ·
74625 (1) ·
77275 (1) ·
Belle Glade (1) ·
Boca Raton (1) ·
Boynton Beach (1) ·
Cape Canaveral (1) ·
Cocoa (1) ·
Delray Beach (1) ·
Fort Pierce (1) ·
Greenacres City (1) ·
Indialantic (1) ·
Lantana (1) ·
Melbourne (1) ·
Merritt Island (1) ·
New Smyrna Beach (1) ·
North Palm Beach village (1) ·
Port Orange (1) ·
Sebastian (1) ·
Titusville (1) ·
Vero Beach (1) ·
West Palm Beach (1)
Route 005d:
Features 006a:
'Banana River ' (1) ·
'Banana River Relief East' (1) ·
'Barge Canal ' (1) ·
'BESSEY CREEK ' (1) ·
'CANAL E-4 ' (1) ·
'City St. & Crane Creek ' (1) ·
'CR-515 & Indian River ' (1) ·
'ELKCAM WATERWAY ' (1) ·
'FEC Railroad ' (1) ·
'FECRR ' (1) ·
'GARDEN CANAL ' (1) ·
'Halifax River ' (1) ·
'HILLSBORO L-14 CANAL ' (1) ·
'I 95 and SR 704 ' (1) ·
'I-4 ' (1) ·
'Indian River ' (1) ·
'INTRACOASTAL WATERWAY ' (1) ·
'IWW Indian River ' (1) ·
'JOANN CANAL ' (1) ·
'LAKE IDA CANAL ' (1) ·
'LAT CANAL (LK WORTH INT)' (1) ·
'LATERAL A CANAL ' (1) ·
'LATERAL CANAL ' (1) ·
'LOXAHATCHEE WPB CANAL ' (1) ·
'LWDD LAT CANAL 17 ' (1) ·
'NORTH CANAL ' (1) ·
'OKEECHOBEE RIM CANAL ' (1) ·
'PHIPP CANAL ' (1) ·
'RANGE LINE CANAL ' (1) ·
'RIM DITCH CANAL C-24 ' (1) ·
'S Fork St. Lucie River ' (1) ·
'SEBASTIAN RIVER PRONG ' (1) ·
'Service Rd & Canal ' (1) ·
'SR 91 TPK ' (1) ·
'SR 91 TPK (STUART INT) ' (1) ·
'SR-513 ' (1) ·
'St. Lucie Canal ' (1) ·
'Tide Relief Canal ' (1) ·
'Turkey Creek ' (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
1935 (1) ·
1936 (1) ·
1952 (1) ·
1955 (1) ·
1956 (1) ·
1957 (1) ·
1958 (1) ·
1959 (1) ·
1961 (1) ·
1962 (1) ·
1963 (1) ·
1964 (1) ·
1965 (1) ·
1967 (1) ·
1969 (1) ·
1970 (1) ·
1971 (1) ·
1972 (1) ·
1981 (1) ·
1985 (1) ·
1987 (1) ·
1990 (1) ·
1994 (1) ·
1997 (1) ·
1999 (1) ·
2001 (1) ·
2003 (1) ·
2006 (1)
Lanes 028a: (Click arrow to add another value)
Traffic 029:
101 (1) ·
10200 (1) ·
10502 (1) ·
11500 (1) ·
1260 (1) ·
13300 (1) ·
134 (1) ·
14500 (1) ·
1550 (1) ·
15800 (1) ·
19500 (1) ·
20300 (1) ·
20500 (1) ·
21000 (1) ·
22500 (1) ·
24317 (1) ·
250 (1) ·
25000 (1) ·
25474 (1) ·
26500 (1) ·
30500 (1) ·
35500 (1) ·
36000 (1) ·
400 (1) ·
4050 (1) ·
44400 (1) ·
46600 (1) ·
5900 (1) ·
6363 (1) ·
6480 (1) ·
68700 (1) ·
6960 (1) ·
7400 (1) ·
8250 (1) ·
8950 (1) ·
9200 (1) ·
936 (1) ·
9700 (1)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
104 (1) ·
1169 (1) ·
117 (1) ·
136 (1) ·
14 (1) ·
143 (1) ·
148 (1) ·
153 (1) ·
18 (1) ·
19 (1) ·
229 (1) ·
23 (1) ·
24 (1) ·
263 (1) ·
27 (1) ·
276 (1) ·
32 (1) ·
341 (1) ·
36 (1) ·
38 (1) ·
39 (1) ·
397 (1) ·
412 (1) ·
424 (1) ·
47 (1) ·
50 (1) ·
51 (1) ·
53 (1) ·
563 (1) ·
58 (1) ·
68 (1) ·
709 (1) ·
90 (1) ·
91 (1) ·
92 (1) ·
96 (1)
Width 052:
Deck 058:
Superstructure 059: (Click arrow to add another value)
Substructure 060:
Channel 061:
Bank is beginning to slump. River control devices and embankment protection have widespread minor damage. There is minor stream bed movement evident. Debris is restricting the channel slightly. (1) ·
Bank protection is in need of minor repairs. River control devices and embankment protection have a little minor damage. Banks and/or channel have minor amounts of drift. (1) ·
Banks are protected or well vegetated. River control devices such as spur dikes and embankment protection are not required or are in a stable condition. (1) ·
N/A (1) ·
No noticeable or noteworthy deficiencies which affect the condition of the channel. (1)
Culvert 062:
Inspect Date 090: (Click arrow to add another value)
Direction 102:
Rebuilt 106:
Deck Type 107:
Scour 113:
Bridge foundations determined to be stable for assessed or calculated scour condition. Scour is determined to be within the limits of footing or piles (Example B) by assessment (i.e.,bridge foundations are on rock formations that have been determined to resist scour within the service life of the bridge), by calculations or by installation of properly designed countermeasures (1) ·
Bridge foundations determined to be stable for the assessed or calculated scour condition. Scour is determined to be above top of footing (Example A) by assessment (i.e., bridge foundations are on rock formations that have been determined to resist scour within the service life of the bridge4), by calculation or by installation of properly designed countermeasures (1) ·
Bridge is scour critical; bridge foundations determined to be unstable for assessed or calculated scour conditions: Scour within limits of footing or piles. Scour below spread-footing base or pile tips. (1) ·
Bridge not over waterway. (1) ·
Countermeasures have been installed to mitigate an existing problem with scour and to reduce the risk of bridge failure during a flood event. Instructions contained in a plan of action have been implemented to reduce the risk to users from a bridge failure during or immediately after a flood event. (1)
Future 114:
Clearance 116:
Showing below up to 49 results in range #1 to #49.
View (previous 250 | next 250) (20 | 50 | 100 | 250 | 500)
T
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
