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:
Direction 005e:
Features 006a:
'ANGLE RD & BELCHER CANAL' (1) ·
'Banana River Relief East' (1) ·
'Banana River Relief West' (1) ·
'C-52 Canal ' (1) ·
'CANAL L-12 ' (1) ·
'CANAL L-20 ' (1) ·
'CR-3 ' (1) ·
'Danforth Creek ' (1) ·
'E-2 Canal ' (1) ·
'E-3 CANAL ' (1) ·
'Header Creek Canal ' (1) ·
'I-95 ' (1) ·
'Indian River Relief East' (1) ·
'Indian River West Relief' (1) ·
'KELLER CANAL ' (1) ·
'Kings Road ' (1) ·
'L-78 Borrow Canal ' (1) ·
'LEVEE NO. 8 ' (1) ·
'LEVEE NO.8 ' (1) ·
'LWDD E-1 CANAL ' (1) ·
'Miami Canal L-25 ' (1) ·
'OUTFALL SLOUGH ' (1) ·
'Padgett Branch Marsh ' (1) ·
'S Fork St. Lucie River ' (1) ·
'SR-404 ' (1) ·
'St Johns River ' (1) ·
'St Johns River Relief ' (1) ·
'St. Johns River ' (1) ·
'Ten Mile Creek ' (1) ·
'Tomoka River ' (1) ·
I-95 (1) ·
Sawgrass Creek (1) ·
St Johns River (1) ·
St Johns River Relief (1) ·
St. Johns River (1)
Critical 006b:
Facility 007:
'BISCAYNE DRIVE ' (1) ·
'CENTER DRIVE ' (1) ·
'CR-606 Oslo Rd. ' (1) ·
'EB Martin Downs Bd' (1) ·
'EB SR 70 ' (1) ·
'NEW ENGLAND BLVD ' (1) ·
'Pioneer Road ' (1) ·
'SR 70 EB ' (1) ·
'SR-40 EB ' (1) ·
'SR-40 WB ' (1) ·
'SR-404 EB ' (1) ·
'SR-404 WB ' (1) ·
'SR-407 ' (1) ·
'SR-50 EB ' (1) ·
'SR-50 WB ' (1) ·
'SR-520 EB ' (1) ·
'SR-528 ' (1) ·
'SR-60 EB ' (1) ·
'SR-60 WB ' (1) ·
'SR-80 EB ' (1) ·
'SR-80 WB ' (1) ·
'SR-80EB (Southern)' (1) ·
'SR-80WB (Southern)' (1) ·
'SR519NB(Fiske Blv)' (1) ·
'SR519SB(Fiske Blv)' (1) ·
'SR91 NB TPK 157.9 ' (1) ·
'SR91 NB TPK 158.6 ' (1) ·
'SR91 NB TPK 178.03' (1) ·
'SR91 SB TPK 157.9 ' (1) ·
'SR91 SB TPK 158.6 ' (1) ·
'SR91 SB TPK 178.03' (1) ·
'US-1 NB ' (1) ·
'US-192 WB ' (1) ·
'US-27/SR-80 NB ' (1) ·
'US-27/SR-80 SB ' (1) ·
'WB SR - 714 ' (1) ·
Micco Rd. (1) ·
US-192 EB (1) ·
US-192 WB (1)
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
Lanes 028a:
Traffic 029:
12750 (1) ·
1400 (1) ·
15250 (1) ·
16250 (1) ·
17122 (1) ·
17750 (1) ·
20000 (1) ·
20500 (1) ·
21000 (1) ·
21300 (1) ·
23000 (1) ·
2600 (1) ·
300 (1) ·
3087 (1) ·
318 (1) ·
3250 (1) ·
3400 (1) ·
4400 (1) ·
4800 (1) ·
5000 (1) ·
5400 (1) ·
5850 (1) ·
6174 (1) ·
748 (1) ·
7500 (1) ·
800 (1) ·
8200 (1)
Traffic Year 030:
Service On 042a:
Service Under 042b:
Kind 043a: (Click arrow to add another value)
Type 043b:
Length 049:
Width 052: (Click arrow to add another value)
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)
Culvert 062:
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 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:
10150 (1) ·
10712 (1) ·
1249 (1) ·
13012 (1) ·
14227 (1) ·
22121 (1) ·
2429 (1) ·
26459 (1) ·
28194 (1) ·
29707 (1) ·
30796 (1) ·
34700 (1) ·
35568 (1) ·
36435 (1) ·
36956 (1) ·
39905 (1) ·
4510 (1) ·
500 (1) ·
521 (1) ·
5356 (1) ·
5639 (1) ·
5899 (1) ·
7634 (1) ·
8328 (1) ·
8675 (1) ·
9369 (1) ·
960 (1)
Future Year 115: (Click arrow to add another value)
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
