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:
None (1) ·
45775 (1) ·
58725 (1) ·
77275 (1) ·
Cocoa (1) ·
Daytona Beach (1) ·
DeLand (1) ·
Fellsmere (1) ·
Fort Pierce (1) ·
Holly Hill (1) ·
Malabar (1) ·
Melbourne (1) ·
Micco (1) ·
New Smyrna Beach (1) ·
Ormond Beach (1) ·
Palm Beach Gardens (1) ·
Palm Springs village (1) ·
Port Orange (1) ·
Riviera Beach (1) ·
Stuart (1) ·
Vero Beach (1) ·
Viera (1) ·
West Melbourne (1) ·
West Palm Beach (1)
Route 005d:
Features 006a:
'Beamer's Canal ' (1) ·
'Beamer's Ditch ' (1) ·
'Belvedere Road ' (1) ·
'BIG MUD CREEK ' (1) ·
'BLIND CREEK ' (1) ·
'C-18 Canal ' (1) ·
'Canal ' (1) ·
'Canal 15 ' (1) ·
'Carter's Canal ' (1) ·
'Crane Creek Canal ' (1) ·
'Creek ' (1) ·
'Drainage Canal ' (1) ·
'DRAINAGE DITCH ' (1) ·
'Eau-Gallie River ' (1) ·
'Fellsmere Canal ' (1) ·
'I-95 ' (1) ·
'Indian River ' (1) ·
'L.W.D.D. #9 ' (1) ·
'Lake Dias Creek ' (1) ·
'LATERAL CANAL A ' (1) ·
'MONTERREY WATERWAY ' (1) ·
'Moore's Creek ' (1) ·
'Navy Canal ' (1) ·
'Northlake Blvd. ' (1) ·
'Nova Canal ' (1) ·
'POPPOLTON CREEK ' (1) ·
'SR 60 ' (1) ·
'SR-91 Turnpike ' (1) ·
'Trib to Groover Creek ' (1) ·
'TRIBUTARY OF MANATEE CRE' (1) ·
'TRIBUTARY OF MANATEE CRK' (1) ·
'Turnbull Creek ' (1) ·
Banana River Relief (1) ·
Brushy Canal (1) ·
Canal (1) ·
Fellsmere Canal (1) ·
Palm Canal (1) ·
St Johns River Relief (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
1932 (1) ·
1937 (1) ·
1942 (1) ·
1946 (1) ·
1948 (1) ·
1950 (1) ·
1952 (1) ·
1956 (1) ·
1957 (1) ·
1958 (1) ·
1959 (1) ·
1964 (1) ·
1965 (1) ·
1966 (1) ·
1967 (1) ·
1969 (1) ·
1970 (1) ·
1972 (1) ·
1975 (1) ·
1977 (1) ·
1987 (1) ·
1989 (1) ·
1991 (1) ·
1993 (1) ·
1994 (1) ·
1995 (1) ·
1998 (1) ·
2000 (1) ·
2003 (1) ·
2004 (1) ·
2005 (1) ·
2007 (1) ·
2011 (1) ·
2012 (1) ·
2014 (1)
Traffic 029:
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049: (Click arrow to add another value)
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 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) ·
No deficiencies (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: (Click arrow to add another value)
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 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 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) ·
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:
Clearance 116:
Showing below up to 55 results in range #1 to #55.
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
