Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 2.13-02 <br />CRDSS System Maintenance <br />1.0 ISSUE <br />This memorandum discusses the tasks involved in maintaining CRDSS systems. <br />2.0 DISCUSSION/ANALYSIS <br />CRDSS Database Update (Refresh) <br />Task memorandum 2.13-01 was prepared to describe in detail the recommended procedure to update <br />or refresh the CRDSS database with new and/or revised data. This procedure is also found in <br />Section 2.2 of the CRDSS Developers? Manual . <br />Maintain the CRDSS Software System <br />Although the CRDSS software systems were developed under other tasks, the purpose of this task <br />was to assure the continued proper operation of the UNIX operating system and CRDSS software. <br />The CRDSS software system, user accounts on the SGI workstations at RTi, GIS data at RTi, and <br />associated flat file data were backed up each business day. A full backup was performed each <br />Friday, while incremental backups were performed on the other business days. Tapes containing the <br />full backups were retained for 3 months before being returned to the rotation scheme. Routine <br />system administration was performed on the SGI workstations at RTi, including user account <br />maintenance, UNIX security, network security, and disk space maintenance. Additional <br />troubleshooting of the operating system and CRDSS software configuration was also performed. <br />The operating system was not upgraded during the year because of compatibility issues with other <br />software and to maintain consistency with the operating system level on other State efforts. Patches <br />to the current operating system were applied where necessary to address issues associated with the <br />development of the CRDSS and INFORMIX software. <br />Maintain the Spatial Database and GIS System Software <br />The CRDSS spatial database and GIS system software were also constructed under other tasks. <br />Maintenance for the CRDSS spatial data included the testing and documentation necessary to assure <br />the user of the reliability and accuracy of CRDSS spatial data. Each coverage is populated in <br />ARC/INFO and GRASS (see Task Memorandum 2.03-02 for a description of this process and Task <br />Memorandum 2.03-03 for an analysis of the conversion error statistics). For each ARC/INFO sub- <br />directory, there is an associated README file that includes a description of the coverages, as well as <br />source information. A title block was developed for each GRASS coverage that includes statistics <br />about the coverage, data information, and source information (including the corresponding <br />ARC/INFO coverage). <br />In addition to the documentation and testing aspects of maintenance, the team considered the <br />interaction of the data types populated and identified coverages that needed improvement from their <br />original format. A good example of needed improvement is the Hydrologic Units coverage that is a <br />1 <br />a320/taskmems/ 2-13-02.doc 01/03/97 <br />