Laserfiche WebLink
' PROJECT APPROACH <br />' 4.6.2 Automate Flood Outlook, SNODAS, and SNOTEL Data Processing and <br />Management <br />Goals <br />Develop a process that will dynamically update the Flood Outlook data layers and that will retain <br />a sufficient data archive to support related data products. <br />' Background <br />The flood outlook data category from the prototype Flood DSS includes four data layers: flow <br />conditions, SNOTEL SWE, the -CWCB Flood Threat Bulletin, and SNODAS SWE. For the <br />prototype application, static data layers were used for demonstration purposes. For the Phase I <br />Flood DSS, these data layers need to be updated on a regular basis to provide current information <br />' about snowpack, streamflow, and the threat of flooding. <br />Aaproach <br />As described in Section 4.5, the SNOTEL and SNODAS data are available online and can be <br />downloaded and processed. However, updating these data layers for the Flood DSS map service <br />will require careful data management. Automation scripts will download the data and overwrite <br />the previous day's data, while retaining a historical data archive as needed to support the data <br />products. Text file logs will record the dates of the various .layers and be used by the map <br />service to determine the correct date of the data layers. <br />SNOTEL SWE -The CWCB has obtained from Riverside asemi-automated tool for <br />downloading and processing SNOTEL SWE data from a previous contract. The tool uses a <br />combination of Python and TSTooI to download the SNOTEL SWE data and process it into a <br />tabular format. A map document then. joins the data to a shapefile of SNOTEL stations. This <br />tool could be further developed to process SNOTEL soil moisture data, and further. automated to <br />run on a daily basis with no user interaction. .The Flood DSS map service would then <br />automatically link to the current SNOTEL data. A second option for the SWE data is to display <br />SNOTEL percent of average SWE using a Google Earth KML file produced by the NRCS. This <br />option involves downloading the layer daily, but otherwise no other processing is necessary. The <br />KML can be displayed in the Flood DSS map service as is. <br />Flood Threat Bulletin - As described in Section 4.5, the Flood Threat bulletin is produced by <br />HDR and is available in a PDF map format from the CWCB website. The flood threat layer in <br />the Flood DSS prototype was created by digitizing a single bulletin. It will not be a sustainable <br />solution to manually .digitize each bulletin as it is released. Riverside will contact HDR and <br />attempt to .obtain the data in a GIS format to be used in the. map service. If GIS data can be <br />obtained, an automated process could be developed to update the data layer each time it is <br />released to ensure that the layer is current. In the event that the data cannot be obtained in a GIS <br />format, one alternative is to link to the Flood Threat bulletin in PDF format from the Flood DSS. <br />A second alternative is to digitize a limited number of the PDF products. <br />SNODAS SWE -The Flood DSS prototype contained a single day's SWE from SNODAS. The <br />statewide Flood DSS will display the most recent daily SWE. It would also be a useful. feature to <br />store a historical archive, such as the previous 30 days, to support data products showing the <br />change in SWE over a daily, weekly, or monthly time interval. Riverside has several automated <br />scripts and processes developed to download and process the SNODAS SWE data. In addition, <br />DNR RFP PDA-923 49 ~ ~ v E R cj <br />