Laserfiche WebLink
<br />Also modifY watright to calculate the aggregated structure capacity as the sum of the <br />individual capacities of the structures being aggregated and calculate the aggregated <br />irrigated acreage as the sum of the acreage's of the individual structure acreage's. <br />Default information and return flow patterns will be handled as implemented for the <br />Phase II work. As such, data editing command-line options such as "setdiv" will still <br />be enabled on the aggregate structures. <br /> <br />The aggregation commands will be the result of aggregation studies done in Task <br />2.02. The implementation of this functionality will consist of the following: <br /> <br />a) Get the net absolute water rights for all the structures in the aggregate list. <br />Structures without an absolute water right or with zero sum water rights will be <br />ignored and a warning message will be printed to a log file. Net absolute values will <br />be taken from a table in the database and will not be calculated on the fly. <br />b) Sort the water rights by admin number. <br />c) For aggregated structures, calculate summed capacities and acreages. <br />d) Output the explicitly modeled and aggregated diversion station files to the diversion <br />station file (.dds). <br />e) Output all the resulting water rights to the diversion rights file (.ddr). <br /> <br />The version of watright resulting from this task will therefore be able to generate <br />diversion station and rights files where spatial aggregation but no water rights <br />aggregation has occured. This will be useful for a number of reasons: <br /> <br />· to help verifY the water rights aggregation (see next subtask) <br />· to allow water rights to be explicitly modeled if so desired <br />· to allow performance and sensitivity tests of water rights aggregation versus <br />non-aggregation <br /> <br />2. ModifY watright to perform water rights aggregation based on water rights classes. <br />For example, implement a command line option similar to -wrclass(admin#l, <br />admin#2,.....) which would indicate the break-points ofadmin numbers within the <br />entire data set being used. Conventions on how the water rights will be divided will be <br />agreed on and will be handled consistently (e.g., break classes at >= and < the class <br />admin numbers). No aggregation will occur if water rights classes are not specified <br />(the equivalent of the previous subtask). The water rights classes will be the result of <br />aggregation studies done in Task 2.04. The process is similar to that in the previous <br />subtask except that water rights classes must now be considered: <br /> <br />a) Get the absolute water rights for all the structures in the aggregate list. Structures <br />without a net absolute water right or with zero sum water rights will be ignored and a <br />warning will be printed to the log file. Net absolute values will be taken from a table in <br />the database and will not be calculated on the fly. <br /> <br />0064 <br /> <br />5 <br />