1 / 28

StreamStats Update and Demo—Please Stand By

StreamStats Update and Demo—Please Stand By. Conference line: dial 1-210-839-8503, PASSCODE: 24126 Please put your phone on mute If you don’t have a mute button, use *6 to toggle mute on/off Please don’t put your phone on hold (no tunes, please…)

patriciadean
Download Presentation

StreamStats Update and Demo—Please Stand By

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. StreamStats Update and Demo—Please Stand By • Conference line: dial 1-210-839-8503, PASSCODE: 24126 • Please put your phone on mute • If you don’t have a mute button, use *6 to toggle mute on/off • Please don’t put your phone on hold (no tunes, please…) • Familiarize yourself with the interface buttons while you wait for us to start

  2. StreamStats Progress Report July 1, 2003 Al Rea, Jacque Coles, Kernell Ries, Pete Steeves

  3. Background • Massachusetts application • Available internally Jan. 1999 • Available to public Jan. 2001 • Numerous presentations given • Based on ArcView/ArcViewIMS/Java • National StreamStats funding • FY2001, $160,000 • FY2002, $200,000 • FY2003, $200,000, including $50,000 added recently by Bob Hirsch • Idaho StreamStats FY2002—3, $75,000

  4. Development Team • Jacque Coles (Site administrator, ArcIMS specialist) • Al Rea (GIS specialist) • Kernell Ries (hydrologist, coordinator) • Peter Steeves (GIS specialist)

  5. Hardware Purchased • Dell Poweredge server with dual 1.0 Ghz processors and 216 Gb storage for ArcGIS and ArcSDE • Dell Poweredge single CPU server for ArcIMS • SnapServer 300 Gb data storage module • Servers placed in ID District • TOTAL COST ~ $13,000

  6. Software • ESRI ArcGIS • ESRI ArcIMS • ESRI ArcSDE • MS SQL Server 2000 • MS Visual Studio 6.0 Professional

  7. StreamStats—Accomplishments: • Completed StreamStatsDB statistics database • MS Access database with user-friendly GUI • Contains published descriptive information, basin characteristics, and streamflow statistics • Replacement for the Basin Characteristics File • Data to be entered by Districts • When populated, will facilitate large regional studies • Plan to add sediment characteristics • Developed by Aqua Terra Consultants

  8. StreamStats—Accomplishments: • Enhanced National Flood Frequency (NFF) software to serve as equation-solving engine for StreamStats • Added ability to solve low-flow as well as high-flow equations • Added weighting technique for ungaged sites • Added region-of-influence analysis • Added prediction intervals • TOTAL COST (StreamStatsDB and NFF) ~ $102,500

  9. StreamStats—Accomplishments: • Added measurement of basin characteristics to ArcHydro • “Desktop Tool” working in ArcMap 8.2/8.3 • Basin characteristics needed for Idaho (except MCS) • Basin area • Mean elevation • Relief • Mean slope • Percent of basin area >= 30 % slope • Percent of basin area >= 30 % slope and North-facing • Mean annual Precipitation • Percent Forested area

  10. StreamStats—Accomplishments: • Database development—Idaho • ArcHydro data for Salmon and Clearwater River basins, 18 HUCs • Partial processing completed for remaining 120 HUCs • Base map material for Web site completed, covering all Idaho plus large margin

  11. StreamStats—Accomplishments: • Prototype Web-Based Application for ID • User interface mostly complete • Base maps complete for ID • Basic watershed delineation • Basin characteristics computation • Interfaces with NFF to solve equations • Download watershed shapefile with attributes • Print maps shown in map frame • ESRI contract, partly done through CRADA

  12. StreamStats—To be done: • Testing, Testing, Testing • Load testing • Will multiple users crash it? • Are time-out errors acceptable? • Fix a few minor bugs • Add monthly flow exceedance estimates

  13. StreamStats—To be done: • To take web site public we must first: • Write data-set documentation (metadata) • Write general documentation, tutorials, caveats and disclaimers • Continue verification that results are comparable to those used for development of regression equations • Complete ArcHydro data development for remainder of Idaho • Initially exclude monthly flow exceedance computations requiring main channel slope • Display gage statistics database

  14. StreamStats—Future Developments: • Phase 2 Plans for Q4 FY 2003 • Make several improvements to the user interface • Allow user edits to watershed polygon • Better integration with NFF, improved reporting of results • Display stream-gage data from StreamStatsDB • Assess multi-user performance issues—find bottlenecks • Start on multi-state issues, implementation docs • If possible, begin serving parts of New England pilot (NH, VT, MA)

  15. StreamStats—Future Developments: • Phase 3 Plans for FY2004 (subject to change) • Multistate issues—scaling and implementation • Address performance issues—especially in multiuser environment • Add computation of Main Channel Slope • Extending channel to divide was manual process for Idaho • ESRI implementing automated process in ArcHydro • Extensive testing needed • Batch delineation (desktop tool only) • Channel elevation profile artifact removal • Drainage-area ratio method with nearby gages • Tie to National Hydrography Dataset (NHD)

  16. Implementation Plan • District offices will complete required work, usually through cooperative funding • StreamStats team will provide guidance and support to Districts • Everything will be served from StreamStats servers in Idaho • States will be put on line internally to check results • States will be made available to the public when results have been proven acceptable

  17. District Responsibilities • Provide regression equations • Populate the streamflow statistics database • Develop the necessary GIS data sets • Test the application and summarize results • Potentially develop new regression equations, using GIS data to measure basin characteristics • Approve use of equations on Web

  18. District Responsibilities—What will it take? • Building ArcHydro data sets from EDNA (experienced GIS expert) • ~30 min per 8-digit HUC interactive processing • 1—2 weeks building global and regional data sets • + 1 week learning curve for learning to do networks in GeoDatabase • Note: (ID and OR districts have people with experience, consider farming this out)

  19. District Responsibilities—What will it take? (cont.) • ~2 weeks per state to prepare DRGs • ~1 week per state to append/prepare NHD • Optional “New England Method” Enhanced DEM processing, 3-6 hrs interactive work per HUC plus (typically overnight) CPU time • Multiply GIS total by ~2X for general data management • Multiply GIS total by ~2X—5X for less experienced GIS staff (AML and Grid experience very desirable) • Very fast PC essential for processing

  20. District Responsibilities—What will it take? (cont.) • Hardware • Server and disk space<= $5K (to be centrally administered) • Hardware maintenance plus replacement every 3 yrs ~$2K/yr • External USB 2 Hard Drive ~$400 (will return to district) • Software licensing and site support • Assume OSW will continue to fund this • Potential future (shared) costs if OSW funding lost

  21. Why can’t districts run their own StreamStats site? • StreamStats is a very complex application with all the following working together: • ArcGIS with ArcHydro Tools • ArcSDE • SQL Server • ArcIMS • IIS • ASP • Tomcat • Javascript and HTML

  22. Why can’t districts run their own StreamStats site? (cont.) • Minimum Hardware & Software costs ~ $20,000 • ArcIMS and IIS security, firewall concerns • Need at least two dedicated servers, isolated from district LAN, high bandwidth WAN connection • StreamStats team = 4 part-time staff (<2 FTE) • Next 1-2 years, we will support 1 installation in Idaho serving multiple states • Longer term probably regional installations make sense

  23. Summary • StreamStats uses cutting-edge technology to put stream information in the hands of users • Based on the ArcHydro Data Model and Tools • Design is flexible and expandable • States will need to develop funding to implement • Full implementation will likely take several years

  24. More information • National StreamStats web page • http://water.usgs.gov/osw/programs/streamstats.html • Massachusetts StreamStats web page • http://ststdmamrl.er.usgs.gov/streamstats/ • NFF Program web page • http://water.usgs.gov/software/nff.html

More Related