Laserfiche WebLink
• LOMRS & CLOMRS will be accessed through external links, while DFIRM GIS layers <br />will be hosted internally or obtained via web services. One possible solution is to host <br />final DFIRMs but link to preliminary maps. <br />• AMEC should harvest as much DFIRM data as possible, even if preliminary. <br />• For high-risk counties, where no DFIRM data exists, AMEC will supplement with <br />HAZUS Level-1 spatial data. <br />• AMEC should pursue non-spatial flood data from local governments. However, CWCB <br />advised the project team against `data overload' during the Inventory task (i.e. focus on <br />key data first, then secondary data once all key data are collected). <br />• CWCB would like all data that are gathered to be delivered to them, even if the data are <br />not included in the Flood-DSS. These data could be organized /automated for later <br />inclusion in the DSS, or for other uses. <br />• Where possible the project team should obtain (access) data directly from external <br />websites. This will allow for faster access for large raster files, and reduce the burden of <br />data update. <br />• When encountering data sensitivity concerns from local government, AMEC should <br />report and discuss this at the next progress meeting in order that CWCB can make <br />decisions on how to deal with the concern. In some cases this might require someone <br />from CWCB to sign a release form with conditions of use. <br />• When encountering costs associated with data, AMEC should report and discuss this at <br />the next progress meeting in order that CWCB can make decisions on the importance of a <br />particular dataset and willingness to pay for the information. <br />• When encountering general resistance to discussing and/or sharing data, AMEC should <br />report and discuss this at the next progress meeting in order that CWCB can provide <br />AMEC guidance on how to proceed. In some cases CWCB staff may determine someone <br />from CWCB should contact the local government agency. <br />Data Digitization <br />The approach will be to collect as much data as possible, but digitize only what is required. <br />CWCB may have internal resources to help with digitization. <br />Task 6 -Data Processing <br />Real-Time Flow Data <br />• The point was made that we have several proven alternatives based on previous work. <br />Riverside will implement something in an early release, and respond to feedback. <br />• Having the data available in the system sooner rather than later would allow for early use <br />of the system. Most extreme events occur due to seasonal rains (not snowmelt). <br />Flood Outlook, SNODAS, SNOTEL Automation <br />Riverside will develop automated procedures for collecting flood outlook/flood bulletins, <br />SNODAS data, and SNOTEL data. Automated routines will be developed and implemented at <br />the State's facilities to update the data. The Flood DSS development may identify some new <br />