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:
Date: (Click arrow to add another value)
County 003:
Place 004:
Route 005d: (Click arrow to add another value)
Direction 005e:
Features 006a:
'Aurantia Rd. ' (1) ·
'Beamer's Canal ' (1) ·
'Beamer's Ditch ' (1) ·
'C-54 Canal ' (1) ·
'Carter's Canal ' (1) ·
'CR-5A ' (1) ·
'Fellsmere Canal ' (1) ·
'I-95 ' (1) ·
'Indian River / ICW ' (1) ·
'Indian River East Relief' (1) ·
'Maytown Rd. ' (1) ·
'Maytown Road ' (1) ·
'Rockledge Creek ' (1) ·
'Sottile Canal ' (1) ·
'Spruce Creek ' (1) ·
'SR-40 ' (1) ·
'SR-406 ' (1) ·
'SR-421 ' (1) ·
'SR-44 ' (1) ·
'SR-442 ' (1) ·
'SR-50 ' (1) ·
'SR-518 ' (1) ·
'SR-520 ' (1) ·
'SR-524 ' (1) ·
'Sunshine Canal ' (1) ·
'Tillman Canal ' (1) ·
'Timothy's Ditch ' (1) ·
'Tomoka River ' (1) ·
'US-1 ' (1) ·
'US-192 ' (1) ·
'US-92 ' (1) ·
'W. Relief Indian River ' (1) ·
'Warner Creek ' (1) ·
Addison Canal (1) ·
Fellsmere Canal (1) ·
Lake Washington Road (1) ·
Sottile Canal (1) ·
Wickham Road (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
Traffic 029:
13250 (1) ·
15400 (1) ·
15700 (1) ·
16340 (1) ·
18250 (1) ·
18301 (1) ·
20327 (1) ·
21000 (1) ·
21382 (1) ·
23250 (1) ·
24750 (1) ·
25250 (1) ·
32250 (1) ·
33250 (1) ·
36500 (1) ·
37006 (1) ·
39750 (1) ·
41250 (1) ·
42764 (1) ·
49500 (1) ·
50500 (1) ·
66000 (1) ·
68000 (1) ·
68500 (1) ·
8000 (1) ·
81764 (1)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
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 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) ·
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:
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)
Inspect Date 090:
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 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 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 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:
114510 (1) ·
117980 (1) ·
118848 (1) ·
13880 (1) ·
141861 (1) ·
22989 (1) ·
26719 (1) ·
27240 (1) ·
28350 (1) ·
31664 (1) ·
31752 (1) ·
35268 (1) ·
36435 (1) ·
37098 (1) ·
40339 (1) ·
42941 (1) ·
43809 (1) ·
55954 (1) ·
57689 (1) ·
63328 (1) ·
64205 (1) ·
68966 (1) ·
71569 (1) ·
74196 (1) ·
85882 (1) ·
87618 (1)
Clearance 116:
Showing below up to 53 results in range #1 to #53.
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
