Laserfiche WebLink
application of the model and allow consideration of new data and changing conditions. <br />Some additional automated processing will be required to translate these primary sources <br />into a format useable in modeling. Selected software tools should be capable of exporting <br />information as GIS shape files. <br />^ Surface water and consumptive use data processing and model input preparation will remain <br />the same, since these are mature processes with software tools that work well. <br />^ Underlying databases and GIS coverages will clearly differentiate actual measured data from <br />interpretive products and engineering estimates. Control points based on engineering <br />judgement that may be necessary for model construction will be documented and maintained <br />in working GIS coverages. This will provide a clear record of how a model dataset is <br />generated and allow for future modification if new data become available. <br />^ The model calibration process should remain flexible and allow incorporation of advanced <br />techniques for streamlining calibration, such as the use of MODFLOW-2000 parameterization <br />and the PEST package use of pilot points and regularization methods. <br />^ Processes and tools will be self-documenting to facilitate checking. Software tools will use a <br />command file approach, similar to that used in other State applications such as StatePP or <br />StateCU. In this approach, a GUI will be used to generate or modify command files that <br />control actual processing of data. This provides documentation of the process, source and <br />destination of data, and control parameters. These control files must allow the incorporation <br />of user comments for additional documentation. <br />^ Individual steps in the current process will be evaluated for opportunities to streamline them. <br />This could be accomplished through refinements to the current integration package <br />(ModGUI) that manages many of the software tools. <br />^ A model GUI (currently GMS version 3.1) will be utilized to the extent possible to handle the <br />modeling processes included in its design rather than developing additional tools to handle <br />those same processes. <br />^ Any software tools selected or developed need to be compatible with current systems used <br />by the State for GIS and database management. All tools will run on a current version of <br />Microsoft Windows. <br />^ Evaluation of future scenarios, primarily related to changes in stress terms such as pumping, <br />recharge, and return flow will be driven by changes to source GIS coverages or HydroBase, <br />then processed through the data centered process. Planning scenarios will likely derive <br />projections from sources other than HydroBase. Management of future scenarios is difficult <br />to anticipate and thus the recommended model enhancements should maintain a high degree <br />of flexibility to incorporate a variety of data sources and potential model scenarios that could <br />be simulated under both steady-state and transient conditions. <br />^ Software tools that are developed need to be generalized so basin-specific assumptions are <br />controlled by files, rather than within the program code. <br />