Laserfiche WebLink
database requirements for CWCB. Some questions that resulted from the kickoff meeting that <br />need to be answered include: <br />• How long of an archive should be stored for certain data products such as SNODAS? <br />• What kind of value-added products should be produced from SNODAS? Basin averages? <br />Weekly change? <br />• How can we automate the flood outlook data layers to ensure that the least human <br />involvement is needed? <br />CWCB wants guidance on file management and directory structures. The team is not sure if <br />CWCB or DNR has file management responsibility for GIS data. <br />SMS Alert System <br />• CWCB was not aware of any development of the Alert System since it was utilized for <br />the Instream Flow DSS. An initial activity will be to review the existing system offered <br />by DWR to confirm understanding of its use for this project. <br />• CWCB does get email alerts to cell phones but a review of the alert configuration is <br />needed. <br />• It was suggested that flood warnings should not be available on the public site because <br />CWCB does not want to be liable for public response. A follow-up question is to <br />determine if any flood products should be provided to the public (e.g., Flood Outlook). <br />• Riverside mentioned that TSTooI now includes routing capabilities and it would be <br />possible to route flows to ungaged locations and perform checks at those locations. <br />There was some interest in this but utilizing this feature is probably a Phase 2 activity. <br />• Joe made the point that there was no need to try to forecast floods based on real-time <br />data. The focus should be on providing observations, i.e., streamflow and surrounding <br />precipitation data. <br />Data Quality Assessment and Utility of Data for Web Serving <br />• The Riverside team will assess the data that are obtained from various sources and <br />evaluate it for use in the Flood DSS. <br />• The data must be documented and possess metadata. <br />• The metadata should include update frequency in addition to standard metadata <br />requirements. <br />• If the data cannot confidently be kept current for the Flood DSS than it will not be used. <br />• The State will be made aware of all available data even they are not used in the Flood <br />DSS. <br />Data Pre-Processing <br />Riverside will prepare all data to be used in the Flood DSS. Map documents will be created and <br />layers will be symbolized during the data assessment phase. These map documents will be the <br />starting point for the Flood DSS map services. <br />