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)
bridge data > Route 005d :
00000 or
00603
& Channel 061:
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.
Use the filters below to narrow your results.
ObjectID:
None (1) ·
35550 (1) ·
54175 (1) ·
58725 (1) ·
Atlantis (1) ·
Belle Glade (1) ·
Boca Raton (1) ·
Boynton Beach (1) ·
Delray Beach (1) ·
Fort Pierce (1) ·
Golf village (1) ·
Greenacres City (1) ·
Holly Hill (1) ·
Indiantown village (1) ·
Jupiter (1) ·
Lake Worth (1) ·
Lantana (1) ·
Manalapan (1) ·
North Palm Beach village (1) ·
Ocean Ridge (1) ·
Pahokee (1) ·
Palm Bay (1) ·
Port Orange (1) ·
Rockledge (1) ·
South Daytona (1) ·
Tequesta village (1) ·
Vero Beach (1) ·
Wellington village (1) ·
West Palm Beach (1)
Features 006a:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
1925 (1) ·
1955 (1) ·
1962 (1) ·
1964 (1) ·
1965 (1) ·
1967 (1) ·
1969 (1) ·
1975 (1) ·
1980 (1) ·
1984 (1) ·
1985 (1) ·
1986 (1) ·
1988 (1) ·
1991 (1) ·
1992 (1) ·
1993 (1) ·
1994 (1) ·
1995 (1) ·
1996 (1) ·
1997 (1) ·
1999 (1) ·
2000 (1) ·
2002 (1) ·
2003 (1) ·
2004 (1) ·
2005 (1) ·
2006 (1) ·
2007 (1) ·
2008 (1) ·
2009 (1) ·
2010 (1) ·
2011 (1) ·
2012 (1) ·
2013 (1) ·
2014 (1) ·
2015 (1) ·
2016 (1) ·
2017 (1)
Traffic 029:
Length 049:
N/A (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)
Bridge foundations (including piles) on dry land well above flood water elevations. (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 (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 is scour critical; bridge foundations determined to be unstable for assessed or calculated scour conditions: Scour within limits of footing or piles. Scour below spread-footing base or pile tips. (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:
Showing below up to 91 results in range #1 to #91.
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
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch