Kickoff memo_final - Laserfiche WebLink

Home Browse Search

prototype features could be implemented (navigation, map displays, etc). The bigger issue may be the ability to integrate the mapping solution with other system components, such as LaserFiche, real-time data (e.g., flow), multiple snapshots of data (e.g., SNODAS). Therefore further evaluation will take into consideration the requirements of other system components and also input from the needs assessment. However, evaluation cannot wait until the needs assessment is completed. Therefore, initial information from the needs assessment will be considered in recommendations for the technologies. Task 4 -Data Inventory Potential data sources for inclusion in the Flood DSS will be identified through the user needs assessment, the prototype inventory, CWCB input, and county/local data contacts. The data sources will be further evaluated in terms of availability, updating frequency, collection effort, and system integration effort. Attribute information will be collected (e.g., data format). Given the project resources, the data sources will be prioritized, both for inclusion in Phase I as well as future efforts. Riverside will produce a summary memo and spreadsheet documenting the results of the data inventory and identifying data collection recommendations. Riverside will review the memo with CWCB before beginning the data collection task. Riverside will work with CWCB to ensure the data prioritization and collection strategy will result in a Flood DSS that supports decision-making in addition to being a data repository. • Chris indicated that we should rely on web services as much as possible to minimize the data maintenance burden on CWCB. • Christine visits communities every 3 years for the Community Assistance Program (CAP). This can be a mechanism to help collect user needs and reduce costs. • Joe Busto is interested in using radar precipitation to help indicate stream conditions. Flood DSS should limit links to external sites or use the NOAA "FX" network feed. • Chris recommended waiting until the CWCB interviews to review the prototype data inventory. • The public Flood DSS site should be informational and include DFIRMs, but not alerts or warnings due to liability issues. Task 5 -Data Collection Statewide Data Collection Riverside will collect statewide data for the Flood DSS. This will consist mostly of existing GIS data: • The main data layers include CDSS data, aerial photography, elevation data, land cover data, weather modification data, and flood warning and flood threat bulletins. • Riverside will utilize existing web services as much as possible when appropriate. • Joe Busto will be the contact for the weather modification data. Chris Pacheco at MRCS provides a supporting data product to Joe. Joe can provide an example product. • Joe Busto purchases data from the Colorado Avalanche Information Center on snow loads at highway passes. We need to determine if avalanche threat information is a user requirement.