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: (Click arrow to add another value)
Route 005d:
Direction 005e:
Features 006a:
'ANGLE RD & BELCHER CANAL' (1) ·
'BELCHER C-25 CANAL ' (1) ·
'Belcher Canal (C-25) ' (1) ·
'Berrys Canal ' (1) ·
'BIG MUD CREEK ' (1) ·
'BLIND CREEK ' (1) ·
'Brando Canal ' (1) ·
'Callalisa Creek ' (1) ·
'Canal ' (1) ·
'Canal No. 1 ' (1) ·
'Canal No.1 ' (1) ·
'Conners Canal ' (1) ·
'DRAINAGE DITCH ' (1) ·
'FEC Railroad ' (1) ·
'FPL Nuc Plant Disc Canal' (1) ·
'FPL Nuc Plant Intake Cnl' (1) ·
'Gabordy's Canal ' (1) ·
'ICWW ' (1) ·
'Intracoastal Waterway ' (1) ·
'IWW Indian River ' (1) ·
'LITTLE MUD CREEK ' (1) ·
'Moore's Creek ' (1) ·
'MOORES CREEK ' (1) ·
'Relief E.of North Bridge' (1) ·
'SR 70 ' (1) ·
'SR 91 TPK ' (1) ·
'SR 91 TPK(FT PIERCE INT)' (1) ·
'SR-70 (Okeechobee Rd.) ' (1) ·
'TAYLOR CREEK ' (1) ·
'Taylor Creek(C-25 Canal)' (1) ·
'TEN MILE CREEK ' (1) ·
'Turnbull Creek ' (1) ·
'US-1 & FECRR ' (1) ·
'Yacht Club Cut ' (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
Traffic 029:
10200 (1) ·
10500 (1) ·
1091 (1) ·
120 (1) ·
1400 (1) ·
1500 (1) ·
15100 (1) ·
15900 (1) ·
17122 (1) ·
18300 (1) ·
2000 (1) ·
20150 (1) ·
21500 (1) ·
2165 (1) ·
240 (1) ·
25000 (1) ·
2544 (1) ·
2599 (1) ·
2600 (1) ·
26000 (1) ·
28100 (1) ·
29307 (1) ·
30000 (1) ·
34244 (1) ·
3820 (1) ·
3850 (1) ·
40300 (1) ·
4800 (1) ·
500 (1) ·
5458 (1) ·
6100 (1) ·
7100 (1) ·
7150 (1) ·
7800 (1) ·
9200 (1) ·
9300 (1)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
Width 052:
Deck 058:
Superstructure 059:
Substructure 060: (Click arrow to add another value)
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) ·
N/A (1)
Culvert 062:
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) ·
No noticeable or noteworthy deficiencies which affect the condition of the culvert. Insignificant scrape marks caused by drift. (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:
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 conditions; field review indicates action is required to protect exposed foundations (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) ·
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)
Future 114:
10584 (1) ·
12319 (1) ·
12405 (1) ·
1320 (1) ·
13533 (1) ·
144 (1) ·
15962 (1) ·
16136 (1) ·
17697 (1) ·
18218 (1) ·
2256 (1) ·
2500 (1) ·
2603 (1) ·
26199 (1) ·
2620 (1) ·
27587 (1) ·
29707 (1) ·
3145 (1) ·
31751 (1) ·
3470 (1) ·
34960 (1) ·
360 (1) ·
37303 (1) ·
43375 (1) ·
4414 (1) ·
4511 (1) ·
45110 (1) ·
4622 (1) ·
48754 (1) ·
50848 (1) ·
52050 (1) ·
521 (1) ·
59413 (1) ·
6604 (1) ·
6680 (1) ·
69920 (1) ·
8328 (1)
Clearance 116:
Showing below up to 52 results in range #1 to #52.
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
