1. Where does VIPER get its data from? Tom Pagano tom.pagano@por.usda.gov 503-414-3010

2. What data do we need? VIPER’s input and storage of data Old and new databases AWDBWYFORCDBSSNOTEL Real-time data schedule Local file import

3. What data do we need? Metadata Station lists, lat/lon/elev Historical time series data Real-time time series data Snowpack, Precipitation, etc Forecast equations, configurations

4. VIPER Workbook Station Metadata Historical Time-Series 1 station POR Real-time Data All stations 2 years Equations/ Configurations

5. VIPER Workbook Station Metadata Historical Time-Series 1 station POR Real-time Data All stations 2 years Equations/ Configurations Metadata Data AWDB

6. VIPER Workbook Station Metadata Historical Time-Series 1 station POR Real-time Data All stations 2 years Equations/ Configurations USGS webpage Metadata Data AWDB

7. Old time series databases Old databases and new databases CDBS “Final” data Period of record ~1 year out of date Daily, monthly Snow, Precip, Temp Resv, Strm

8. Old time series databases Old databases and new databases CDBS “Final” data Period of record ~1 year out of date Daily, monthly Snow, Precip, Temp Resv, Strm SNOTEL Provisional Recent 2 years Hourly (and daily) All snotel elements Archive kept (since ?)

9. Old time series databases Old databases and new databases CDBS “Final” data Period of record ~1 year out of date Daily, monthly Snow, Precip, Temp Resv, Strm SNOTEL Provisional Recent 2 years Hourly (and daily) All snotel elements Archive kept (since ?) WYFOR Ephemeral Recent 2 years Monthly Snow, Prec, Strm Resv, “Misc” Archive kept (since ‘93)

10. Old time series databases Old databases and new databases CDBS “Final” data Period of record ~1 year out of date Daily, monthly Snow, Precip, Temp Resv, Strm SNOTEL Provisional Recent 2 years Hourly (and daily) All snotel elements Archive kept (since ?) WYFOR Ephemeral Recent 2 years Monthly Snow, Prec, Strm Resv, “Misc” Archive kept (since ‘93) AWDB Provisional and final mixed All years All durations All elements* New time series database *Planned NOTE: AWDB load strategy being reworked so rest of slides may not apply in near future!

11. Example- where do historical monthly snow come from? 1960 1970 1980 1990 2000 Back estimated snowcourse Site automated (aug 1980) Brumley Snotel

12. Example- where do historical monthly snow come from? 1960 1970 1980 1990 2000 CDBS 1x load of cdbs… updated if Dana notified of changes 1x load daily data in off season into monthly slots (snotel.. Or daily cdbs?) SNOTEL

13. Historical streamflow data 1960 1970 1980 1990 2000

14. CDBS Wyfor “under” CDBS Historical streamflow data 1960 1970 1980 1990 2000 1x load of old wyfor files since mid 1990’s Then on top of that… 1x load of cdbs… updated if Dana notified of changes

15. The realtime data schedule and synchronization AWDB database WyforSNOTEL 4x a day, complete load (1:20am, 5:20am, 11:20am, 10:20pm)

16. The realtime data schedule and synchronization AWDB database WyforSNOTEL Any DMP edits to snotel loaded every 5 minutes to wyfor/awdb DMP Edits

17. The realtime data schedule and synchronization AWDB database WyforSNOTEL Spreadsheet files loaded every 10 minutes all day to wyfor/awdb CSV spreadsheet files (non-snotel data) CSV processor

18. The realtime data schedule and synchronization AWDB database WyforSNOTEL Direct edits of wyfor reach wyfor right away But reach AWDB 50 minutes after the hour 5-9am, 11am-4pm and 11pm. Worst method of entering data for viper. Manual edits

19. If you have custom datasets, Viper can also access local CSV format files. Same layout as individual station data sheets (e.g. data1, data2) Realtime data gets manually entered in “ExternalData” sheet.

20. OMG Viper is so slow!!!! Viper is a network-hungry application. Within the USDA backbone, your connection should be very fast. Outside the backbone, speed varies from tolerable to disgruntling.

21. OMG Viper is so slow!!!! Viper is a network-hungry application. Within the USDA backbone, your connection should be very fast. Outside the backbone, speed varies from tolerable to disgruntling. The way viper connects to the database is the same way that users contact the new update report…. which can mean: