Laserfiche WebLink
• <br />MEMORANDUM - Background for August 30, 1995 Meeting <br />Page 2 <br />Fundamental in the discussion is the amount of water allocated to Colorado and the <br />amount of water currently in use. The Colorado River Compacts were negotiated based <br />on a perceived 15 MAF of available water. Recent hydrology indicates the available water <br />may be only 14.5 MAF. Additionally, differing interpretations of Colorado's obligation <br />under the Mexican Treaty effect the amount of water which may be available to Colorado. <br />The estimates of water development potential to be protected for the Yampa River basin <br />the CDWG range from 164,572 AF (based on a total entitlement of 3.079 MAF) to 338,013 <br />AF (based on 3.855 MAF). <br />In Table 1 we have attempted to put relative meaning to these amounts of water <br />by equating them to industry, agriculture and population. We hope this presentation gives <br />meaning to the amount of development which must occur within the Yampa river basin to <br />consume these amounts of water. <br />Figure 2 <br />Using the demand patterns developed during the Yampa Feasibility Study, Figure <br />2 shows that much of the dry year future demand projected for the Yampa River would <br />occur out of sync with the available supply. To meet this demand pattern storage would <br />need to be constructed. <br />Figure 3 <br />Using the demand patterns developed during the Yampa Feasibility Study, Figure <br />2 shows that much of the average year future demand projected for the Yampa River would <br />occur out of sync with the available supply. To meet this demand pattern some storage <br />would need to be constructed, although less than would be required to meet dry year <br />demands. <br />Figure 4 <br />Figure 4 suggests a shift in the demand impact on the hydrograph which would be <br />realized if storage would be constructed to meet the dry year demand levels. This would <br />be a suggestion for the pattern of development potential which should be protected when <br />considering an instream flow filing. <br />