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:
Direction 005e:
Features 006a:
Critical 006b:
Facility 007:
'I 95 SR 9 ' (1) ·
'I-4 EB ' (1) ·
'I-4 EB ' (1) ·
'I-4 WB ' (1) ·
'I-95 ' (1) ·
'I-95 NB ' (1) ·
'I-95 SB ' (1) ·
'NB I 95 SR 9 ' (1) ·
'NB I-95 (SR-9) ' (1) ·
'NB I-95 (SR-9) ' (1) ·
'SB I 95 SR 9 ' (1) ·
'SB I-95 (SR 9) ' (1) ·
'SB I-95 (SR-9 ) ' (1) ·
'SR-40 ' (1) ·
'SR-40 EB ' (1) ·
'SR-40 WB ' (1) ·
'SR-407 NB ' (1) ·
'SR-528 ' (1) ·
'SR-528 EB ' (1) ·
'SR-528 WB ' (1) ·
'SR-710 ' (1) ·
'SR-710 Beeline Hwy' (1) ·
'SR91 NB TPK 175.4 ' (1) ·
'SR91 NB TPK 178.03' (1) ·
'SR91 NB TPK 180.16' (1) ·
'SR91 SB TPK 175.4 ' (1) ·
'SR91 SB TPK 178.03' (1) ·
'SR91 SB TPK 180.16' (1) ·
'US98&441 SR700&15' (1) ·
Fiske Blvd Ramps (1) ·
I-95 (1)
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Built 027:
Traffic 029:
106500 (1) ·
12250 (1) ·
12600 (1) ·
15250 (1) ·
16250 (1) ·
16340 (1) ·
16500 (1) ·
171500 (1) ·
19000 (1) ·
19500 (1) ·
20000 (1) ·
203082 (1) ·
21000 (1) ·
21300 (1) ·
213000 (1) ·
25250 (1) ·
25474 (1) ·
31669 (1) ·
3200 (1) ·
32000 (1) ·
32680 (1) ·
35500 (1) ·
38000 (1) ·
40250 (1) ·
40500 (1) ·
41250 (1) ·
42764 (1) ·
45000 (1) ·
55000 (1) ·
64500 (1) ·
66500 (1) ·
6800 (1) ·
68000 (1) ·
6900 (1) ·
73000 (1) ·
82500 (1) ·
84500 (1) ·
8500 (1)
Traffic Year 030: (Click arrow to add another value)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
10 (1) ·
100 (1) ·
101 (1) ·
11 (1) ·
110 (1) ·
111 (1) ·
118 (1) ·
119 (1) ·
12 (1) ·
14 (1) ·
143 (1) ·
148 (1) ·
166 (1) ·
173 (1) ·
18 (1) ·
24 (1) ·
25 (1) ·
27 (1) ·
35 (1) ·
36 (1) ·
37 (1) ·
43 (1) ·
46 (1) ·
47 (1) ·
53 (1) ·
54 (1) ·
6 (1) ·
60 (1) ·
63 (1) ·
65 (1) ·
66 (1) ·
67 (1) ·
7 (1) ·
77 (1) ·
8 (1) ·
9 (1) ·
93 (1) ·
99 (1)
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) ·
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) ·
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 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 not over waterway. (1)
Future 114:
111908 (1) ·
115378 (1) ·
11798 (1) ·
117980 (1) ·
11972 (1) ·
126655 (1) ·
143138 (1) ·
146608 (1) ·
14748 (1) ·
184778 (1) ·
21254 (1) ·
21861 (1) ·
26459 (1) ·
28194 (1) ·
28350 (1) ·
28628 (1) ·
297552 (1) ·
32965 (1) ·
33832 (1) ·
34700 (1) ·
352347 (1) ·
36435 (1) ·
369555 (1) ·
36956 (1) ·
43809 (1) ·
44197 (1) ·
54946 (1) ·
5552 (1) ·
55520 (1) ·
56700 (1) ·
61592 (1) ·
65930 (1) ·
69834 (1) ·
70268 (1) ·
71569 (1) ·
74196 (1) ·
78075 (1) ·
95425 (1)
Future Year 115:
Clearance 116:
Showing below up to 71 results in range #1 to #71.
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
- 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
