Laserfiche WebLink
2. Project Summary <br />The following sections summarize the tasks that were completed during the implementation of the Flood <br />DSS prototype. <br />Prototype development utilized the existing ArcIMS platform created by RTi for the CWCB /DWR <br />(CDSS Map Viewer). This proven foundation allowed for a cost - effective means for rapid prototype <br />development, creating the opportunity to concentrate primarily on gathering, processing, and entering <br />appropriate data, and displaying it for effective assessment. Another major objective was to make <br />information in Content Manager available through the DSS interface, enabling text and other data to be <br />accessed and selected based on its geographic emphasis. <br />When available, flood data covering the entire state were collected. However, it was agreed at the kickoff <br />meeting that much of the information would be specific to counties or communities. As it would be <br />outside the scope of this prototype to collect data for multiple counties and communities, it was agreed <br />that Larimer County should be the example focus of more spatially detailed data. This selection was <br />based upon the range of representative physiographic and land cover conditions the area offers, the fact <br />that the City of Fort Collins recently suffered a devastating flash flood (1997) leading to a state of <br />emergency declaration, and the proximity of RTi to the County and City offices. <br />Prototype development activities included the following tasks: <br />1. Project Kickoff — to restate project goals and constraints, to allow initiation of work. <br />2. Data Inventory — preparation of a list of all data identified for inclusion in the Flood DSS. <br />3. Data Collection — assembling data files for data types listed in the data inventory. <br />4. Data Processing — prepare data for use in the Flood DSS web site. <br />5. Adapt CDSS Map Viewer — adapt existing CDSS Map Viewer files to create the Flood DSS Map <br />Viewer. <br />6. Implement Access to Non - Spatial Data — make Content Manager information and other web -based <br />data available to the Flood DSS Viewer interface. <br />7. Implement Map Links to Non - Spatial Data — link the spatial data to non - spatial data. <br />8. Prototype Installation — provide to State all data layers and available metadata, secondary data files <br />implemented for the prototype, map viewer site files, and configuration documentation. <br />9. Prototype Evaluation — prepare recommendations in this document. <br />10. Project Management — participate in coordination and status meetings in order to deliver a quality <br />product that meets the scope. <br />These tasks are summarized below. <br />2.1 Project Kickoff <br />A Flood DSS project kickoff meeting was held at the CWCB on May 5, 2006 and was attended by Tom <br />Browning, Ray Alvarado, and Carolyn Fritz of the CWCB; Lori Torikai of DWR; and Steve Malers, <br />Amnon Nevo, Jay Day, and Graeme Aggett of RTi. Minutes of the meeting were subsequently <br />distributed to attendees and were updated to reflect feedback. Major decisions from the kickoff, which <br />impacted later work in the project, were: <br />1. Although the full -scale system is envisioned to be statewide, the majority of interest by users is <br />on a county level. Larimer County was identified as a suitable candidate for the prototype, when <br />statewide data were not readily available. <br />2. Major categories of use include flood hazard mapping, flood outlook, and general data <br />clearinghouse. <br />