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) ·
54175 (1) ·
55380 (1) ·
55385 (1) ·
58725 (1) ·
Boca Raton (1) ·
Boynton Beach (1) ·
Cape Canaveral (1) ·
Delray Beach (1) ·
Fort Pierce (1) ·
Hypoluxo (1) ·
Jupiter (1) ·
Merritt Island (1) ·
Palm Bay (1) ·
Palm Beach Gardens (1) ·
Palm Shores (1) ·
Port Malabar (1) ·
Royal Palm Beach village (1) ·
Sebastian (1) ·
Vero Beach (1) ·
Viera (1) ·
Wellington village (1) ·
West Palm Beach (1)
Route 005d:
Direction 005e:
Features 006a:
'Banana River ' (1) ·
'Banana River Relief East' (1) ·
'Banana River Relief West' (1) ·
'BOYNTON CANAL ' (1) ·
'C-51 CANAL ' (1) ·
'C. Stanley Weaver Canal ' (1) ·
'COLLIER CREEK ' (1) ·
'CR-3 ' (1) ·
'CYPRESS CREEK ' (1) ·
'DANFORTH CREEK ' (1) ·
'DIRT FARM ROAD ' (1) ·
'EL RIO CANAL ' (1) ·
'F.E.C. Railroad ' (1) ·
'Indian River ' (1) ·
'Indian River Relief East' (1) ·
'Indian River West Relief' (1) ·
'Intracoastal Waterway ' (1) ·
'Jupiter Creek ' (1) ·
'L-38 CANAL ' (1) ·
'Lake Gertie ' (1) ·
'Long Creek ' (1) ·
'LWDD E-3 CANAL ' (1) ·
'LWDD E-4 CANAL ' (1) ·
'M-1 CANAL ' (1) ·
'Main Canal ' (1) ·
'N. Fork St. Lucie River ' (1) ·
'QUAIL COVEY ROAD ' (1) ·
'RCA CANAL ' (1) ·
'S Fork St. Lucie River ' (1) ·
'SR 70 ' (1) ·
'SR-3 ' (1) ·
'SR-401 ' (1) ·
'SR-404 ' (1) ·
'SR-91 Turnpike ' (1) ·
'St. Johns River ' (1) ·
'Sykes Creek ' (1) ·
'WARNER CREEK ' (1) ·
Canal (1) ·
Tillman Canal (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027: (Click arrow to add another value)
Traffic 029:
10000 (1) ·
11300 (1) ·
1202 (1) ·
12250 (1) ·
15500 (1) ·
15813 (1) ·
17250 (1) ·
17300 (1) ·
19500 (1) ·
2000 (1) ·
20000 (1) ·
20150 (1) ·
20500 (1) ·
21000 (1) ·
22500 (1) ·
23000 (1) ·
25000 (1) ·
29250 (1) ·
29500 (1) ·
3000 (1) ·
3100 (1) ·
32750 (1) ·
33000 (1) ·
34000 (1) ·
44000 (1) ·
48500 (1) ·
5400 (1) ·
6193 (1) ·
6400 (1) ·
6540 (1) ·
6724 (1) ·
6900 (1) ·
8950 (1) ·
978 (1)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
Width 052:
Deck 058:
Superstructure 059:
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 being eroded. River control devices and/or embankment have major damage. Trees and brush restrict the channel. (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) ·
Bridge closed because of channel failure. Corrective action may put back in light service. (1) ·
N/A (1)
Culvert 062:
N/A (1) ·
Shrinkage cracks, light scaling and insignificant spalling which does not expose reinforcing steel. Insignificant damage caused by drift with no misalignment and not requiring corrective action. Some minor scouring has occured near curtain walls, wingwalls or pipes. Metal culverts have a smooth symmetrical curvature with superficial corrosion and no pitting. (1)
Inspect Date 090: (Click arrow to add another value)
Direction 102:
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 assessed or calculated scour condition. Scour is determined to be within the limits of footing or piles by assessment, 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 foundations determined to be stable for the assessed or calculated scour condition. Scour is determined to be above top of footing by assessment, 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:
1174 (1) ·
11972 (1) ·
12000 (1) ·
1390 (1) ·
15528 (1) ·
19134 (1) ·
19606 (1) ·
21254 (1) ·
26893 (1) ·
29929 (1) ·
3000 (1) ·
30015 (1) ·
33832 (1) ·
34700 (1) ·
34960 (1) ·
35568 (1) ·
3600 (1) ·
36435 (1) ·
39038 (1) ·
39905 (1) ·
43375 (1) ·
50749 (1) ·
51182 (1) ·
5378 (1) ·
56821 (1) ·
57255 (1) ·
58990 (1) ·
7000 (1) ·
7157 (1) ·
76340 (1) ·
7800 (1) ·
8175 (1) ·
84148 (1) ·
9369 (1)
Clearance 116:
Showing below up to 55 results in range #1 to #55.
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
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
