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:
None (1) ·
24350 (1) ·
30975 (1) ·
35550 (1) ·
54175 (1) ·
55385 (1) ·
58725 (1) ·
74625 (1) ·
Cocoa (1) ·
Fellsmere (1) ·
Fort Pierce (1) ·
Greenacres City (1) ·
Indialantic (1) ·
Jupiter (1) ·
Lake Park (1) ·
Malabar (1) ·
Melbourne (1) ·
Merritt Island (1) ·
Palm Beach (1) ·
Palm Springs village (1) ·
Port Orange (1) ·
Riviera Beach (1) ·
West Melbourne (1) ·
West Palm Beach (1)
'Banana River ' (1) ·
'Banana River Relief ' (1) ·
'Banana River Relief East' (1) ·
'Banana River Relief West' (1) ·
'BESSEY CREEK ' (1) ·
'COUNTY LINE CANAL C-23 ' (1) ·
'DRAINAGE CANAL ' (1) ·
'DRAINAGE DITCH ' (1) ·
'Goat Creek ' (1) ·
'Halifax River ' (1) ·
'Indian River East Relief' (1) ·
'Indian River Relief ' (1) ·
'KELLER (E-4) CANAL ' (1) ·
'Lake Worth Tide Relief' (1) ·
'Lake Worth Relief ' (1) ·
'LAT CANAL (LK WORTH INT)' (1) ·
'LATERAL CANAL #38 ' (1) ·
'LOXAHATCHEE CREEK ' (1) ·
'LOXAHATCHEE WPB CANAL ' (1) ·
'N RELIEF CANAL ' (1) ·
'OUTFALL CANAL ' (1) ·
'OUTFALL SLOUGH ' (1) ·
'PHIPP CANAL ' (1) ·
'RELIEF CANAL ' (1) ·
'Relief E.of North Bridge' (1) ·
'RIM DITCH CANAL C-24 ' (1) ·
'SHAWANO DRAINAGE DITCH ' (1) ·
'St Johns River Relief ' (1) ·
'St. Johns River Relief ' (1) ·
'Turnbull Creek (East) ' (1) ·
'Turnbull Creek (West) ' (1) ·
'W. Relief Indian River ' (1) ·
Banana River Relief (1) ·
St Johns River Relief (1)
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
10500 (1) ·
13300 (1) ·
13400 (1) ·
15300 (1) ·
15700 (1) ·
16250 (1) ·
18500 (1) ·
19500 (1) ·
200 (1) ·
20150 (1) ·
21000 (1) ·
24317 (1) ·
26500 (1) ·
30500 (1) ·
34244 (1) ·
37000 (1) ·
40300 (1) ·
4400 (1) ·
44400 (1) ·
4600 (1) ·
46600 (1) ·
48633 (1) ·
59800 (1) ·
600 (1) ·
68700 (1) ·
6900 (1) ·
742 (1) ·
7473 (1) ·
78500 (1) ·
8145 (1) ·
8250 (1) ·
9150 (1)
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)
Deterioration or initial disintegration, minor chloride contamination, cracking with some leaching, or spalls on concrete or masonry walls and slabs. Local minor scouring at curtain walls, wingwalls or pipes. Metal culverts have a smooth curvature, non-symmetrical shape, significant corrosion or moderate pitting. (1) ·
Moderate to major deterioration or disintegration, extensive cracking and leaching or spalls on concrete or masonry walls and slabs. Minor settlement or misalignment. Noticeable scouring or erosion at curtain walls, wingwalls or pipes. Metal culverts have significant distortion and deflection in one section, significant corrosion or deep pitting (1) ·
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)
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 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 with "unknown" foundation that has not been evaluated for scour. Until risk can be determined, a plan of action should be developed and implemented to reduce the risk to users from abridge failure during and immediately after a flood event. (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)
103753 (1) ·
1041 (1) ·
119194 (1) ·
11972 (1) ·
12966 (1) ·
136198 (1) ·
14132 (1) ·
14314 (1) ·
15875 (1) ·
18218 (1) ·
23076 (1) ·
23249 (1) ·
250 (1) ·
26546 (1) ·
27240 (1) ·
28194 (1) ·
32098 (1) ·
33832 (1) ·
34960 (1) ·
36435 (1) ·
42189 (1) ·
45978 (1) ·
52918 (1) ·
59413 (1) ·
64195 (1) ·
69920 (1) ·
7634 (1) ·
77034 (1) ·
7981 (1) ·
80851 (1) ·
84378 (1) ·
898 (1)
Showing below up to 64 results in range #1 to #64.
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
- 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