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:
Route 005d:
Features 006a:
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027: (Click arrow to add another value)
Traffic 029:
1000 (1) ·
10000 (1) ·
101541 (1) ·
104500 (1) ·
114500 (1) ·
12200 (1) ·
12700 (1) ·
13500 (1) ·
1440 (1) ·
14878 (1) ·
16000 (1) ·
16297 (1) ·
172 (1) ·
17200 (1) ·
17750 (1) ·
20647 (1) ·
2300 (1) ·
240 (1) ·
283 (1) ·
3400 (1) ·
34500 (1) ·
3600 (1) ·
440 (1) ·
4400 (1) ·
45000 (1) ·
4800 (1) ·
5300 (1) ·
5800 (1) ·
6174 (1) ·
7161 (1) ·
72500 (1) ·
85750 (1)
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
1006 (1) ·
104 (1) ·
106 (1) ·
12 (1) ·
128 (1) ·
162 (1) ·
17 (1) ·
18 (1) ·
20 (1) ·
200 (1) ·
21 (1) ·
22 (1) ·
24 (1) ·
28 (1) ·
29 (1) ·
326 (1) ·
37 (1) ·
38 (1) ·
46 (1) ·
463 (1) ·
49 (1) ·
519 (1) ·
536 (1) ·
58 (1) ·
587 (1) ·
596 (1) ·
60 (1) ·
62 (1) ·
68 (1) ·
7 (1) ·
750 (1) ·
8 (1) ·
82 (1) ·
896 (1) ·
9 (1) ·
94 (1)
Width 052:
Deck 058:
Superstructure 059:
Substructure 060:
Channel 061: (Click arrow to add another value)
Culvert 062:
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:
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 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:
10063 (1) ·
10712 (1) ·
12424 (1) ·
125788 (1) ·
148776 (1) ·
1665 (1) ·
17350 (1) ·
176174 (1) ·
181308 (1) ·
19050 (1) ·
198658 (1) ·
2000 (1) ·
208 (1) ·
21167 (1) ·
23422 (1) ·
24776 (1) ·
25813 (1) ·
27760 (1) ·
28275 (1) ·
288 (1) ·
29842 (1) ·
30796 (1) ·
342 (1) ·
3990 (1) ·
4320 (1) ·
5899 (1) ·
59858 (1) ·
694 (1) ·
7634 (1) ·
78075 (1) ·
8328 (1) ·
9196 (1)
Clearance 116:
Showing below up to 54 results in range #1 to #54.
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
