Laserfiche WebLink
conceptual model elements independently from the numerical grid; interpolation capabilities; <br />visualization capabilities; management of aquifer properties; ability to manage files for <br />MODFLOW-2000 packages that may be used in the SPDSS; available calibration assistance <br />tools; and documentation and support issues. Vistas and ArgusOne were eliminated for <br />consideration and GMS is the recommended as the SPDSS groundwater flow model GUI based <br />on the analysis of capabilities presented in Table 3. <br />Vistas was eliminated because it provides weak internal conceptual model capabilities, even <br />though it is able to utilize shape files for defining conceptual model elements. The actual <br />process for importing the shape files and creating the numerical model in Vistas involves many <br />manual steps, limiting the utility of this process. The interpolation capabilities within Vistas <br />include only distance weighted options, which would necessitate incorporation of another <br />external program to apply techniques such as kriging. Visualization capabilities are acceptable <br />for two-dimensional displays and interchange with ArcGIS, however, three-dimensional <br />displays require the use of external programs. Implementing more automated data input <br />processes and conceptual-model capabilities within Vistas would involve significant <br />development time. <br />ArgusOne meets many of the requirements for the GUI. This package is being used by the <br />USGS as their GUI for their current Denver Basin modeling effort. However, this package was <br />eliminated due to several limitations that make it less suitable than the alternatives. The <br />visualization capabilities, while adequate for use during modeling, are not adequate for final <br />report production. Interpolation tools available within ArgusOne are limited compared to <br />those in GMS. ArgusOne does not incorporate internal tools to assist in evaluation of <br />calibration, or to directly use calibration assistance tools such as PEST. Construction of <br />conceptual model elements is also cumbersome, especially for transient simulations. Since this <br />package uses components developed by both the USGS and a commercial vendor, user support <br />would also be an issue, since the USGS does not directly support users outside of their <br />organization. Data interchange with the USGS may occur using both actual model files and <br />shape files, so use of different modeling GUI packages by the State and USGS will not impede <br />data interchange or interoperability between the models. The State may need to acquire a <br />license to ArgusOne to facilitate this interchange of files in an efficient manner. <br />GMS is recommended as the primary modeling GUI for the project. GMS has superior <br />conceptual model capabilities, excellent interpolation tools, including kriging and extensive <br />two- and three-dimensional visualization features. An earlier version of GMS has been used on <br />the RGDSS, so the State is familiar with use of this GUI. GMS allows extensive interaction with <br />ArcGIS for both conceptual model definition and exporting of model configuration and results. <br />GMS incorporates ArcObjects into its interface, which allows use of many ArcGIS capabilities <br />within GMS. GMS incorporates use of PEST into the GUI. Many of the pre- and post- <br />processing tools that are recommended, currently operate with GMS. GMS uses file formats for <br />internal conceptual model definitions that are documented and suitable for modification by <br />other programs to supplement the internal GMS capabilities. The limitations identified in GMS, <br />such as no support in the GUI for some of the recent MODFLOW packages like MNW and SFR, <br />can be overcome with modifications to current State processes using external packages. <br />