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:
'11th Street Canal ' (1) ·
'B-19 Canal / Trib 1 ' (1) ·
'BUCCANEER CANAL ' (1) ·
'BUTTERFLY CANAL ' (1) ·
'C-104 CANAL ' (1) ·
'CAMINO CANAL ' (1) ·
'CANAL C-104 ' (1) ·
'CANAL C-108 ' (1) ·
'CANAL C-24 ' (1) ·
'CANAL C-73 ' (1) ·
'CANAL E-114 ' (1) ·
'CANAL E-12/E-84 ' (1) ·
'CANAL E-14 ' (1) ·
'CANAL E-8 ' (1) ·
'CANAL E-84 ' (1) ·
'Canal No. 1 (Rim Canal) ' (1) ·
'COLLIER CREEK ' (1) ·
'CPB20 CANAL ' (1) ·
'EL RIO CANAL ' (1) ·
'FISHTAIL CANAL ' (1) ·
'GARDEN CANAL ' (1) ·
'HILLSBORO CANAL L-14 ' (1) ·
'HILLSBORO L-14 CANAL ' (1) ·
'Indian River Relief ' (1) ·
'LIPTOG CANAL ' (1) ·
'LWDD E-4 CANAL ' (1) ·
'RELIEF CANAL ' (1) ·
'Turkey Creek ' (1) ·
'WEST PALM BEACH CANAL ' (1)
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
1000 (1) ·
1050 (1) ·
110 (1) ·
1120 (1) ·
115 (1) ·
120 (1) ·
1200 (1) ·
1440 (1) ·
1500 (1) ·
153 (1) ·
200 (1) ·
2050 (1) ·
220 (1) ·
2302 (1) ·
250 (1) ·
2600 (1) ·
3000 (1) ·
304 (1) ·
354 (1) ·
3825 (1) ·
400 (1) ·
440 (1) ·
4700 (1) ·
500 (1) ·
5975 (1) ·
600 (1) ·
630 (1) ·
7200 (1) ·
9500 (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)
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 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)
1041 (1) ·
12492 (1) ·
1350 (1) ·
1562 (1) ·
16482 (1) ·
1665 (1) ·
1700 (1) ·
1728 (1) ·
174 (1) ·
1900 (1) ·
2000 (1) ·
2020 (1) ·
250 (1) ·
2603 (1) ·
265 (1) ·
3120 (1) ·
3470 (1) ·
3500 (1) ·
353 (1) ·
3556 (1) ·
3994 (1) ·
4000 (1) ·
428 (1) ·
500 (1) ·
600 (1) ·
6812 (1) ·
694 (1) ·
7050 (1) ·
720 (1) ·
763 (1) ·
7980 (1) ·
850 (1)
Showing below up to 44 results in range #1 to #44.
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