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:
None (1) ·
35550 (1) ·
54175 (1) ·
58725 (1) ·
Boynton Beach (1) ·
Daytona Beach (1) ·
DeBary (1) ·
DeLand (1) ·
Deltona (1) ·
Fellsmere (1) ·
Fort Pierce (1) ·
Jupiter (1) ·
Lantana (1) ·
Malabar (1) ·
Melbourne (1) ·
Melbourne Village (1) ·
Merritt Island (1) ·
New Smyrna Beach (1) ·
North Palm Beach village (1) ·
Palm Beach Gardens (1) ·
Port Orange (1) ·
Riviera Beach (1) ·
Royal Palm Beach village (1) ·
South Daytona (1) ·
Titusville (1)
Features 006a:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
1958 (1) ·
1959 (1) ·
1963 (1) ·
1964 (1) ·
1965 (1) ·
1966 (1) ·
1967 (1) ·
1969 (1) ·
1976 (1) ·
1981 (1) ·
1982 (1) ·
1984 (1) ·
1985 (1) ·
1986 (1) ·
1987 (1) ·
1990 (1) ·
1991 (1) ·
1993 (1) ·
1994 (1) ·
1997 (1) ·
1999 (1) ·
2000 (1) ·
2003 (1) ·
2004 (1) ·
2005 (1) ·
2006 (1) ·
2008 (1) ·
2009 (1) ·
2012 (1) ·
2014 (1) ·
2017 (1)
Traffic 029:
Length 049:
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) ·
No noticeable or noteworthy deficiencies which affect the condition of the channel. (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 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 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 not over waterway. (1)
Future 114:
Showing below up to 94 results in range #1 to #94.
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
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch