Laserfiche WebLink
<br />001991 <br /> <br />Reclamation created data tables of all time series used in natural flow spreadsheets. In addition, a <br />data table called Hue Jtys containing irrigation unit data such as total acres and incidental loss rate <br />was developed and populated. Some additional support tables were also developed. <br />The next step was to map the depletions in the newly created database to RiverWare nodes. A table <br />called Hue map was used to map all depletions of a given diversion. Figure 4-1 shows how tables <br />Sta all and Hue map are linked through field sta num. Sta num is a concatenation of the water <br />district, id, and use code. Table Hue_map was linked to table Hue Jtys as shown on Figure 4-2. <br /> <br />Finally, RiverWare nodes were mapped to depletion categories by creating table P _nodes and linking <br />it to table Hue map as shown on Figure 4-3. The linking fields are sta num and huc combo. <br />Huc combo (also called HUC combination) is merely a number to describe-the nth item that was <br />mapped to a given diversion in Sta_num. Huc_combo will always vary from 1 to number of <br />depletions that a diversion is mapped to. Table F-l in Appendix F lists entire contents of table <br />P_nodes. <br /> <br />The following is an excerpt of table p _nodes showing complete mapping of one aggregate diversion <br />with two water user nodes. <br /> <br />34_5141 1 AboveJacksonGulch_IrSum <br />34_5149 1 AboveJacksonGulch_NoDlr <br />34 51492 AboveJacksonGulch NoDlr <br />- - <br />34_5600 1 AboveJacksonGulch_NonIr <br />34_5601 1 AboveJacksonGulch_IrSum <br />34_5609 1 AboveJacksonGulch_NoDlr <br />34 5609 2 AboveJacksonGulch NoDlr <br /> <br />What the example is showing is that station number 34_5141, HUC combination 1 is mapped to <br />RiverWare node AboveJacksonGulch_IrSum, station number 34_5149, HUC combination 1 is <br />mapped to RiverWare node AboveJacksonGulch _ NoDlr, and so on. Irrigation depletions and non- <br />irrigation depletions were mapped to separate. However, an aggregate diversion may have an <br />irrigation water user and a non-irrigation user. This was particularly true in Colorado where most <br />irrigation diversions also have a stock water right. The majority of Colorado non irrigation <br />diversions are associated with an irrigation diversion (same diversion id with a 'I' and a '9' use <br />code). The non irrigation diversion was mapped to two depletion categories - livestock and stock <br />pond evaporation. Hence the appearance of two HUC combinations for station 34_5149 and <br />34 5609. <br /> <br />Note that above example shows an Aggregate Diversion (AboveJacksonGulch) with two RiverWare <br />water user nodes, AboveJacksonGulch IrSum and AboveJacksonGulch NoDlr. In Table 6-1, the <br />aggregate diversion is always part of name left of the underscore. The-water user node is the full <br />name. Many diversions were aggregated to a common RiverWare node. Only larger diversions <br />were mapped one-to-one. Most irrigation water users were labeled "IrSum" while most non <br />irrigation water users were labeled "NoDlr". <br /> <br />DRAFT - SJRIP Hydrology Model Documentation <br />June 18, 1999 <br /> <br />52 <br />