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:
Features 006a:
Facility 007:
Number 008:
Location 009:
Latitude 016:
Longitude 017:
101 (1) ·
101000 (1) ·
101541 (1) ·
104500 (1) ·
1200 (1) ·
12533 (1) ·
14200 (1) ·
16400 (1) ·
18000 (1) ·
195661 (1) ·
2000 (1) ·
203082 (1) ·
20500 (1) ·
21000 (1) ·
24000 (1) ·
25000 (1) ·
25170 (1) ·
25500 (1) ·
26500 (1) ·
2700 (1) ·
29000 (1) ·
3000 (1) ·
3200 (1) ·
33000 (1) ·
34000 (1) ·
40500 (1) ·
43500 (1) ·
6124 (1) ·
6900 (1) ·
7300 (1) ·
7400 (1) ·
8100 (1) ·
8368 (1) ·
8900 (1) ·
90900 (1) ·
9100 (1) ·
9700 (1) ·
98900 (1) ·
9900 (1)
11 (1) ·
13 (1) ·
135 (1) ·
15 (1) ·
16 (1) ·
18 (1) ·
20 (1) ·
23 (1) ·
24 (1) ·
25 (1) ·
26 (1) ·
27 (1) ·
28 (1) ·
29 (1) ·
30 (1) ·
32 (1) ·
34 (1) ·
35 (1) ·
36 (1) ·
37 (1) ·
38 (1) ·
39 (1) ·
424 (1) ·
44 (1) ·
49 (1) ·
53 (1) ·
55 (1) ·
58 (1) ·
64 (1) ·
66 (1) ·
68 (1) ·
72 (1) ·
8 (1) ·
82 (1) ·
91 (1)
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)
Future 114:
Showing below up to 58 results in range #1 to #58.
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