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) ·
35550 (1) ·
54175 (1) ·
58725 (1) ·
Boynton Beach (1) ·
Daytona Beach (1) ·
DeBary (1) ·
Fort Pierce (1) ·
Holly Hill (1) ·
Melbourne (1) ·
New Smyrna Beach (1) ·
Ormond Beach (1) ·
Palm Bay (1) ·
Palm Beach Gardens (1) ·
Palm Shores (1) ·
Port Orange (1) ·
Port St. John (1) ·
Riviera Beach (1) ·
South Daytona (1) ·
Stuart (1) ·
Valkaria (1) ·
Vero Beach (1) ·
West Palm Beach (1)
Route 005d:
Direction 005e:
Features 006a:
'B-19 Canal ' (1) ·
'Bessey Creek ' (1) ·
'C-59 Canal ' (1) ·
'Canal ' (1) ·
'Crane Creek ' (1) ·
'Drainage Canal ' (1) ·
'Drainage Ditch ' (1) ·
'E-2-W canal ' (1) ·
'Eau Gallie River ' (1) ·
'Eau-Gallie River ' (1) ·
'ELKCAM CANAL ' (1) ·
'Five Mile Creek ' (1) ·
'FPL Cooling Disch. Canal' (1) ·
'FPL Cooling Intake Canal' (1) ·
'Goat Creek ' (1) ·
'Golf Cart Underpass ' (1) ·
'Halifax Canal ' (1) ·
'Horse Creek ' (1) ·
'HOWARD CREEK ' (1) ·
'Lake Osborne ' (1) ·
'LATERAL CANAL A ' (1) ·
'Little Tomoka River ' (1) ·
'MANATEE CREEK ' (1) ·
'Misner Creek ' (1) ·
'MONTERREY WATERWAY ' (1) ·
'Moore's Creek ' (1) ·
'Moores Creek ' (1) ·
'Nova Canal ' (1) ·
'Nova Road Canal ' (1) ·
'POPPOLTON CREEK ' (1) ·
'Range Line Canal ' (1) ·
'Reed Canal ' (1) ·
'Sweetwater Creek ' (1) ·
'Warner Creek ' (1) ·
'WPB WATER SUPPLY CANAL ' (1) ·
Zoo Trail (1)
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
1948 (1) ·
1950 (1) ·
1952 (1) ·
1956 (1) ·
1957 (1) ·
1958 (1) ·
1959 (1) ·
1970 (1) ·
1974 (1) ·
1975 (1) ·
1977 (1) ·
1982 (1) ·
1983 (1) ·
1986 (1) ·
1988 (1) ·
1989 (1) ·
1990 (1) ·
1992 (1) ·
1993 (1) ·
1994 (1) ·
1995 (1) ·
1996 (1) ·
1998 (1) ·
2000 (1) ·
2003 (1) ·
2005 (1) ·
2006 (1) ·
2008 (1) ·
2009 (1) ·
2011 (1) ·
2013 (1) ·
2014 (1) ·
2015 (1) ·
2016 (1)
Traffic 029:
Service On 042a: (Click arrow to add another value)
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
Deck 058:
Superstructure 059: (Click arrow to add another value)
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) ·
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) ·
No deficiencies (1) ·
No noticeable or noteworthy deficiencies which affect the condition of the culvert. Insignificant scrape marks caused by drift. (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 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)
Future 114:
Future Year 115:
Clearance 116:
Showing below up to 56 results in range #1 to #56.
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
