Laserfiche WebLink
A GUI-based browse tool will be developed to display GIS coverages and tabular data that is keyed <br />to the spatial data. This tool will be available from the main CRDSS interface and will allow a <br />CRDSS user to query the database based on selections from a map-based display. Task <br />Memorandum 1.05-16 describes the general features of the GUI. The data items that will be <br />displayed by the tool are also indicated in Task Memorandum 1.05-16. The database browse tool <br />will use GRASS to display coverage data. The tool will be incorporated into the main CRDSS shell; <br />however, it is likely that the tool will be called as an external process. This will allow more <br />flexibility in the use of the tool. The database will be queried as described in Task Memorandum <br />1.05-8 and display forms will be developed to display the appropriate database tables. The display <br />forms will be shared with other development tasks through discussions by the System Integration <br />Team. <br />The extent of GUI development for database browse utilities can be modified based on budget and <br />user needs. The consultant recommends that a stepped approach be used in the development of these <br />tools with the goal being to provide database information first while providing a GUI later in Year 1 <br />(See Task Memorandum 1.05-16). Additionally, GUI-based database products (such as INFORMIX <br />?4GL++?) that are not yet available will allow database browse tools to be developed more easily in <br />later years. The consultant recommends that the majority of database browse tools (outside of the <br />general map-based tool) remain as form-based tools until the graphical database products are more <br />mature. <br />DMI Utilities <br />As stated earlier in this task memorandum, DMI utilities do not always include a GUI. There may <br />actually only be a few DMI utilities that do require a GUI (the CU model DMI is one). Because of <br />the complexity of the CRDSS database and the complexity of analysis scenarios, a number of small <br />DMI utilities will be developed to perform specific and limited functions. For example, a DMI <br />utility will be developed to read a time series from the database and format it for plotting. <br />The need for DMI utilities will be outlined in DMI utility task memoranda prepared by modeling <br />task leaders. The task memorandum for a specific DMI utility will indicate the desired functionality <br />of the DMI utility, the usage of the utility, and the data inputs and outputs for the utility. The needed <br />low-level DMI routines (see Task Memorandum 1.05-8) will be developed by the consultant for use <br />by the other developers. General DMI utilities which are used by more than one modeling task will <br />be developed within the system integration task. DMI utilities specific to a model will be developed <br />within the modeling task (the low-level DMI routines will still be developed in task 1.05). <br />The System Integration Team meetings will provide a forum for discussions about DMI utilities, <br />their purpose, and possible use in different modeling tasks. <br />Other Toolbox Programs <br />The consultant is evaluating other display tools for the CRDSS, including spreadsheets and statistics <br />packages. The GUIs for such packages will depend on the supplier of such software. Several widely <br />XMgr <br />popular programs have already been made available for the CRDSS developers, including , <br />Mosaic xv <br />, and . In general, these utilities will be used in a stand-alone fashion for data analysis or <br />will be called from a controlling script to display information at an appropriate time during an <br />analysis. The implementation of such tools will be carried out under task 1.05. Most tools will be <br />implemented in Year 1 because Year 1 tasks involve the major activities for which such tools are <br />6 <br />A275 07.28.94 1.05-31 Malers <br />