Laserfiche WebLink
recommend a way to organize electronic files, in order to effectively support the Flood DSS. <br />A workable solution will be implemented in the prototype, which can be adjusted in a full <br />system implementation. <br />Deliverable Data in the inventory will be collected and organized in a directory structure <br />suitable to support implementation of the prototype web site. The data will be provided to the <br />State as part of the prototype delivery. <br />4. Data Processing. Data processing includes the following types of activities: <br />• Projecting data to a consistent coordinate system. This may be needed to update data to <br />the State's standard (NAD 83, UTM Zone 13), support software features, or to improve <br />performance. <br />• Review data for map server suitability. For example, attributes may need to be adjusted <br />or added to allow linkages to non - spatial data. <br />• Merging data to create statewide layers. <br />• Performing cursory quality review to evaluate whether additional issues need to be <br />resolved. <br />• Creating new spatial layers to allow access to non - spatial data (e.g., locations of studies <br />or engineering data sets). <br />RTi will perform data processing necessary to implement a working prototype. However, <br />quality control will be limited to activities necessary to display layers in the map server. The <br />resulting spatial data will be maintained consistent with other CDSS data, to allow delivery to <br />and maintenance by the State. <br />Deliverable Data that are collected in the previous task will be updated as necessary to <br />support the prototype implementation (for example to merge data to create Statewide layers). <br />Data processing will occur at a level suitable to demonstrate prototype features. The data will <br />be provided to the State as part of the prototype delivery. <br />5. Adapt Existing CDSS Map Viewer for Main Interface. The existing CDSS Map Viewer <br />files will be utilized to create a website for disseminating Flood Protection data. The look <br />and feel and features of the existing site will be available in the new site, which will be <br />accessed using a link from the CWCB website. The map layers will be configured using the <br />inventory and grouping discussed above (finalized during the project). Symbols for layers <br />will be consistent with the CDSS Map Viewer where possible and utilize standard symbols <br />where available (e.g., to match FEMA or other agency representation). The initial <br />implementation will be made available to the State as an interim product, so that feedback on <br />the layer grouping and symbols can be evaluated before final delivery. <br />Deliverable A new ArclMS web site application will be developed. The application will <br />have features similar to the existing CDSS Map Viewer, but will display data suitable for the <br />Flood DSS, as indicated in the data inventory. All files necessary to support the web site will <br />be provided to the State as part of the prototype delivery. <br />6. Implement Access to Non - Spatial Data. Non - spatial data consisting of reports and model <br />files need to be managed, whether or not a spatial link to the data is available (the next item <br />discusses linking the non - spatial data to the map). The existing CDSS web site utilizes a <br />DWR design (utilizing the DotNetNuke framework) and a database to manage static content. <br />Dynamic content (e.g., database queries for real -time data) is formatted on the fly using <br />