Run WEPP anywhere in the continental U.S.
Elevation data is from the USGS National Elevation Set. This interface uses TOPAZ for watershed delineation. The soils are built using SURGO/STATSGO. Landcover is selected based on the USGS National Landcover dataset. Climates are generated from the CLIGEN database.
782 projects and 33,409 hillslopes ran since January 1, 2019
The WEPPcloud Post-Fire Erosion Prediction (PEP) allows users to upload a burn severity map and predict erosion
based on fire severity.
View 15 May 2019 USDA Forest Service Webinar: An Introduction to WEPPcloud-PEP
The RRED interface uses WEPP inputs generated by the Rapid Response Erosion Database (RRED). These parameterize Disturbed WEPP soils and managements with with SSURGO/STATSGO soil data.
372 projects and 2,326 hillslopes ran since January 1, 2019
WEPPcloud for Europe.
Managements are assigned based on ESDAC landuses. Soils are built from ESDAC and EU-SoilHydroGrids data. U.S. climate stations are selected based on E-OBS monthly precip and temperatures.
The PeP interfaces provide post fire erosion modeling and ash transport modeling. Parameterizes soils based on burn severity and soil texture using Disturbed WEPP soil files.
EU projects and EU hillslopes ran since January 1, 2019
PeP Method 2 projects and EU WEPP-PeP hillslopes ran since January 1, 2019
WEPPcloud for Australia.
Managements are assigned based on Land Use of Australia 2010-11. Soils are built from ASRIS soil data. U.S. climate stations are selected based on AGDC monthly precip and temperatures.
The PeP interfaces provide post fire erosion modeling and ash transport modeling. Soils based on burn severity and soil texture using Disturbed WEPP soil files.
AU projects and AU hillslopes ran since January 1, 2019
PeP Method 1 projects and AU WEPP-PeP hillslopes ran since January 1, 2019
Run the Rangeland Hydrology and Erosion Model (RHEM) over the US.
Where available foliar and ground covers are estimated from NLCD Shrubland 2016 data.
SURGO/STATSGO is used to identify soil textures
RHEM projects and RHEM hillslopes ran since January 1, 2019
Site Specific Resources
The Lake Tahoe Project incorporates region specific soil, phosphorus, and estimated soil burn severity.
Coeur d'Alene Lake Interface
Provides access to running WEPP in the Coeur d'Alene Lake Basin.
WEPPcloud UtilitiesCombined Watershed Viewer URL Generator
For assistance or questions please contact Mariana Dobre at firstname.lastname@example.org or Roger Lew at email@example.com
|February 28, 2020||Cligen5.32 integrated into interface. This includes a fix for tpeak values when building from observed datasets.|
|June 17, 2019||Hillslope and Watershed ash transport modeling for WEPPcloud-PEP. Single Storm climate fully implemented.|
|May 17, 2019||Annual climate precip, tmax, tmin in station summary and .cli summary. Phosphorus variables removed from freq flood report when not ran. Units fixed for runoff on combined watershed viewer. Summary for wepp run is now populated. Mary Ellen's soil texture classification incorporated. Soil texture based on surgo data in ERMiT download. ERMiT meta data file contains climate station information (state, station description, par). Link to FSWEPP batch processing scripts below the ERMiT csv. Units pretty much everywhere rounding to 2 significant digits. MCL and CSA inputs respect the units of the project (m and ha or ft and acre). Tab titles now include project name if a project name is defined.|
|March 29, 2019||Various usability enhancements. 10-min and 30-min peak rainfall intensities added to return period analysis. soil fix for channels and hillslopes with dominate water.|
|February 14, 2019||Hazard SEES - FireEarth Data Portals added.|
|January 14, 2019||Miscellaneous interface improvements and bug fixes.|
|December 3, 2018||Bug fix for building DAYMET Climates with small extents.|
|November 2, 2018||Changed default parameters for running TOPAZ and WEPP.|
|August 27, 2018||Combined Watershed URL Generator. Ability to reassign landuse to different management. Zack Holden's WRF Precipitation dataset integrated into Debris Flow model over bounds of [-117.386, 34.694, 48.756, -96.980].|
|August 13, 2018||Debris flow enhancements (liquid limit from surgo, SBS area based on grid).|
|July 31, 2018||Fixed layout bug with screens with 1280px width.|
|July 30, 2018||Updated phosphorus maps for Lake Tahoe. New WEPP binary to fix missing chanwb output. Bug fix for hillslope delineation in locations below 1m in elevation.|
|July 20, 2018||frost submodule removed from hillslope processing. WEPP bug fix for empty chanwb outputs.|
|June 14, 2018||Disturbed WEPP managements added to single landuse selection. Single landuse selection added. Support for 98.4 management files.|
|June 10, 2018||Minor map and interface enhancements.|
|June 8, 2018||2006.2 WEPP soil support added, county level soil database for NSERL.|
|June 3, 2018||Coeur d'Alene added.|
|May 31, 2018||Lake Tahoe (LT) Homepage added.|
|May 18, 2018||Observed climates for Lake Tahoe added to interface.|
|May 15, 2018||WEPP runs hillslopes in parallel.|
|May 11, 2018||Debris flow model added.|
|April 23, 2018||Soil restrictive layer scaled by 1/100.|
|April 7, 2018||Power User Panel added to interface.|
|April 5, 2018||Total yearly water balance report.|
|April 4, 2018||totalwatsed export added.|
|April 3, 2018||Watershed preparation details added.|
|April 3, 2018||Watershed preparation details added.|
|Mar 26, 2018||Projects can be set READONLY and PUBLIC.|
|Mar 21, 2018||Project archive export added.|
|Mar 20, 2018||Return Period Analysis implemented.|
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.