Laserfiche WebLink
<br />Microsoft. One of the big efforts in the software industry recently has been the conversion of the <br />myriad of existing VB 6 applications to VB.NET. Microsoft has provided many tools to <br />facilitate these conversions. <br />The daily consumptive use methodologies available in StateCU do not allow an analysis to be <br />performed if there is any missing daily climate station data (minimum temperature, maximum <br />temperature, precipitation, wind speed, vapor pressure, and solar radiation). In addition, the <br />daily methodology code was developed when computer capabilities restricted extensive use of <br />arrays. Therefore, each climate station data file must currently have the same number of climate <br />stations in the same order for the same years in order for StateCU to calculate CU correctly. <br />StateCU users at the State have requested the ability for StateCU to adjust temperature and <br />precipitation data based on the location of CU structures compared to the location of the climate <br />station where the data used in an analysis was collected. <br />Consultants for the Upper Gunnison River Water Conservancy District (UGRWCD} use <br />advanced StateCU capabilities to "fill in" estimates of water supply-limited consumptive use <br />when no diversion records exist. LRE did not know that the Upper Gunnison application of <br />StateCU required this feature, and the capability was removed from the water budget portion of <br />StateCU when the State requested the ability to run a CU analysis with missing data and have the <br />results provide a missing data flag. UGRWCD has indicated their need for StateCU to <br />automatically fill missing CU results. <br />Based on investigation of effective precipitation methods during phase 1 and 2 of SPDSS, it was <br />determined that the most widely accepted and used methodology for estimating effective <br />precipitation is the monthly TR-21 method. Basin users have indicated their desire to run a daily <br />ASCE Penman CU analysis along with a monthly TR-21 method to estimate effective <br />precipitation in order to determine total monthly irrigation water requirement. Currently, <br />StateCU does not allow a monthly effective precipitation method to be used with a daily CU <br />analysis. <br />StateCU data sets have been generated in support of the CDSS efforts that represent 100 percent <br />of crop consumptive use in the basin. These data sets, plus filled and unfilled climate data sets, <br />are available for StateCU users in Colorado. For the western slope and Rio Grande basins, <br />smaller structures have been combined into "aggregate" structures. Users at the State are often <br />reviewing change cases that involve smaller structures not explicitly included in the supplied <br />data sets. They have requested a system for automating the generation of new sets of StateCU <br />input files from StateCUI so they can concentrate on StateCU analyses and not on the data <br />management interface tools. <br />Previously, it was agreed that users wishing to significantly revise input data extracted from <br />HydroBase would need to leave the StateCU environment and use the data management tools <br />TSTooI or StateDMI. Therefore, StateCUI currently allows only limited editing capabilities <br />surrounding input variables and analysis flags. In support of allowing users to generate data sets <br />using a "wizard" from within the StateCU GUI, StateCUI will be updated to allow all input data <br />to be edited. In addition, add the capability to document data edits from within the GUI by <br />creating and inserting comment lines into the data files. Editing capabilities for time series data <br />will include the ability to revise a single value or group of data, plus the ability to change the <br />Page A-8 <br />