07.09.2014 Views

Chapter 1 Minimum Flows and Levels - Southwest Florida Water ...

Chapter 1 Minimum Flows and Levels - Southwest Florida Water ...

Chapter 1 Minimum Flows and Levels - Southwest Florida Water ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

attributed to analytic precision differences. However, for presentation <strong>and</strong><br />

discussion purposes, we combined numerous l<strong>and</strong> use types into fairly broad<br />

categories, <strong>and</strong> thereby eliminated some of the error associated with use of the<br />

two classification systems.<br />

For our analyses, l<strong>and</strong> use/cover types identified included: urban; upl<strong>and</strong>s<br />

(rangel<strong>and</strong> <strong>and</strong> upl<strong>and</strong> forests); wetl<strong>and</strong>s (wetl<strong>and</strong> forests <strong>and</strong> non-forested<br />

wetl<strong>and</strong>s); mines; water; citrus; <strong>and</strong> other agriculture. We examined changes in<br />

these use/cover types for the entire watershed <strong>and</strong> also for two major subbasins.<br />

Before discussing individual sub-basin l<strong>and</strong> use changes, it is informative to<br />

discuss the entire watershed of the Braden River to get an appreciation of the<br />

major l<strong>and</strong> uses/covers <strong>and</strong> the changes that have occurred during the nearly 30<br />

years for which l<strong>and</strong> use maps are available. L<strong>and</strong> use/cover maps for 1972 <strong>and</strong><br />

1999 for the entire Braden River watershed are shown in Figures 2-3 <strong>and</strong> 2-4.<br />

Based on these maps, the entire Braden River watershed is 83.6 square miles or<br />

53,487 acres in size (Table 2-1).<br />

Because we combine several agricultural l<strong>and</strong> use types for our analysis,<br />

temporal changes in l<strong>and</strong> use from 1972 to 1999 (see Figure 2-5) may not reflect<br />

the shift which has occurred from less intensive types of agricultural l<strong>and</strong> use to<br />

those requiring greater amounts of water. It should be noted, however, that of<br />

the major l<strong>and</strong> use categories, the amount of l<strong>and</strong> converted to urban uses has<br />

shown the single greatest increase. In many instances, within sub-basins, what<br />

appears to be a substantial decrease in upl<strong>and</strong>s <strong>and</strong> increase in wetl<strong>and</strong>s is<br />

actually an artifact of the disparity in resolution of features denoted in 1972 <strong>and</strong><br />

1999 mapping. While it appears that the amount of wetl<strong>and</strong>s has increased in<br />

most sub-basins, this is probably not the case. Because many wetl<strong>and</strong>s are<br />

small in size <strong>and</strong> interspersed within upl<strong>and</strong> areas, they were not delineated<br />

under the relatively coarser resolution employed in the 1972 mapping. Actual<br />

increases in wetl<strong>and</strong>s (resulting in a concomitant decrease in upl<strong>and</strong>s) were the<br />

consequence of increased resolution rather than the conversion of, for example,<br />

upl<strong>and</strong>s to wetl<strong>and</strong>s. In many cases what appear to be substantial declines in<br />

upl<strong>and</strong>s should more appropriately be interpreted as an improvement in map<br />

resolution. However, decreases in upl<strong>and</strong>s have occurred in some sub-basins.<br />

It is helpful when interpreting these data to view the sum of the wetl<strong>and</strong>s <strong>and</strong><br />

upl<strong>and</strong>s as natural area, <strong>and</strong> the decline in this total as a measure of conversion<br />

to some other more intensive l<strong>and</strong> use (e.g., agriculture, mining, urban).<br />

2-4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!