Laserfiche WebLink
PROJECT APPROACH <br />' 4.2.1 User Needs Assessment <br />The CWCB will identify a maximum of 15 stakeholders to provide input on the data <br />' requirements. Riverside will develop a questionnaire or interview approach that will identify <br />useful data layers, and data products or summaries that can be created in the Flood DSS to help <br />users make decisions. To the extent possible, Riverside will .conduct face-to-face interviews. <br />' Riverside will question each stakeholder regarding the data types (e.g., weather, snowpack, <br />reservoir storage or operations, hydrologic conditions, outlook reports, flood mapping, hazard), <br />sources (e.g., federal, state, local), and products that are regularly employed as part of their work <br />' process. If possible, Riverside will obtain sample data products. Riverside -will collect <br />information about the high-risk flood areas that should be focused on when statewide data are <br />not available. <br />' Based on the results of the user needs assessment, Riverside will inventory and rank all identified <br />data -types and sources. Data sources that are essential for inclusion for the Phase I Flood DSS <br />will be identified and categorized into "needs" versus "wants." Other data sources may be <br />' categorized as candidates for Phase IL <br />Deliverables <br />' 1. Technical memorandum describing- the results from the user needs assessment and <br />recommendations for conducting the data inventory. <br />4.3 Evaluate Alternative Technologies for Flood DSS <br />:Goals <br />' Determine technologies that can best meet the requirements of the Flood DSS, while being cost- <br />effective and consistent with the Geographic Information Technology (GIT) infrastructure at the <br />DNR. <br />Background <br />ESRI's ArcIMS software and corresponding HTML Viewer client for the web browser were <br />' chosen for the CDSS Map Viewer and Flood DSS Viewer prototype, both developed by <br />Riverside. ArcIMS was the map server solution offered by ESRI at that time; however, ESRI <br />has introduced ArcGIS Server and newer browser clients, which are components of the ArcGIS <br />product suite. The ArcIMS site has functioned well and required little maintenance; however, <br />the ArcIMS product will cease to be supported by ESRI at some point and has limited <br />capabilities compared to newer technologies. For example, the HTML Viewer used as the client <br />' for the prototype is not capable of overlaying multiple map services (mashup). The Phase I <br />Flood DSS effort provides an opportunity to move to a newer technology if appropriate. <br />Recently, Riverside performed a review of GIS technologies being used by DNR. Although <br />' there is interest in open technologies, ESRI GIS software is predominantly used. DNR is using <br />ArcGIS Server and has expressed interest in using it more in the future. Riverside also <br />performed a review of web mapping technologies as part of the SPDSS project. The. outcome <br />' from that review was that there is no singular best solution. In some cases, using a combination <br />of technologies maybe appropriate within a system. Web technologies have advanced quickly <br />in the past :couple of years, with the advent of service oriented architecture (SOA), Web 2.0, and <br />AJAX resulting in a more dynamic and interactive web application. <br />DNR RFP PDA-923 27 R ~ V E R S~ ~ E <br />