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: (Click arrow to add another value)
Place 004:
Route 005d:
Direction 005e:
Features 006a:
Critical 006b:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
Owner 022:
Built 027:
Traffic 029:
Traffic Year 030:
Service On 042a:
Service Under 042b:
Kind 043a:
Type 043b:
Length 049:
Width 052:
Deck 058: (Click arrow to add another value)
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:
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 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) ·
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 107 results in range #1 to #107.
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
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
- Template:Bridge Data fetch
